[SOLVED] binutils-2.29.1-r1 fails with +cxx use flag

[OldTango]

Not sure what sets USE="cxx" on binutils-2.29.1-r1, but with that flag set it fails to compile on one of my systems.

Code: Select all

/var/tmp/portage/sys-devel/binutils-2.29.1-r1/work/binutils-2.29.1/gold/output.cc: In member function ‘__gnu_cxx::__normal_iterator<_Iterator, _Container>& __gnu_cxx::__normal_iterator<_Iterator, _Container>::operator++() [with _Iterator = const gold::Output_reloc<9, false, 32, true>*; _Container = std::vector<gold::Output_reloc<9, false, 32, true>, std::allocator<gold::Output_reloc<9, false, 32, true> > >]’:
/var/tmp/portage/sys-devel/binutils-2.29.1-r1/work/binutils-2.29.1/gold/output.cc:5601:1: internal compiler error: Segmentation fault
 } // End namespace gold.
 ^
Please submit a full bug report,
with preprocessed source if appropriate.
See <https://bugs.gentoo.org/> for instructions.
make[4]: *** [Makefile:918: output.o] Error 1
make[4]: *** Waiting for unfinished jobs....

[***]

 * ERROR: sys-devel/binutils-2.29.1-r1::gentoo failed (compile phase):
 *   emake failed
 * 
 * If you need support, post the output of `emerge --info '=sys-devel/binutils-2.29.1-r1::gentoo'`,
 * the complete build log and the output of `emerge -pqv '=sys-devel/binutils-2.29.1-r1::gentoo'`.
 * The complete build log is located at '/var/tmp/portage/sys-devel/binutils-2.29.1-r1/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/sys-devel/binutils-2.29.1-r1/temp/environment'.
 * Working directory: '/var/tmp/portage/sys-devel/binutils-2.29.1-r1/work/build'
 * S: '/var/tmp/portage/sys-devel/binutils-2.29.1-r1/work/binutils-2.29.1'

>>> Failed to emerge sys-devel/binutils-2.29.1-r1, Log file:

Using:

Code: Select all

USE="-cxx" emerge -av binutils

Allows it to build and install without errors but I fear this is not the way to solve the problem.

TIA.....

[dilfridge]

Not sure what sets USE="cxx" on binutils-2.29.1-r1, but with that flag set it fails to compile on one of my systems.

Code: Select all

/var/tmp/portage/sys-devel/binutils-2.29.1-r1/work/binutils-2.29.1/gold/output.cc: In member function ‘__gnu_cxx::__normal_iterator<_Iterator, _Container>& __gnu_cxx::__normal_iterator<_Iterator, _Container>::operator++() [with _Iterator = const gold::Output_reloc<9, false, 32, true>*; _Container = std::vector<gold::Output_reloc<9, false, 32, true>, std::allocator<gold::Output_reloc<9, false, 32, true> > >]’:
/var/tmp/portage/sys-devel/binutils-2.29.1-r1/work/binutils-2.29.1/gold/output.cc:5601:1: internal compiler error: Segmentation fault
 } // End namespace gold.
 ^
Please submit a full bug report,
with preprocessed source if appropriate.
See <https://bugs.gentoo.org/> for instructions.
make[4]: *** [Makefile:918: output.o] Error 1
make[4]: *** Waiting for unfinished jobs....

[...]

 * 
 * If you need support, post the output of `emerge --info '=sys-devel/binutils-2.29.1-r1::gentoo'`,
 * the complete build log and the output of `emerge -pqv '=sys-devel/binutils-2.29.1-r1::gentoo'`.
 * The complete build log is located at '/var/tmp/portage/sys-devel/binutils-2.29.1-r1/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/sys-devel/binutils-2.29.1-r1/temp/environment'.
 * Working directory: '/var/tmp/portage/sys-devel/binutils-2.29.1-r1/work/build'
 * S: '/var/tmp/portage/sys-devel/binutils-2.29.1-r1/work/binutils-2.29.1'

>>> Failed to emerge sys-devel/binutils-2.29.1-r1, Log file:

Using:

Code: Select all

USE="-cxx" emerge -av binutils

Allows it to build and install without errors but I fear this is not the way to solve the problem.

TIA.....

Right ... there's a lot of relevant info missing (gcc version? the actual command that fails?), following above instructions gets you all of it. Also it's probably more helpful to make a report on [bug=]bugs.g.o[/bug] (with that information) ...

[Moderator edit: fixed link. Forum auto-linking guessed the domain as-shown, which does not work. -Hu]

[OldTango]

I managed to solve the problem and get binutils to build properly.

I am not sure what the exact cause was but I believe it was something I missed while updating to the 17.0 profile. So I'm back in business again.

....