EugeneTheJeep
Tux's lil' helper
Joined: 17 May 2017
Posts: 101
|
 Posted: Wed Dec 06, 2017 12:32 pm Post subject: sys-libs/libcxxrt fails to compile after 17.0 profile switch |
 |
|
Hello,
A lot of dust yet to settle after the profile switch. Mine went fairly well except for sys-libs/libcxxrt failing to compile.
I used these instructions from the news item:
| Code: |
If you are not already running a hardened setup with PIE enabled, then
switching the profile involves the following steps:
If not already done,
* Use gcc-config to select gcc-6.4.0 or later as system compiler
* Re-source /etc/profile:
. /etc/profile
* Re-emerge libtool
emerge -1 sys-devel/libtool
Then,
* Select the new profile with eselect
* Re-emerge, in this sequence, gcc, binutils, and glibc
emerge -1 sys-devel/gcc:6.4.0
emerge -1 sys-devel/binutils
emerge -1 sys-libs/glibc
* Rebuild your entire system
emerge -e @world
|
Only change I made was to add --keep-going.
Last few items of sys-libs/libcxxrt are:
| Code: |
stdexcept.So: In function `std::exception::~exception()':
stdexcept.cc:(.text+0xf3): undefined reference to `operator delete(void*, unsigned long)'
stdexcept.So: In function `std::bad_alloc::~bad_alloc()':
stdexcept.cc:(.text+0x113): undefined reference to `operator delete(void*, unsigned long)'
stdexcept.So: In function `std::bad_cast::~bad_cast()':
stdexcept.cc:(.text+0x133): undefined reference to `operator delete(void*, unsigned long)'
stdexcept.So: In function `std::bad_typeid::~bad_typeid()':
stdexcept.cc:(.text+0x153): undefined reference to `operator delete(void*, unsigned long)'
stdexcept.So: In function `std::bad_array_new_length::~bad_array_new_length()':
stdexcept.cc:(.text+0x173): undefined reference to `operator delete(void*, unsigned long)'
typeinfo.So:typeinfo.cc:(.text+0x347): more undefined references to `operator delete(void*, unsigned long)' follow
collect2: error: ld returned 1 exit status
make: *** [Makefile:20: libcxxrt.so.1] Error 1
* ERROR: sys-libs/libcxxrt-0.0_p20160922::gentoo failed (compile phase):
* emake failed
*
* If you need support, post the output of `emerge --info '=sys-libs/libcxxrt-0.0_p20160922::gentoo'`,
* the complete build log and the output of `emerge -pqv '=sys-libs/libcxxrt-0.0_p20160922::gentoo'`.
* The complete build log is located at '/var/tmp/portage/sys-libs/libcxxrt-0.0_p20160922/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/sys-libs/libcxxrt-0.0_p20160922/temp/environment'.
* Working directory: '/var/tmp/portage/sys-libs/libcxxrt-0.0_p20160922/work/libcxxrt-0.0_p20160922-abi_x86_64.amd64/src'
* S: '/var/tmp/portage/sys-libs/libcxxrt-0.0_p20160922/work/libcxxrt-0.0_p20160922'
|
Anyone else run into this and if so, how did you handle it? Otherwise, does anybody have suggestions on how I should proceed?
EDIT:
I see that it is filed as a bug report at
https://bugs.gentoo.org/632186
So I guess I should just wait for a bugfix? He was right about not being the only one...
Last edited by EugeneTheJeep on Wed Dec 06, 2017 1:06 pm; edited 1 time in total |
|
Portage & Programming
