On 7 Jul 2008, dave@boostpro.com wrote:
boost_1_35_0$ ./configure --with-toolset=gcc-3.3 --prefix=./BUILT
Looks good to me.
Building Boost.Jam with toolset gcc-3.3... ./configure:
./bootstrap/jam0: No such file or directory tools/jam/src//bjam
Urr. Looks like the procedure for building Boost.Jam is using a
Boost.Build toolset name. They are distinct sets. Doug?
[...]
You got the command right; there's a bug in the configure script.
Try changing the line in ./configure that reads
# Determine the toolset, if not already decided
if test "x$TOOLSET" = x; then
so that it reads:
# Determine the toolset, if not already decided
if test "x$TOOLSET" != y; then
This is a hack, but it will build bjam with your system compiler no
matter which toolset you've requested for your Boost build. That
should be fine.
So I made the change to the configure script that you suggested and then
ran it. Things seemed to work okay at first but soon went awry:
------------------------------------
$ ./configure --with-toolset=gcc-3.3 --prefix=./BUILT
Building Boost.Jam with toolset gcc... tools/jam/src/bin.linuxx86/bjam
Detecting Python version... 2.2
Detecting Python root... /usr
Unicode/ICU support for Boost.Regex?... not found.
Backing up existing Boost.Build configuration in user-config.jam.1
Generating Boost.Build configuration in user-config.jam...
Generating Makefile...
$ make install
[...lots of stuff...]
...skipped libboost_serialization-gcc295-mt.so for lack of libboost_serialization-gcc295-mt-1_35.so.1.35.0...
...skipped libboost_wserialization-gcc295-mt.so for lack of libboost_wserialization-gcc295-mt-1_35.so.1.35.0...
common.hard-link BUILT/lib/libboost_signals-gcc295-mt.so
common.hard-link BUILT/lib/libboost_prg_exec_monitor-gcc295-mt.so
...skipped libboost_test_exec_monitor-gcc295-mt.a for lack of libboost_test_exec_monitor-gcc295-mt-1_35.a...
...skipped libboost_unit_test_framework-gcc295-mt.so for lack of libboost_unit_test_framework-gcc295-mt-1_35.so.1.35.0...
...skipped libboost_thread-gcc295-mt.so for lack of libboost_thread-gcc295-mt-1_35.so.1.35.0...
...skipped libboost_wave-gcc295-mt.so for lack of libboost_wave-gcc295-mt-1_35.so.1.35.0...
...skipped libboost_date_time-gcc295-mt.so for lack of libboost_date_time-gcc295-mt-1_35.so.1.35.0...
...skipped libboost_system-gcc295-mt.so for lack of libboost_system-gcc295-mt-1_35.so.1.35.0...
...skipped libboost_filesystem-gcc295-mt.so for lack of libboost_filesystem-gcc295-mt-1_35.so.1.35.0...
...skipped libboost_graph-gcc295-mt.so for lack of libboost_graph-gcc295-mt-1_35.so.1.35.0...
...skipped libboost_iostreams-gcc295-mt.so for lack of libboost_iostreams-gcc295-mt-1_35.so.1.35.0...
...skipped libboost_program_options-gcc295-mt.so for lack of libboost_program_options-gcc295-mt-1_35.so.1.35.0...
...skipped libboost_python-gcc295-mt.so for lack of libboost_python-gcc295-mt-1_35.so.1.35.0...
common.hard-link BUILT/lib/libboost_regex-gcc295-mt.so
...failed updating 57 targets...
...skipped 52 targets...
...updated 5741 targets...
Not all Boost libraries built properly.
------------------------------------
And when I went to look in BUILT/lib, I didn't find many libraries and
the ones I did find claimed that they were for gcc-2.95 (the default)
rather than for the gcc-3.3 compiler I'd specified:
------------------------------------
$ ls BUILT/lib
libboost_prg_exec_monitor-gcc295-mt-1_35.so
libboost_prg_exec_monitor-gcc295-mt-1_35.so.1.35.0
libboost_prg_exec_monitor-gcc295-mt.so
libboost_regex-gcc295-mt-1_35.so
libboost_regex-gcc295-mt-1_35.so.1.35.0
libboost_regex-gcc295-mt.so
libboost_signals-gcc295-mt-1_35.so
libboost_signals-gcc295-mt-1_35.so.1.35.0
libboost_signals-gcc295-mt.so
------------------------------------
More issues in the configure script? Or is there something else I need
to patch?
Thanks!
Dan
