Go to:
Gentoo Home
Documentation
Forums
Lists
Bugs
Planet
Store
Wiki
Get Gentoo!
Gentoo's Bugzilla – Attachment 339504 Details for
Bug 458404
dev-libs/boost-1.52.0-r5[-threads] fails to build
Home
|
New
–
[Ex]
|
Browse
|
Search
|
Privacy Policy
|
[?]
|
Reports
|
Requests
|
Help
|
New Account
|
Log In
[x]
|
Forgot Password
Login:
[x]
/var/tmp/portage/dev-libs/boost-1.52.0-r5/temp/build.log
build.log (text/plain), 5.06 KB, created by
Thomas Beutin
on 2013-02-20 15:07:45 UTC
(
hide
)
Description:
/var/tmp/portage/dev-libs/boost-1.52.0-r5/temp/build.log
Filename:
MIME Type:
Creator:
Thomas Beutin
Created:
2013-02-20 15:07:45 UTC
Size:
5.06 KB
patch
obsolete
>[32;01m * [39;49;00mPackage: dev-libs/boost-1.52.0-r5 >[32;01m * [39;49;00mRepository: gentoo >[32;01m * [39;49;00mMaintainer: cpp@gentoo.org >[32;01m * [39;49;00mUSE: amd64 elibc_glibc kernel_linux nls python python_targets_python2_7 python_targets_python3_2 userland_GNU >[32;01m * [39;49;00mFEATURES: sandbox >>>> Unpacking source... >>>> Unpacking boost_1_52_0.tar.bz2 to /var/tmp/portage/dev-libs/boost-1.52.0-r5/work >>>> Source unpacked in /var/tmp/portage/dev-libs/boost-1.52.0-r5/work >>>> Preparing source in /var/tmp/portage/dev-libs/boost-1.52.0-r5/work/boost_1_52_0 ... > [32;01m*[0m Applying boost-1.48.0-mpi_python3.patch ... >[A[263C [34;01m[ [32;01mok[34;01m ][0m > [32;01m*[0m Applying boost-1.51.0-respect_python-buildid.patch ... >[A[263C [34;01m[ [32;01mok[34;01m ][0m > [32;01m*[0m Applying boost-1.51.0-support_dots_in_python-buildid.patch ... >[A[263C [34;01m[ [32;01mok[34;01m ][0m > [32;01m*[0m Applying boost-1.48.0-no_strict_aliasing_python2.patch ... >[A[263C [34;01m[ [32;01mok[34;01m ][0m > [32;01m*[0m Applying boost-1.48.0-disable_libboost_python3.patch ... >[A[263C [34;01m[ [32;01mok[34;01m ][0m > [32;01m*[0m Applying boost-1.48.0-python_linking.patch ... >[A[263C [34;01m[ [32;01mok[34;01m ][0m > [32;01m*[0m Applying boost-1.48.0-disable_icu_rpath.patch ... >[A[263C [34;01m[ [32;01mok[34;01m ][0m > [32;01m*[0m Applying remove-toolset-1.48.0.patch ... >[A[263C [34;01m[ [32;01mok[34;01m ][0m > [32;01m*[0m Applying boost-1.52.0-tuple.patch ... >[A[263C [34;01m[ [32;01mok[34;01m ][0m >>>> Source prepared. >>>> Configuring source in /var/tmp/portage/dev-libs/boost-1.52.0-r5/work/boost_1_52_0 ... >>>> Source configured. >>>> Compiling source in /var/tmp/portage/dev-libs/boost-1.52.0-r5/work/boost_1_52_0 ... > [32;01m*[0m python3.2: running building >b2 gentoorelease -j5 -q -d+2 --user-config=/var/tmp/portage/dev-libs/boost-1.52.0-r5/work/boost_1_52_0/user-config.jam --disable-icu boost.locale.icu=off --without-mpi pch=off --boost-build=/usr/share/boost-build --prefix="/var/tmp/portage/dev-libs/boost-1.52.0-r5/image/usr" --layout=system threading=single link=shared --without-context --python-buildid=3.2 > >Building the Boost C++ Libraries. > > >Performing configuration checks > > - has_icu builds : no >warning: Graph library does not contain MPI-based parallel components. >note: to enable them, add "using mpi ;" to your user-config.jam > - iconv (libc) : yes > - gcc visibility : yes > - long double support : yes >/usr/share/boost-build/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.52.0 >error: previous virtual target { common%common.copy-libboost_system.so.1.52.0.SHARED_LIB { gcc%gcc.link.dll-libboost_system.so.1.52.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.52.0.SHARED_LIB { gcc%gcc.link.dll-libboost_system.so.1.52.0.SHARED_LIB { gcc%gcc.compile.c++-error_code.o.OBJ { error_code.cpp.CPP } } } } >error: created from ./stage-proper >error: added properties: <threading>multi <warnings>on >error: removed properties: <threading>single <warnings>all >/usr/share/boost-build/build/virtual-target.jam:490: in actualize-no-scanner from module object(file-target)@3519 >/usr/share/boost-build/build/virtual-target.jam:135: in object(file-target)@3519.actualize from module object(file-target)@3519 >/usr/share/boost-build/build-system.jam:749: in load from module build-system >/usr/share/boost-build/kernel/modules.jam:283: in import from module modules >/usr/share/boost-build/kernel/bootstrap.jam:142: in boost-build from module >/var/tmp/portage/dev-libs/boost-1.52.0-r5/work/boost_1_52_0/boost-build.jam:17: in module scope from module > > [31;01m*[0m ERROR: dev-libs/boost-1.52.0-r5 failed (compile phase): > [31;01m*[0m Building of Boost libraries failed > [31;01m*[0m > [31;01m*[0m Call stack: > [31;01m*[0m ebuild.sh, line 93: Called src_compile > [31;01m*[0m environment, line 3329: Called python_foreach_impl 'building' > [31;01m*[0m environment, line 2956: Called building > [31;01m*[0m environment, line 3299: Called die > [31;01m*[0m The specific snippet of code: > [31;01m*[0m ejam ${OPTIONS} $(use python && echo --python-buildid=${EPYTHON#python}) || die "Building of Boost libraries failed"; > [31;01m*[0m > [31;01m*[0m If you need support, post the output of `emerge --info '=dev-libs/boost-1.52.0-r5'`, > [31;01m*[0m the complete build log and the output of `emerge -pqv '=dev-libs/boost-1.52.0-r5'`. > [31;01m*[0m The complete build log is located at '/var/tmp/portage/dev-libs/boost-1.52.0-r5/temp/build.log'. > [31;01m*[0m The ebuild environment file is located at '/var/tmp/portage/dev-libs/boost-1.52.0-r5/temp/environment'. > [31;01m*[0m Working directory: '/var/tmp/portage/dev-libs/boost-1.52.0-r5/work/boost_1_52_0' > [31;01m*[0m S: '/var/tmp/portage/dev-libs/boost-1.52.0-r5/work/boost_1_52_0'
You cannot view the attachment while viewing its details because your browser does not support IFRAMEs.
View the attachment on a separate page
.
View Attachment As Raw
Actions:
View
Attachments on
bug 458404
: 339504 |
340868
|
364820