Re: [Boost-build] [build] Problems building release branch

Subject: Re: [Boost-build] [build] Problems building release branch
From: John Maddock (boost.regex_at_[hidden])
Date: 2010-10-24 04:41:19

>>> common.mkdir bin.v2
>>> common.mkdir bin.v2/libs
>>> common.mkdir bin.v2/libs/regex
>>> common.mkdir bin.v2/libs/regex/build
>>> common.mkdir bin.v2/libs/regex/build/gcc-4.1.2
>>> common.mkdir bin.v2/libs/regex/build/gcc-4.1.2/debug
>>> gcc.compile.c++ bin.v2/libs/regex/build/gcc-4.1.2/debug/has_icu_test.o
>>> libs/regex/build/has_icu_test.cpp:26:2: warning: no newline at end of 
>>> file
>>> libs/regex/build/has_icu_test.cpp: In function
>>> int main()
>>>
>>> libs/regex/build/has_icu_test.cpp:24: warning: unused variable
>>> c
>>>
>>> gcc.link bin.v2/libs/regex/build/gcc-4.1.2/debug/has_icu
>>> /usr/bin/ld: skipping incompatible /usr/lib/libicuuc.so when searching 
>>> for
>>> -licuuc
>>> /usr/bin/ld: skipping incompatible /usr/lib/libicui18n.so when searching
>>> for -licui18n
>>> /usr/bin/ld: skipping incompatible /usr/lib/libicudata.so when searching
>>> for -licudata
>>> /usr/bin/ld: skipping incompatible /usr/lib/libm.so when searching 
>>> for -lm
>>> /usr/bin/ld: skipping incompatible /usr/lib/libm.a when searching 
>>> for -lm
>>> /usr/bin/ld: skipping incompatible /usr/lib/libc.so when searching 
>>> for -lc
>>> /usr/bin/ld: skipping incompatible /usr/lib/libc.a when searching 
>>> for -lc
>>> ...updated 8 targets...

Interesting that you're seeing those configuration mesages - they should all 
have been sent to file, and should *not* be seen in console output.

>>> Performing configuration checks
>>>
>>>      - has_icu builds           : yes
>>> /dev/shm/release/tools/build/v2/build/feature.jam:485: in
>>> validate-value-string from module feature
>>> error: "msvc:<linkflags>delayimp.lib" is not a known value of feature
>>> <toolset>

Yep, that line is mine, libs/regex/build/Jamfile.v2 has the requirements:

         <toolset>msvc:<linkflags>/delayload:$(icuucd_name:B).dll
         <toolset>msvc:<linkflags>/delayload:$(icuuc_name:B).dll
         <toolset>msvc:<linkflags>/delayload:$(icudt_name:B).dll
         <toolset>msvc:<linkflags>/delayload:$(icuin_name:B).dll
         <toolset>msvc:<linkflags>/delayload:$(icuind_name:B).dll
         <toolset>msvc:<linkflags>delayimp.lib

added when building with ICU.  But this all works just fine for me here, 
both on Win32 and Ubuntu Linux.  None of the test runners have complained 
either.  Is your bjam executable up to date with source?  Just checking... 
can't think of anything else right now.

BTW, one annoying thing I do see that needs fixing before release, is a load 
of "cruft" coming from the thread Jamfile:

$ bjam --with-regex
THREAD JAMFILE libs\thread\build\Jamfile.v2 34 
Jamfile</M:/data/boost/branches/r
elease/libs/thread/build>. modules.load 
M:/data/boost/branches/release/tools/bui
ld/v2/build\project.jam 310 project. load-jamfile 
M:/data/boost/branches/release
/tools/build/v2/build\project.jam 62 project. project.load 
M:/data/boost/branche
s/release/tools/build/v2/build\project.jam 760 project. project.use 
M:/data/boos
t/branches/release/tools/build/v2/build\project.jam 89 project. 
load-used-projec
ts M:/data/boost/branches/release/tools/build/v2/build\project.jam 73 
project. l
oad M:/data/boost/branches/release/tools/build/v2/build\project.jam 168 
project.
 project.find M:/data/boost/branches/release/tools/build/v2\build-system.jam 
569
 build-system. load 
M:\data\boost\branches\release\tools\build\v2/kernel\modules
.jam 283 modules. import 
M:\data\boost\branches\release\tools\build\v2\kernel\bo
otstrap.jam 142  boost-build M:\data\boost\branches\release\boost-build.jam 
17
module scope

Building the Boost C++ Libraries.

Regards, John.