Installing the client in linux

Message boards : BOINC client : Installing the client in linux
Message board moderation

To post messages, you must log in.

AuthorMessage
Carren

Send message
Joined: 15 Jan 06
Posts: 9
New Zealand
Message 2609 - Posted: 15 Jan 2006, 5:28:30 UTC

I just downloaded the linux version and followed the instructions for intalling a self-extracting archive, but when I type in the

<i>sh boinc_5.2.13_i686-pc-linux-gnu.sh<i> command it tells me that directory doesn't exist. I thought that command was supposed to create the directory?

Can someone please tell me how to do this?

ID: 2609 · Report as offensive
James Drews

Send message
Joined: 6 Jan 06
Posts: 38
United States
Message 2677 - Posted: 20 Jan 2006, 16:56:40 UTC - in response to Message 2609.  

I just downloaded the linux version and followed the instructions for intalling a self-extracting archive, but when I type in the

<i>sh boinc_5.2.13_i686-pc-linux-gnu.sh<i> command it tells me that directory doesn't exist. I thought that command was supposed to create the directory?

Can someone please tell me how to do this?


After you downloaded the file, did you chmod it so it is executable?
chmod 550 boinc_5.2.13_i686-pc-linux-gnu.sh

The other probem may be that the shell (sh) isn't in your path. It usually lives in /bin, so you could type /bin/sh boinc_5.2.13_i686-pc-linux-gnu.sh (but I still think it needs to be chmod'd first)

James
ID: 2677 · Report as offensive
Carlos_Pfitzner
Avatar

Send message
Joined: 14 Jan 06
Posts: 18
Brazil
Message 2688 - Posted: 21 Jan 2006, 11:48:11 UTC
Last modified: 21 Jan 2006, 11:52:00 UTC

chmod 744 boinc_5.2.13_i686-pc-linux-gnu.sh
./boinc_5.2.13_i686-pc-linux-gnu.sh

do works -:)

my problem is that on Red Hat Linux 7.2 (enigma)
after I do:
cd BOINC
./boinc -redirectio &

It claims that it needs a libc.so.6 compiled with some special gcc version
and ends
---> gcc 3.0 if I remember correctly

What I have is
crobertp [/home/boinc] > ls /lib/libc* -l
-rw-r--r-- 1 root root 1230116 Oct 13 2004 /lib/libc-2.2.2.so
lrwxrwxrwx 1 root root 13 Oct 18 2004 /lib/libc.so.6 -> libc-2.2.2.so

and when I place there (on /lib) that required libc the whole system
stops working (not even boot)

-> Then, I need to boot from the cd-room, to restore the original libc
and get the whole system working again

however ./boinc_cmd --get_state

do works -> this one does not require that special gcc version

So, I am asking here why ./boinc needs a special gcc version
while ./boinc_cmd do works with existing gcc library(s)

Otherwise, why not compile/distribute ./boinc static linked ?

Thanks
Click signature for team stats
ID: 2688 · Report as offensive
Metod, S56RKO

Send message
Joined: 9 Sep 05
Posts: 128
Slovenia
Message 2778 - Posted: 26 Jan 2006, 15:05:41 UTC - in response to Message 2688.  
Last modified: 26 Jan 2006, 15:07:19 UTC

chmod 744 boinc_5.2.13_i686-pc-linux-gnu.sh
./boinc_5.2.13_i686-pc-linux-gnu.sh

do works -:)

my problem is that on Red Hat Linux 7.2 (enigma)
after I do:
cd BOINC
./boinc -redirectio &

It claims that it needs a libc.so.6 compiled with some special gcc version
and ends
---> gcc 3.0 if I remember correctly


This means that boinc executable was created on a linux machine with fairly recent software installed. It's quite normal to assume that majority of users will run more or less updated systems as this is good for security of their systems. If one assumes that, then there's no need to distribute statically linked binaries as this would mean much increased size of software packages.

There are some custom-compiled versions of boinc CC available on net and at least some of them are statically linked.
Metod ...
ID: 2778 · Report as offensive
Metod, S56RKO

Send message
Joined: 9 Sep 05
Posts: 128
Slovenia
Message 2779 - Posted: 26 Jan 2006, 15:06:40 UTC - in response to Message 2778.  
Last modified: 26 Jan 2006, 15:07:04 UTC

Double post.
Metod ...
ID: 2779 · Report as offensive

Message boards : BOINC client : Installing the client in linux

Copyright © 2024 University of California.
Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation.