[Boost-build]/[bjam] Problem compiling CVS bjam from sources
As far as I'm aware I'm using pretty much a default ubuntu installation with gcc 4.1.2. After compiling bjam from sources, using thesehttp://boost.org/boost-build2/doc/html/jam/building.htmlinstructions, and running the tests, I get the following failures: root@---------:/usr/local/src/boost/tools/jam/test# sh test.sh
--- Testing SHELL builtin... --- Testing W32_GETREGNAMES builtin... --- Testing var expansion... --- Testing var on target semantics... --- Testing var expansion... var_expand.jam:14: error: [FAILED] (==) '' var_expand.jam:17: error: [FAILED] (==) '' --- Complete: PASSED(21) *FAILED(2)*
The output from the compilation is below (it seems to work, even with the lists of warnings): root@hallah:/usr/local/src/boost/tools/jam# cd src | sh ./build_dist.sh
../../../Jamfile.v2:335: in load-aux rule path.glob-tree unknown in module Jamfile. /usr/share/boost-build/build/project.jam:318: in load-jamfile /usr/share/boost-build/build/project.jam:68: in load /usr/share/boost-build/build/project.jam:120: in load-parent /usr/share/boost-build/build/project.jam:447: in initialize /usr/share/boost-build/build/project.jam:301: in load-jamfile /usr/share/boost-build/build/project.jam:68: in load /usr/share/boost-build/build/project.jam:120: in load-parent /usr/share/boost-build/build/project.jam:447: in initialize /usr/share/boost-build/build/project.jam:301: in load-jamfile /usr/share/boost-build/build/project.jam:68: in load /usr/share/boost-build/build/project.jam:170: in project.find /usr/share/boost-build/build-system.jam:148: in load /usr/share/boost-build/kernel/modules.jam:261: in import /usr/share/boost-build/kernel/bootstrap.jam:132: in boost-build /usr/local/src/boost/boost-build.jam:9: in module scope cp: cannot stat `html/*': No such file or directory ### ### Using 'gcc' toolset. ### rm -rf bootstrap mkdir bootstrap gcc -o bootstrap/jam0 command.c compile.c debug.c execunix.c expand.c fileunix.c glob.c hash.c hdrmacro.c headers.c jam.c jambase.c jamgram.c lists.c make.c make1.c newstr.c option.c parse.c pathunix.c pathvms.c regexp.c rules.c scan.c search.c subst.c timestamp.c variable.c modules.c strings.c filesys.c builtins.c pwd.c class.c native.c w32_getreg.c modules/set.c modules/path.c modules/regex.c modules/property-set.cmodules/sequence.c modules/order.c execnt.c filent.c compile.c: In function 'compile_set': compile.c:1151: warning: passing argument 2 of 'assign_var_mode' from incompatible pointer type compile.c: In function 'compile_settings': compile.c:1244: warning: passing argument 2 of 'assign_var_mode' from incompatible pointer type ./bootstrap/jam0 -f build.jam --toolset=gcc --toolset-root= clean ...found 1 target... ...updating 1 target... ...updated 1 target... ./bootstrap/jam0 -f build.jam --toolset=gcc --toolset-root= ...found 46 targets... ...updating 2 targets... [MKDIR] bin.linuxx86 [COMPILE] bin.linuxx86/bjam compile.c: In function 'compile_set': compile.c:1151: warning: passing argument 2 of 'assign_var_mode' from incompatible pointer type compile.c: In function 'compile_settings': compile.c:1244: warning: passing argument 2 of 'assign_var_mode' from incompatible pointer type hash.c: In function 'hash_search': hash.c:126: warning: pointer targets in passing argument 1 of 'strlen' differ in signedness hash.c:126: warning: pointer targets in passing argument 2 of '__builtin_strcmp' differ in signedness hash.c:126: warning: pointer targets in passing argument 2 of '__builtin_strcmp' differ in signedness hash.c:126: warning: pointer targets in passing argument 1 of 'strlen' differ in signedness hash.c:126: warning: pointer targets in passing argument 2 of '__builtin_strcmp' differ in signedness hash.c:126: warning: pointer targets in passing argument 2 of '__builtin_strcmp' differ in signedness ...updated 2 targets...
Note that the first 10 or so lines of the output above keep coming up when I'm trying to build other boost libraries. What am I doing wrong? --- Darren Garvey
D Garvey wrote:
As far as I'm aware I'm using pretty much a default ubuntu installation with gcc 4.1.2.
After compiling bjam from sources, using thesehttp://boost.org/boost-build2/doc/html/jam/building.htmlinstructions, and running the tests, I get the following failures:
root@---------:/usr/local/src/boost/tools/jam/test# sh test.sh
--- Testing SHELL builtin... --- Testing W32_GETREGNAMES builtin... --- Testing var expansion... --- Testing var on target semantics... --- Testing var expansion... var_expand.jam:14: error: [FAILED] (==) '' var_expand.jam:17: error: [FAILED] (==) '' --- Complete: PASSED(21) *FAILED(2)*
I see this too. Rene, var_expand.jam is written by you. Do you have a chance to look at this failure?
The output from the compilation is below (it seems to work, even with the lists of warnings):
root@hallah:/usr/local/src/boost/tools/jam# cd src | sh ./build_dist.sh
../../../Jamfile.v2:335: in load-aux rule path.glob-tree unknown in module Jamfile.
I don't get those errors. Do you have up-to-date tree? Is this CVS HEAD or RC_1_34_0? Do you have any other version of Boost.Build? Like a version installed from Ubuntu package somewhere in /usr/share/boost-build? You mention you get the same message when building other boost libraries, can you add --debug-configuration to bjam options when building any library and send the output? - Volodya
Hi Vladimir, thanks for the help.
On 1/27/07, Vladimir Prus
The output from the compilation is below (it seems to work, even with the lists of warnings):
root@hallah:/usr/local/src/boost/tools/jam# cd src | sh ./build_dist.sh
../../../Jamfile.v2:335: in load-aux rule path.glob-tree unknown in module Jamfile.
I don't get those errors. Do you have up-to-date tree? Is this CVS HEAD or RC_1_34_0? Do you have any other version of Boost.Build? Like a version installed from Ubuntu package somewhere in /usr/share/boost-build? You mention you get the same message when building other boost libraries, can you add
--debug-configuration
to bjam options when building any library and send the output?
It turns out the version of boost-build in /usr/share was causing the problems. I didn't find any information anywhere that I'd have to remove that folder; is that something worth noting in the docs, or am I the only one to have this trouble? Thanks for the help, Darren Garvey
participants (2)
-
D Garvey
-
Vladimir Prus