| Summary: | dev-libs/boost-1.49.0 clashes with sys-libs/glibc-2.16 | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Diego Elio Pettenò (RETIRED) <flameeyes> |
| Component: | New packages | Assignee: | C++ Team [disbanded] <cpp+disabled> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | arfrever.fta, jrmalaq, Martin.Jansa, patrick, stevan, toralf, xaviermiller |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Bug Depends on: | |||
| Bug Blocks: | 424737 | ||
| Attachments: | boost-1.49.0-xtime.patch | ||
Created attachment 317366 [details, diff]
boost-1.49.0-xtime.patch
This patch fixes the issue.
not a bug in glibc, so not anything for toolchain@g.o to do i can see It's fixed in upstream version 1.50, probably upgrading boost would be better. boost::TIME_UTC has been renamed to boost::TIME_UTC_ in Boost 1.50, which is now available in gentoo-x86. (In reply to comment #4) https://svn.boost.org/trac/boost/ticket/6940 https://svn.boost.org/trac/boost/changeset/78802 *** Bug 429984 has been marked as a duplicate of this bug. *** same issue. I've just installed 1.51.0 from poly-c overlay *** Bug 432586 has been marked as a duplicate of this bug. *** Having the same symptom but while building boost itself (ie dev-libs/boost-1.49.0-r2) shortly after merging sys-libs/glibc-2.16.0. Can attach emerge --info, boost buildlog, etc if requested. *** Bug 440688 has been marked as a duplicate of this bug. *** |
Building sci-visualisation/nonolith-connect (but I guess the same applied to other packages as drizzle failed to find boost!): x86_64-pc-linux-gnu-g++ -o streaming_device/ws_api.o -c -O2 -pipe -ggdb -march=native -ftracer -frecord-gcc-switches -Ilibusb -Iwebsocketpp/src -Wall streaming_device/ws_api.cpp In file included from /usr/include/boost/thread/pthread/mutex.hpp:14:0, from /usr/include/boost/thread/mutex.hpp:16, from /usr/include/boost/thread/pthread/thread_data.hpp:12, from /usr/include/boost/thread/thread.hpp:17, from /usr/include/boost/thread.hpp:13, from usb.cpp:13: /usr/include/boost/thread/xtime.hpp:23:5: error: expected identifier before numeric constant /usr/include/boost/thread/xtime.hpp:23:5: error: expected '}' before numeric constant /usr/include/boost/thread/xtime.hpp:23:5: error: expected unqualified-id before numeric constant /usr/include/boost/thread/xtime.hpp:46:14: error: expected type-specifier before 'system_time' line 23 of that file is the first line of this enum: enum xtime_clock_types { TIME_UTC=1 // TIME_TAI, // TIME_MONOTONIC, // TIME_PROCESS, // TIME_THREAD, // TIME_LOCAL, // TIME_SYNC, // TIME_RESOLUTION }; and of course it's defined now in time.h when ISOC11 is enabled (which seems to be for whatever reason in that case): # ifdef __USE_ISOC11 /* Time base values for timespec_get. */ # define TIME_UTC 1 # endif