Opened 10 years ago
Last modified 10 years ago
#7482 new Bugs
Build from source with MinGW on Windows
Reported by: | Owned by: | timblechmann | |
---|---|---|---|
Milestone: | To Be Determined | Component: | Building Boost |
Version: | Boost Development Trunk | Severity: | Problem |
Keywords: | mingw windows layout system | Cc: |
Description
Hello, I've trying to build boost with mingw, and I've got error, when
--layout=system
option is used.
check out (with cygwin):
> svn co http://svn.boost.org/svn/boost/trunk boost-trunk > svnversion 80897
build (windows cmd.exe):
> g++ --version g++ (Built by MinGW-builds projects) 4.7.1 > cd boost-trunk > .\bootstrap gcc
build with --layout=tagged
works fine:
> .\b2 --toolset=gcc --layout=tagged
but build with --layout=system
failed:
> .\b2 --toolset=gcc --layout=system ... error: Duplicate name of actual target: <pstage\lib>libboost_atomic.a error: previous virtual target { common%common.copy-libboost_atomic.a.STATIC_LIB { gcc%gcc.archive-libboost_atomic.a.STATIC_LIB { gcc%gcc.compile.c++- lockpool.o.OBJ { lockpool.cpp.CPP } } } } error: created from ./stage-proper error: another virtual target { common%common.copy-libboost_atomic.a.STATIC_LIB { gcc%gcc.archive-libboost_atomic.a.STATIC_LIB { gcc%gcc.compile.c++-l ockpool.o.OBJ { lockpool.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 M:/boost-trunk/tools/build/v2/build\virtual-target.jam:491: in actualize-no-scanner from module object(file-target)@4808 M:/boost-trunk/tools/build/v2/build\virtual-target.jam:134: in object(file-target)@4808.actualize from module object(file-target)@4808 M:/boost-trunk/tools/build/v2\build-system.jam:736: in load from module build-system M:\boost-trunk\tools\build\v2/kernel\modules.jam:289: in import from module modules M:\boost-trunk\tools\build\v2/kernel/bootstrap.jam:139: in boost-build from module M:\boost-trunk\boost-build.jam:17: in module scope from module
Change History (4)
comment:1 by , 10 years ago
Component: | Building Boost → atomic |
---|---|
Owner: | set to |
Version: | Boost 1.52.0 → Boost Development Trunk |
comment:2 by , 10 years ago
Component: | atomic → Building Boost |
---|
seems to be a boost.build issue according to: http://permalink.gmane.org/gmane.comp.lib.boost.devel/237614
comment:3 by , 10 years ago
Component: | Building Boost → build |
---|
comment:4 by , 10 years ago
Component: | build → Building Boost |
---|
Vincente, a component of "build" means the ticket is for Boost.Build itself. This is not a problem in Boost.Build. The problem is that Jamroot creates a build request that cannot be satisfied.
Note:
See TracTickets
for help on using tickets.
Atomic will be released on 1.53. Moved to Atomic In case this is an Atomic specific issue.