[pkg-boinc-devel] BOINC Compile failed

Peter Stoddard peter at stoddard.name
Tue Mar 21 19:45:44 UTC 2006


On Monday 20 March 2006 12:43 am, you wrote:
> Hi Peter,
>
> Am Montag 20 März 2006 06:42 schrieb Peter Stoddard:
> > deb-src http://pkg-boinc.alioth.debian.org/debian/ sarge main
> >
> > to /etc/apt/sources.list, and executed the command
> >
> > # apt-get build-dep boinc
> >
> > Everything seemed to go fine.
> >
> > Then I tried to compile the boinc client but it didn't work.  I followed
> > the instructions in the wiki, which advised sending failed build
> > experiences to this list.
> >
> > Here are some things I did to prepare for the build:
> >
> > ##############################
> >
> > # /usr/bin/gcc --version
> > gcc (GCC) 3.3.5 (Debian 1:3.3.5-13)
> >
> > # export CXXFLAGS=CFLAGS
> > # export CFLAGS="-mtune=pentium-4"
>
> Hm. From "man gcc" this is pentium4 not pentium-4. I would try without
> though. Also, consider to have the CXXFLAGS=CFLAGS setting after the
> setting of the CFLAGS, also it is $CFLAGS since you want the contents of
> the variable, not its name to be assigned ... which actually may be a cause
> of the problems observed.
>
> > ##############################
> >
> > The Debian wiki cited above recommended setting the environmental
> > variables CFLAGS and CXXFLAGS.  I made the =pentium-4 part up because I
> > have no idea what value to put in the variable CFLAGS.
> >
> > I tried the build and it choked on the "rfakeroot" option:
>
> apt-get install fakeroot
>
> Since you are apparently building as root, this should not be required,
> though.
>
> If problems prevail, first set the CFLAGS and CXXFLAGS to "" in order to
> reduce complexity ... or use the default binaries :-)
>
> Good luck.
>
> Steffen

Steffen, thanks for the information.  I built the package and installed it, 
and now the daemon is running and I have successfully bound to SETI at home.  
But now I have a new problem.

Here are a couple of entries from my /var/lib/boinc-client/stdoutdae.txt

##############################

2006-03-20 09:53:17 [---] Starting BOINC client version 5.2.5 for 
x86_64-pc-linux-gnu

2006-03-20 10:34:58 [SETI at home] Message from server: platform 
'x86_64-pc-linux-gnu' not found

##############################

I googled this error message and found a discussion on the 
http://einstein.phys.uwm.edu/ forum which took place in March 2005 when Wurgl 
made the comment:

##############################

"There is ?currently? no 64 bit application available. Can you try to compile 
boinc in 32 bit mode?
 
 It should identify the host as i686-pc-linux-gnu."

##############################

Is this still true?

If I want to use dpkg-buildpackage, should I use something like:

dpkg-buildpackage -us -uc -aarchitecture=i686-pc-linux-gnu ???

Or maybe you can suggest a better way to satisfy the server.  I looked at 
the /etc/default/boinc-client and "man boinc" but didn't see anything about 
how to get the daemon to start in 32 bit or 64 bit mode.

I would value some advice here, because if I just try different things I have 
to wait 24 hours each time to see if it worked.

From the dpkg-buildpackage man page:

##############################

-aarchitecture
Specify  the  Debian  architecture  we  build  for. The architecture of the 
machine we build on is determined automatically, and is also the default for 
the host machine.

##############################

Thanks again for your help.

Pete



More information about the pkg-boinc-devel mailing list