On 9/10/22 11:42, Arve Barsnes wrote:
On Sat, 10 Sept 2022 at 17:28, Jack<[email protected]> wrote:
Any thoughts or suggestions?
I feel like this is an error that tends to pop up when your toolchain
is broken. Are you able to re-emerge gcc?
gcc11.3.0 re-emerge with no errors, bug the problem remains.
I note that in configure, line 2977 is 'ac_files="a.out conftest.exe
conftest a.exe a_out.exe b.out conftest.*"' but the test compilation
creates the output file "g" so configure seems to think that the compile
didn't produce any executable. Using the same compile line but
switching x86_64-pc-linux-gnu-gcc to gcc produces a.out. Further
searching makes me wonder if the configure itself for these two packages
is just based on some starting point too old for gcc11, but that line
is the same in every package I currently still have present in
/var/tmp/portage.
This leaves me wondering why gcc and x86_64-pc-linux-gnu-gcc use
different default output file names.
