Build failed in step 'Installing GMP for host'

[progzone122]

System info

$ uname -a                            
Linux diablo 6.14.4-arch1-2 #1 SMP PREEMPT_DYNAMIC Tue, 29 Apr 2025 09:23:13 +0000 x86_64 GNU/Linux
$ gcc --version
gcc (GCC) 15.1.1 20250425

Error

$ ./gen-tc.sh kindlehf
...
[INFO ]  Installing GMP for host
[EXTRA]    Configuring GMP
[ERROR]    configure: error: could not find a working compiler, see config.log for details
[ERROR]   
[ERROR]  >>
[ERROR]  >>  Build failed in step 'Installing GMP for host'
[ERROR]  >>        called in step '(top-level)'
[ERROR]  >>
[ERROR]  >>  Error happened in: CT_DoExecLog[scripts/functions@378]
[ERROR]  >>        called from: do_gmp_backend[scripts/build/companion_libs/100-gmp.sh@128]
[ERROR]  >>        called from: do_gmp_for_host[scripts/build/companion_libs/100-gmp.sh@58]
[ERROR]  >>        called from: do_companion_libs_for_host[scripts/build/companion_libs.sh@36]
[ERROR]  >>        called from: main[scripts/crosstool-NG.sh@710]
[ERROR]  >>
[ERROR]  >>  For more info on this error, look at the file: 'build.log'
[ERROR]  >>  There is a list of known issues, some with workarounds, in:
[ERROR]  >>      https://crosstool-ng.github.io/docs/known-issues/
[ERROR]  >>
[ERROR]  >> NOTE: Your configuration includes features marked EXPERIMENTAL.
[ERROR]  >> Before submitting a bug report, try to reproduce it without enabling
[ERROR]  >> any experimental features. Otherwise, you'll need to debug it
[ERROR]  >> and present an explanation why it is a bug in crosstool-NG - or
[ERROR]  >> preferably, a fix.
[ERROR]  >>
[ERROR]  >>  If you feel this is a bug in crosstool-NG, report it at:
[ERROR]  >>      https://github.com/crosstool-ng/crosstool-ng/issues/
[ERROR]  >>
[ERROR]  >>  Make sure your report includes all the information pertinent to this issue.
[ERROR]  >>  Read the bug reporting guidelines here:
[ERROR]  >>      http://crosstool-ng.github.io/support/
[ERROR]   
[ERROR]  (elapsed: 6:17.17)
[06:18] / make: *** [/home/diablo/koxtoolchain/build/CT_NG_BUILD/bin/ct-ng:261: build] Ошибка 1

build.log
config.log

[benoit-pierre]

Why not use the pre-built release?

[progzone122]

Why not use the pre-built release?

This I can do at any time, it's important to find out why I can't compile.
I compiled on another computer before and everything was fine. (2 months ago)

[benoit-pierre]

Or use a config that's known to work… (Cf. #52).

What are the contents of GMP's config.log?

[progzone122]

What are the contents of GMP's config.log?

config.log and build.log attached from above

[benoit-pierre]

That config.log looks successful? (configure: exit 0)

Are you sure it's the right one? It looks like the CT-NG one.

[progzone122]

That config.log looks successful? (configure: exit 0)

Are you sure it's the right one? It looks like the CT-NG one.

Yeah, sorry, wrong file

build-gmp-host-x86_64-build_pc-linux-gnu.log

[benoit-pierre]

Is the other machine where it works using an older GCC?

I suspect the problem is GCC 15:

▹ gcc -x c -Wall -Werror -c -o /dev/null - <<<'int t(); int test(void) { return t(2, 4); }'; echo $?
<stdin>: In function ‘test’:
<stdin>:1:34: error: too many arguments to function ‘t’; expected 0, have 2
<stdin>:1:5: note: declared here
1
▹ gcc -x c -dM -P -E - <<<'' | grep __STDC_VERSION__
#define __STDC_VERSION__ 202311L
▹ gcc -x c -std=gnu17 -Wall -Werror -c -o /dev/null - <<<'int t(); int test(void) { return t(2, 4); }'; echo $
0

[benoit-pierre]

In C23, int t(); is now equivalent to int t(void);.

[progzone122]

Is the other machine where it works using an older GCC?

Most likely yes, because Arch Linux is constantly being updated, so I'm pretty sure there was a completely different version of gcc 100% 2 months ago.

[benoit-pierre]

Yep, updated to GCC 15 at the beginning of the month.

[NiLuJe]

Yeah, gcc 15 will require some patching.

[ragnarokxg]

Yeah, gcc 15 will require some patching.

The fix has been implemented a while back ago on the main repo

crosstool-ng/crosstool-ng#2442

[NiLuJe]

I'm aware; we'll resync whenever I have time to do so ;).

[salexan2001]

Just wanted to confirm:

I just built the toolchain with crosstool-ng/crosstool-ng@a3fef85 and the error was gone. (for target pocketbook, arch linux with gcc 15.2.1)