There sure hasn't been much activity with this thread. Am I the only one who's still sticking with BSD?
No no - but BSD-People barely have time for computers or even forums (except they have questions ;-).
That's excatly why I'm writing this... :-)
I have problems getting the client to run on a recent 7-stable/amd64. It reports
5.10.32
process exited with code 193 (0xc1, -63)
2008-06-26 02:37:45.2684 [normal]: Built at: Feb 19 2008 19:44:48
2008-06-26 02:37:45.2685 [normal]: Start of BOINC application 'einstein_S5R3_4.34_i386-unknown-freebsd'.
Fatal error 'can not create signal daemon thread!
' at line 236 in file /usr/releng_5_4/src/lib/libpthread/thread/thr_sig.c (errno = 22)
SIGABRT: abort called
There sure hasn't been much activity with this thread. Am I the only one who's still sticking with BSD?
No no - but BSD-People barely have time for computers or even forums (except they have questions ;-).
That's excatly why I'm writing this... :-)
I have problems getting the client to run on a recent 7-stable/amd64. It reports
5.10.32
process exited with code 193 (0xc1, -63)
2008-06-26 02:37:45.2684 [normal]: Built at: Feb 19 2008 19:44:48
2008-06-26 02:37:45.2685 [normal]: Start of BOINC application 'einstein_S5R3_4.34_i386-unknown-freebsd'.
Fatal error 'can not create signal daemon thread!
' at line 236 in file /usr/releng_5_4/src/lib/libpthread/thread/thr_sig.c (errno = 22)
SIGABRT: abort called
Exiting...
]]>
Any ideas how to fix this?
Not really, I'm getting this error too (FreeBSD 7.0R/amd64/einstein-4.34).
What does your /etc/libmap.conf and /etc/libmap32.conf contain?
According to the port version (4.18) there should be a mapping from libpthread.so.1 to libc_r.so.5 in /etc/libmap32.conf
According to the manual page for errno, value 22 means EINVAL (some passed argument to a function is invalid).
I've asked the maintainer but he doesn't know either, but according to him it runs fine on FreeBSD 6.x/amd64 (I've never tried that myself).
>Not really, I'm getting this error too (FreeBSD 7.0R/amd64/einstein-4.34).
>What does your /etc/libmap.conf and /etc/libmap32.conf contain?
>According to the port version (4.18) there should be a mapping from >libpthread.so.1 to libc_r.so.5 in /etc/libmap32.conf
I started off with no libmap.conf at all when I first saw the error. After reading the port message I tried
No, we're not dead yet :) but I admit I have paid little attention to BOINC past few months.
Right now I'm working on updating the client port to 6.2.14, and I'm eager to see S5R4 app for FreeBSD in the future.
Thank you Pav for your work on the Boinc ports, I only have a single, solitary FreeBSD machine but it's nice to be able to do something useful with it while it's sitting unused. So how long does it tend to take for FreeBSD versions of apps to appear?
My machines are idling right now, unfortunately. SIMAP is out of work, I don't do SETI for political reasons, Linux apps gets hung on completion so they require babysitting I can't give them, and I don't know any other project with native FreeBSD apps.
Milkyway@Home. Don't know why, but it's not in the normal list, but it has native freebsd i386 and amd64 support. If I had any kind of clue, I'd suggest a port for it, but as it is I've just installed in manually.
RE: There sure hasn't been
)
There probably aren't many of us, but I've got more than 20 machines running FreeBSD.
The SSE version is a great improvement. Thanks for the updated app, Bernd!
RE: There sure hasn't been
)
No no - but BSD-People barely have time for computers or even forums (except they have questions ;-).
However, I am running 4.34 on a P3 dual and require roundabout 115,000.00 CPU-secs.
RE: RE: There sure hasn't
)
That's excatly why I'm writing this... :-)
I have problems getting the client to run on a recent 7-stable/amd64. It reports
5.10.32
process exited with code 193 (0xc1, -63)
2008-06-26 02:37:45.2684 [normal]: Built at: Feb 19 2008 19:44:48
2008-06-26 02:37:45.2685 [normal]: Start of BOINC application 'einstein_S5R3_4.34_i386-unknown-freebsd'.
Fatal error 'can not create signal daemon thread!
' at line 236 in file /usr/releng_5_4/src/lib/libpthread/thread/thr_sig.c (errno = 22)
SIGABRT: abort called
Exiting...
]]>
Any ideas how to fix this?
cu
Gerrit
RE: RE: RE: There sure
)
Not really, I'm getting this error too (FreeBSD 7.0R/amd64/einstein-4.34).
What does your /etc/libmap.conf and /etc/libmap32.conf contain?
According to the port version (4.18) there should be a mapping from libpthread.so.1 to libc_r.so.5 in /etc/libmap32.conf
According to the manual page for errno, value 22 means EINVAL (some passed argument to a function is invalid).
I've asked the maintainer but he doesn't know either, but according to him it runs fine on FreeBSD 6.x/amd64 (I've never tried that myself).
>>Any ideas how to fix
)
>>Any ideas how to fix this?
>Not really, I'm getting this error too (FreeBSD 7.0R/amd64/einstein-4.34).
>What does your /etc/libmap.conf and /etc/libmap32.conf contain?
>According to the port version (4.18) there should be a mapping from >libpthread.so.1 to libc_r.so.5 in /etc/libmap32.conf
I started off with no libmap.conf at all when I first saw the error. After reading the port message I tried
mclane# cat /etc/libmap.conf
libpthread.so.1 libc_r.so.5
libpthread.so libc_r.so
However, without any success. The error remains the same.
>According to the manual page for errno, value 22 means EINVAL (some passed >argument to a function is invalid).
>I've asked the maintainer but he doesn't know either, but according to him it >runs fine on FreeBSD 6.x/amd64 (I've never tried that myself).
I don't have any 6.x/amd64 here, either.
cu
Gerrit
No, we're not dead yet :) but
)
No, we're not dead yet :) but I admit I have paid little attention to BOINC past few months.
Right now I'm working on updating the client port to 6.2.14, and I'm eager to see S5R4 app for FreeBSD in the future.
RE: No, we're not dead yet
)
Thank you Pav for your work on the Boinc ports, I only have a single, solitary FreeBSD machine but it's nice to be able to do something useful with it while it's sitting unused. So how long does it tend to take for FreeBSD versions of apps to appear?
It has been a couple of weeks
)
It has been a couple of weeks in the past.
My machines are idling right now, unfortunately. SIMAP is out of work, I don't do SETI for political reasons, Linux apps gets hung on completion so they require babysitting I can't give them, and I don't know any other project with native FreeBSD apps.
Milkyway@Home. Don't know
)
Milkyway@Home. Don't know why, but it's not in the normal list, but it has native freebsd i386 and amd64 support. If I had any kind of clue, I'd suggest a port for it, but as it is I've just installed in manually.
See here: http://milkyway.cs.rpi.edu/milkyway/forum_thread.php?id=217
Oh great, I'm already on it.
)
Oh great, I'm already on it. Seems operational on my i386, will put it on my amd64 later, too. The port is under works too.