Problems installing boost 1.47.0
Hi I'm trying to install boost 1.47 in a single threaded edition but it does not seems to work. Here is what I tried: ./bootstrap.sh --without-icu --without-libraries=graph_parallel,mpi,python ./b2 threading=single --layout=system --prefix=/usr/local Here is the error I got on the second command: Building the Boost C++ Libraries. Performing configuration checks - has_icu builds : yes - ../config//has_gcc_visibility builds : yes - ../config//has_long_double_support builds : yes /storage/src/boost_1_47_0/tools/build/v2/build/virtual-target.jam:1079: in virtual-target.register-actual-name from module virtual-target error: Duplicate name of actual target: <pstage/lib>libboost_system.so.1.47.0 error: previous virtual target { common%common.copy-libboost_system.so.1.47.0.SHARED_LIB { gcc%gcc.link.dll-libboost_system.so.1.47.0.SHARED_LIB { gcc%gcc.compile.c++-error_code.o.OBJ { error_code.cpp.CPP } } } } error: created from ./stage-proper error: another virtual target { common%common.copy-libboost_system.so.1.47.0.SHARED_LIB { gcc%gcc.link.dll-libboost_system.so.1.47.0.SHARED_LIB { gcc%gcc.compile.c++-error_code.o.OBJ { error_code.cpp.CPP } } } } error: created from ./stage-proper error: added properties: <threading>single <warnings>on error: removed properties: <threading>multi <warnings>all /storage/src/boost_1_47_0/tools/build/v2/build/virtual-target.jam:490: in actualize-no-scanner from module object(file-target)@2784 /storage/src/boost_1_47_0/tools/build/v2/build/virtual-target.jam:135: in object(file-target)@2784.actualize from module object(file-target)@2784 /storage/src/boost_1_47_0/tools/build/v2/build-system.jam:749: in load from module build-system /storage/src/boost_1_47_0/tools/build/v2/kernel/modules.jam:283: in import from module modules /storage/src/boost_1_47_0/tools/build/v2/kernel/bootstrap.jam:142: in boost-build from module /storage/src/boost_1_47_0/boost-build.jam:17: in module scope from module Is there anything I can do to fix this locally ?? Best regards Allan W. Nielsen
AMDG On 09/23/2011 02:50 AM, Allan Nielsen wrote:
I'm trying to install boost 1.47 in a single threaded edition but it does not seems to work. Here is what I tried:
./bootstrap.sh --without-icu --without-libraries=graph_parallel,mpi,python ./b2 threading=single --layout=system --prefix=/usr/local
Here is the error I got on the second command:
<snip> error: Duplicate name of actual target: <pstage/lib>libboost_system.so.1.47.0 <snip> error: created from ./stage-proper error: added properties: <threading>single <warnings>on error: removed properties: <threading>multi <warnings>all <snip>
Is there anything I can do to fix this locally ??
Try adding --build-type=minimal to the b2 command line. In Christ, Steven Watanabe
same problem, Windows 7 - 64bit, Visual Studio 2010. first try: D:\Work\boost\boost_1_47_0>bootstrap D:\Work\boost\boost_1_47_0>.\b2 --layout=system --build-dir=builddir --with-date_time --with-exception --with-filesystem --with-iostreams --with-program_options --with-random --with-regex --with-serialization --with-signals --with-system --with-test --with-thread --build-type=minimal second try: D:\Work\boost\boost_1_47_0>bootstrap --with-libraries=date_time,exception,filesystem,iostreams,program_options,random,regex,serialization,signals,system,test,thread D:\Work\boost\boost_1_47_0>.\b2 --layout=system --build-dir=builddir output: D:/Work/boost/boost_1_47_0/tools/build/v2/build\virtual-target.jam:1079: in virtual-target.register-actual-name from module virtual-target error: Duplicate name of actual target: <pstage\lib>libboost_system.lib error: previous virtual target { common%common.copy-libboost_system.lib.STATIC_LIB { msvc%msvc.archive-libboost_system.lib.STATIC_LIB { msvc%msvc.compile.c++-error_code.obj.OBJ { e rror_code.cpp.CPP } } } } error: created from ./stage-proper error: another virtual target { common%common.copy-libboost_system.lib.STATIC_LIB { msvc%msvc.archive-libboost_system.lib.STATIC_LIB { msvc%msvc.compile.c++-error_code.obj.OBJ { er ror_code.cpp.CPP } } } } error: created from ./stage-proper error: added properties: <debug-symbols>off <define>NDEBUG <inlining>full <optimization>speed <runtime-debugging>off <variant>release error: removed properties: <debug-symbols>on <inlining>off <optimization>off <runtime-debugging>on <variant>debug D:/Work/boost/boost_1_47_0/tools/build/v2/build\virtual-target.jam:490: in actualize-no-scanner from module object(file-target)@3726 D:/Work/boost/boost_1_47_0/tools/build/v2/build\virtual-target.jam:135: in object(file-target)@3726.actualize from module object(file-target)@3726 D:/Work/boost/boost_1_47_0/tools/build/v2\build-system.jam:749: in load from module build-system D:\Work\boost\boost_1_47_0\tools\build\v2/kernel\modules.jam:283: in import from module modules D:\Work\boost\boost_1_47_0\tools\build\v2\kernel\bootstrap.jam:142: in boost-build from module D:\Work\boost\boost_1_47_0\boost-build.jam:17: in module scope from module
Hi I just realized that this problem only occurs when boost::chrono is build. Do you think this is a bug in the boost::chrono build script? Best regards Allan W. Nielsen
Le 10/10/11 12:46, Allan Nielsen a écrit :
Hi
I just realized that this problem only occurs when boost::chrono is build.
Do you think this is a bug in the boost::chrono build script?
Hi, currently Boost.Chrono requires multi-threading on Linux. This is surely a bug as I guess all what is needed is to link with the -rt library. The problem is in the build/Jamfile. Could you replace <target-os>linux:<threading>multi by <linkflags>"-lrt" : requirements and : usage-requirements to see if this works for you? Please, could you also create a Trac ticket? Best, Vicente
Le 10/10/11 20:51, Vicente J. Botet Escriba a écrit :
Le 10/10/11 12:46, Allan Nielsen a écrit :
Hi
I just realized that this problem only occurs when boost::chrono is build.
Do you think this is a bug in the boost::chrono build script?
Hi,
currently Boost.Chrono requires multi-threading on Linux. This is surely a bug as I guess all what is needed is to link with the -rt library.
The problem is in the build/Jamfile.
Could you replace
<target-os>linux:<threading>multi
by
<linkflags>"-lrt"
: requirements and : usage-requirements
to see if this works for you?
Please, could you also create a Trac ticket?
I'm trying to solve the issue with the previous proposal. Committed revision 74902. I will see how the regressions behave. Best, Vicente
Okay, sounds good. Just to be sure, have you created the track ticket? Best regards Allan W. Nielsen On Mon, Oct 10, 2011 at 10:00 PM, Vicente J. Botet Escriba < vicente.botet@wanadoo.fr> wrote:
Le 10/10/11 20:51, Vicente J. Botet Escriba a écrit :
Le 10/10/11 12:46, Allan Nielsen a écrit :
Hi
I just realized that this problem only occurs when boost::chrono is build.
Do you think this is a bug in the boost::chrono build script?
Hi,
currently Boost.Chrono requires multi-threading on Linux. This is surely a bug as I guess all what is needed is to link with the -rt library.
The problem is in the build/Jamfile.
Could you replace
<target-os>linux:<threading>**multi
by
<linkflags>"-lrt"
: requirements and : usage-requirements
to see if this works for you?
Please, could you also create a Trac ticket?
I'm trying to solve the issue with the previous proposal.
Committed revision 74902.
I will see how the regressions behave.
Best, Vicente
______________________________**_________________ Boost-users mailing list Boost-users@lists.boost.org http://lists.boost.org/**mailman/listinfo.cgi/boost-**users<http://lists.boost.org/mailman/listinfo.cgi/boost-users>
participants (4)
-
Allan Nielsen -
Roman Shmelev -
Steven Watanabe -
Vicente J. Botet Escriba