Because I'm using 32bit FreeBSD on Pentium4 machine I suppose I don't need to install a 64bit library.

I tried to run some wcg exec manually and I got following error:
ELF binary type "0" not known.
./wcg_hcc1_img_6.03_i686-pc-linux-gnu: Exec format error. Binary file not executable.

next I changed ABI type in ELF header by brand -t Linux wcg_hcc1_img_6.03_i686-pc-linux-gnu command and I got another error:
ERROR: Invalid number of arguments.Segmentation fault (core dumped)

So It looks like the ABI type in header causes on my PC. It seems if you want to run a linux application on freebsd ABI in header has to be set to Linux.

Anyway it doesn't solve my problem because for security the boinc always checks checksum of any exec files before to run it. Therefor if I change ABI type manually the boinc won't run it.

Please correct me if I mistake.

Thank in advance,
Maxim

Hello Maxim.Maslennikov,
I am not a Linux guru, but I do know that the problem that hits people again and again on Linux is installation. It is difficult to install Linux packages. If you click on Search (on the bar between My Forum Profile and Rules) then search for FreeBSD, you will pull up numerous threads where Didactylos tells people to install with Synaptic or try sudo. He tells them to use ldd to locate uninstalled or mis-installed dependencies. So far you have been telling us remedial actions that you have taken but you have not described your installation process step-by-step. Since installation is the great weakness of Linux, this is a key check list. There are several step-by-step check lists for installing BOINC. Which one did you use?

Lawrence

Hello Maxim.Maslennikov,
Correct. We have Linux32 applications and a Linux install package for BOINC, but mostly we depend on people finding ways to run BOINC on different distro's. Use Search to locate the different threads on our Forum. A few include links to step-by-step instructions. Use Google to search the web for BOINC and FreeBSD.

Lawrence

Something is hosed on your system but don't know what.

- Get the appropriate BOINC 6.2.15 package as 6.2.14 was very short lived.
- WCG requires secure communications enabled.
- WCG needs the specific 32 bit libraries... I don't know if they come standard, even on a 32 bit system.
- Detach from WCG in BOINC and re-attach. That should delete all WCG related files except a few like the account file and re-download all science applications anew.

found a thread discussing your error at SETI, but -254 is nowhere mentioned, just a FreeBSD error "process exited with code 2 (0x2, -254)"

sorry, don't know what else.