Open evilbulgarian opened 4 years ago
https://bugs.gentoo.org/697712 fixed by re-building binutils-libs
For future reference, if something fails in the configuration script, it is not as a result of enabling link-time optimization. The only GCC flag that ever broke any configuration script directly was "-Wall", but that was in the "Checking C++ compiler" step. Some other flags may possibly influence other configuration scripts in this way, but I have not personally come across any such flags other than the one presented above.
Edited for formatting -- @evilbulgarian has this been resolved? It looks like libiberty
wasn't installed correctly, based on the log.
@elsandosgrande FYI: your CFLAGS
can indeed cause things to fail in packages configure scripts. Typically the reason is a poorly written test in those scripts that hasn't been touched in a decade or two (or three). That does include -flto
as well. Just in case you run into issues with getting past the configure
stage. cmake
and meson
projects seem to have much less trouble here.
I just had the same problem after upgrading to GCC 10.1. Re-building binutils-libs
fixes the configure problem, but now it breaks on linking with no error message.
@InBetweenNames
CFLAGS
can cause issues with scripts.