Re: [jamboost] bjam in gcc 2.95

From: Rene Rivera (grafik.list_at_[hidden])
Date: 2005-06-25 09:51:20

Jeremy Swigart wrote:
> Apologies for not clarifying. I'm acting as middle man
> for a friend who is the one doing most of our linux
> stuff. Here is what he says.
> 
> When trying to run build.sh by just typing
> "./build.sh" it gives a "bad interpreter error". 

OK, so /bin/sh is not a valid shell?

> When
> using "sh ./build.sh" (like in the boost docs), it
> returns several "unknown command" errors followed by a

We know about those, and just recently fixed them :-)

> syntax error near the first defined function in the
> script (specifying the toolset like "sh ./build.sh
> gcc" shows the same behaviour).

Hmm, there isn't that much difference between sarge and woody when it 
comes to the shell. Maybe: "bash ./build.sh" would work better in case 
you have some other "sh" floating around.

> We don't need gcc-2.95, we need glibc-2.2. That is not
> directly related. For example Woody uses gcc-2.95 or
> gcc-3.04 and Suse uses gcc-3.2. Both with glibc-2.2.5.

OK getting back to sarge vs. woody. Here's what you can do:

* _In sarge_ change the build.jam as I mentioned earlier to build a 
static version of bjam. Something like this diff (sorry I can't be 
certain this is the exact diff as you still didn't tell me what version 
you have):

Index: build.jam
===================================================================
RCS file: /cvsroot/boost/boost/tools/build/jam_src/build.jam,v
retrieving revision 1.67
diff -u -r1.67 build.jam
--- build.jam 19 Jun 2005 19:39:53 -0000 1.67
+++ build.jam 25 Jun 2005 14:46:07 -0000
@@ -100,7 +100,7 @@
[ opt --debug : -g -O0 -fno-inline -pg ] ;
## GCC 2.x, 3.x
toolset gcc gcc : "-o " : -D
- : -pedantic
+ : -pedantic -static
[ opt --release : [ opt --symbols : -g : -s ] -O3 -finline-functions ]
[ opt --debug : -g -O0 -fno-inline ] ;
## GCC 2.x, 3.x on CYGWIN but without cygwin1.dll
===================================================================

* Build a bjam with that which should produce a rather large 500K 
executable. And copy that to your woody machine.

-- 
-- Grafik - Don't Assume Anything
-- Redshift Software, Inc. - http://redshift-software.com
-- rrivera/acm.org - grafik/redshift-software.com
-- 102708583/icq - grafikrobot/aim - Grafik/jabber.org