Hi

I\'ve just registered for Burp and wondering if there is a Version for *BSD like Clients planned. At current I\'m recieving an errormessage wich says that my FreeBSD Client is not supported / not found

regards,
Dura-Zell

The plan is to make the linux client as crossplatform as possible to cover both MacOSX and BSD as well as many other PoSIX/*nix variants. The project will not start to distribute binaries for many of these platforms before late betatesting has begun, though. In other words yes, there is planned support, but it will not be added quite yet.

Theoretically the list of supported platforms is limited by these 3 things:
1) What I have access to (I need to be able to compile stuff on that particular platform
2) What BOINC supports (Which is the majority of platforms really)
3) What Blender supports (Which is also the majority of platforms)

Recently 1 was dramatically improved as Sourceforge opened up its compile farm.

Development is done in Windows and Linux environments because making stuff work in Linux means it will pretty much work on everything except Windows - adding a few special cases for Windows and you have a universal client.

Could I help you with the port of the application ?
I have some different Unixes (MacOS on Intel, HP-UX on PARISC and IA64, FreeBSD, NetBSD OpenBSD, Solaris on SPARC and x86, and Linux on SPARC and IA64) running, which I can port it, if you are interested.

bump

Shortly there\'ll be an announcement about what is to happen with the client-side stuff. This includes things as porting and compiling.

I will try to build a FreeBSD binary.

I will try to build a FreeBSD binary.

You should have a look at the changes committed today to both the Glue2 code and the Blender patchset as these are focused somewhat on getting things to work with FreeBSD.

[Edit:] The Glue2 code (the new client) isn\'t listed on the \"Help us code\" page yet. You may find it under /burp/clients/glue2 in CVS.

[Edit2:] Actually you may want to wait a couple of days with the FreeBSD compiling. Several changes are comming up that will make it quite a lot easier.

Ok, glue2 and the blender patchset should now work with FreeBSD. The changes will not be backported to the old client since the new one is going to supersede it anyways...

There are notes specifically for making things work with FreeBSD in the two HOWTO files.

Thank you, Janus. I will try to compile the new version on FreeBSD.
Am I right, that I must use blender 2.43 now ?
Can I let the MacOS client running till I have compiled a the new release ?

Thank you, Janus. I will try to compile the new version on FreeBSD.

Nice

Am I right, that I must use blender 2.43 now ?

Indeed.

Can I let the MacOS client running till I have compiled a the new release ?

Yes of course - if the results are too different they will be rejected by the validator.

I was able to compile blender 2.43 at FreeBSD and MacOS with the patches, but get the same errors on the wrapper, like on MacOS.

But I get some strange behavior with blender on FreeBSD. If it would be linked against the staticly linked libsdl, I get some unresolved symbols. If the dynamicly linked lib would used, it works successfull.

I get a SIGSEGV with glue2 on FreeBSD :
stderr out

<core_client_version>5.4.11</core_client_version>
<message>
process exited with code 193 (0xc1)
</message>
<stderr_txt>
----------------------------
GLUE
----------------------------
Detected input arg: argv[0] is blender_4.50_i686-unknown-freebsd
Detected input arg: argv[1] is blender
Detected input arg: argv[2] is -b
Detected input arg: argv[3] is in.blend
Detected input arg: argv[4] is -f 208 0.75 0.5 0.78125 1
$Id: BOINCHandler.cpp,v 1.1 2007/04/03 13:12:34 jbk Exp $
boinc_init_diagnostics() completed
boinc_init_options() completed
Basename: blender_4.50_i686-unknown-freebsd --> blender_4.50_i686-unknown-freebsd
Mapping logical files to physical destinations:
in => ../../projects/burp.boinc.dk/368in0.zip
out.zip => ../../projects/burp.boinc.dk/368in0.zip__ses0000000368_frm0000000208_prt00056.wu_3_0
blender_4.50_i686-unknown-freebsd.zip => ../../projects/burp.boinc.dk/blender_4.50_i686-unknown-freebsd.zip
./linux_zip => ../../projects/burp.boinc.dk/linux_zip
./linux_unzip => ../../projects/burp.boinc.dk/linux_unzip
Decompressing input...
Running ../../projects/burp.boinc.dk/linux_unzip -o ../../projects/burp.boinc.dk/368in0.zip
runcmd(../../projects/burp.boinc.dk/linux_unzip -o ../../projects/burp.boinc.dk/368in0.zip) exitted with exit code 0
Decompressing executable archive...
Running ../../projects/burp.boinc.dk/linux_unzip -o ../../projects/burp.boinc.dk/blender_4.50_i686-unknown-freebsd.zip
runcmd(../../projects/burp.boinc.dk/linux_unzip -o ../../projects/burp.boinc.dk/blender_4.50_i686-unknown-freebsd.zip) exitted with exit code 0
CHMODing executable...
Creating worker...
Worker constructing...
Worker constructed.
$Id: glue.cpp,v 1.2 2007/04/04 12:09:26 jbk Exp $
$Id: BOINCHandler.cpp,v 1.1 2007/04/03 13:12:34 jbk Exp $
$Id: Controller.cpp,v 1.2 2007/04/04 16:21:04 jbk Exp $
$Id: ProgressMonitor.cpp,v 1.2 2007/04/04 06:43:59 jbk Exp $
Executing ./blender -b ./in.blend -f 208 0.75 0.5 0.78125 1
Child created.
Worker thread started
Worker thread monitor almost up.
Worker thread monitor up.
SIGSEGV: segmentation violation

Exiting...

</stderr_txt>


Do you have any idea what\'s wrong ?

I have build a FreeBSD (x86) binary package. It is available at www.dotsch.de/burp. It includes the newest patched blender and the old glue version 1. The binaries should run on all FreeBSD 5.x and 6.x releases on i386 or better.