Re: [Boost-users] [1.35.0] Release Candidate 3 available

From: Stephen Nuchia (snuchia_at_[hidden])
Date: 2008-03-28 13:41:08

This is a showstopper for me right now, though I am by no means an
expert at running bjam.  On a Windows (server 2003) 64-bit platform with
MSVC 9.0 I am trying to build the major permutations of the library in
both 32- and 64-bit variants.  I was able to find command lines that
appear to do the job for the 32-bit, debug/release, shared/static
combinations and for the static combinations in 64-bit mode.

I'm getting the following output when I try to build shared libraries
for 64-bit, with "shared" or "static" or no specification for link and
runtime-link

C:\code\Version9\boost>bjam --toolset=msvc
msvc/architecture=x86/address-model=64/runtime-link=shared/link=shared
debug stage
warning: Graph library does not contain optional GraphML reader.
note: to enable GraphML support, set EXPAT_INCLUDE and EXPAT_LIBPATH to
the
note: directories containing the Expat headers and libraries,
respectively.
warning: skipping optional Message Passing Interface (MPI) library.
note: to enable MPI support, add "using mpi ;" to user-config.jam.
note: to suppress this message, pass "--without-mpi" to bjam.
note: otherwise, you can safely ignore this message.
WARNING: No python installation configured and autoconfiguration
         failed.  See http://www.boost.org/libs/python/doc/building.html
         for configuration instructions or pass --without-python to
         suppress this message and silently skip all Boost.Python
targets
Building Boost.Regex with the optional Unicode/ICU support disabled.
Please refer to the Boost.Regex documentation for more information
(don't panic: this is a strictly optional feature).
Skipping build of:  libs/python/build/boost_python  <build>no in common
properti
es
Skipping build of:  libs/python/build/boost_python  <build>no in common
properti
es
C:/code/Version9/boost/tools/build/v2/build\virtual-target.jam:996: in
virtual-t
arget.register-actual-name from module virtual-target
error: Duplicate name of actual target:
<pstage\lib>boost_date_time-vc90-mt-gd-1
_35.dll
error: previous virtual target {
common%common.copy-boost_date_time-vc90-mt-gd-1
_35.dll.SHARED_LIB {
msvc%msvc.link.dll-boost_date_time-vc90-mt-gd-1_35.dll.SHAR
ED_LIB { msvc%msvc.compile.c++-greg_month.obj.OBJ {
gregorian/greg_month.cpp.CPP
 } } { msvc%msvc.compile.c++-greg_weekday.obj.OBJ {
gregorian/greg_weekday.cpp.C
PP } } { msvc%msvc.compile.c++-date_generators.obj.OBJ {
gregorian/date_generato
rs.cpp.CPP } } } }
error: created from ./stage-proper
error: another virtual target {
common%common.copy-boost_date_time-vc90-mt-gd-1_
35.dll.SHARED_LIB {
msvc%msvc.link.dll-boost_date_time-vc90-mt-gd-1_35.dll.SHARE
D_LIB { msvc%msvc.compile.c++-greg_month.obj.OBJ {
gregorian/greg_month.cpp.CPP
} } { msvc%msvc.compile.c++-greg_weekday.obj.OBJ {
gregorian/greg_weekday.cpp.CP
P } } { msvc%msvc.compile.c++-date_generators.obj.OBJ {
gregorian/date_generator
s.cpp.CPP } } } }
error: created from ./stage-proper
error: added properties: none
error: removed properties: <address-model>64 <architecture>x86
C:/code/Version9/boost/tools/build/v2/build\virtual-target.jam:453: in
actualize
-no-scanner from module object(file-target)@2049
C:/code/Version9/boost/tools/build/v2/build\virtual-target.jam:118: in
object(fi
le-target)@2049.actualize from module object(file-target)@2049
C:/code/Version9/boost/tools/build/v2\build-system.jam:675: in load from
module
build-system
C:\code\Version9\boost\tools\build\v2/kernel\modules.jam:267: in import
from mod
ule modules
C:\code\Version9\boost\tools\build\v2/kernel/bootstrap.jam:132: in
boost-build f
rom module
C:\code\Version9\boost\boost-build.jam:11: in module scope from module

C:\code\Version9\boost>

-----Original Message-----
From: Beman Dawes [mailto:bdawes_at_[hidden]] 
Sent: Friday, March 28, 2008 8:38 AM
To: Boost mailing list; Boost Users mailing list
Subject: [Boost-users] [1.35.0] Release Candidate 3 available

See http://boost.cowic.de/rc/

For this release candidate the naming is exactly the same as it will be 
in the final release. Unless a showstopper emerges, these exact files 
will become the final release.

Before declaring the release done, we need to verify that none of the 
four package files is corrupt and installs without error. I'm starting 
to do that now. I encourage others to also look for showstoppers, and 
report results on the developer or user lists.

If no showstoppers surface by 9 AM tomorrow morning, US Eastern time, 
I'll declare 1.35.0 done, create the tag, and push the files out to 
Sourceforge.

--Beman