| View previous topic :: View next topic |
| Author |
Message |
jyoung
Guru
Joined: 20 Mar 2007
Posts: 481
|
 Posted: Sat Mar 01, 2025 2:04 am Post subject: |
 |
|
Folks, I'm nearly through the profile migration, but I'm stuck on the final step of emerge --emptytree. For some reason, sys-devel/gcc-14.2.1_p20241221 is failing to compile. I'm copying the error below. This bug is different enough from the original topic of this thread that it might warrant forking off into a new thread, but perhaps someone can spot an obvious issue? I've previously migrated two other machines without issue, and it's weird that gcc of all things would fail to compile.
| Code: | /var/tmp/portage/sys-devel/gcc-14.2.1_p20241221/temp/ccVhvw77.ltrans105.ltrans.o(.text+0x369bd): relocation R_X86_64_GOTPC32_TLSDESC against `cfun' must be used in LEA only
/usr/x86_64-pc-linux-gnu/bin/ld: failed to set dynamic section sizes: bad value
collect2: error: ld returned 1 exit status
make[3]: *** [/var/tmp/portage/sys-devel/gcc-14.2.1_p20241221/work/gcc-14-20241221/gcc/cp/Make-lang.in:145: cc1plus] Error 1
make[3]: *** Waiting for unfinished jobs....
rm gfdl.pod gcc.pod gfortran.pod gcov-dump.pod gcov-tool.pod fsf-funding.pod gpl.pod cpp.pod gcov.pod lto-dump.pod
make[2]: *** [Makefile:4876: all-stageprofile-gcc] Error 2
make[1]: *** [Makefile:24632: stageprofile-bubble] Error 2
make: *** [Makefile:24870: profiledbootstrap] Error 2
* ERROR: sys-devel/gcc-14.2.1_p20241221::gentoo failed (compile phase):
* emake failed
|
|
|
| Back to top |
|
 |
logrusx
Advocate
Joined: 22 Feb 2018
Posts: 2768
|
| Posted: Sat Mar 01, 2025 5:45 am Post subject: |
|
|
First, I guess you didn't read the news item carefully. I'm guilty of that too.
Second, use the binhost. All that compilation and fixing the breakages is unnecessary. It also takes a lot of time. It took me nearly 6 hours and a half for ~1500 packages when more than 2/3 of them were binary. And I have decent hardware with enough RAM, good CPU and an SSD disk.
Best Regards,
Georgi
Last edited by logrusx on Sat Mar 01, 2025 12:29 pm; edited 1 time in total |
|
| Back to top |
|
|
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 54940
Location: 56N 3W
|
| Posted: Sat Mar 01, 2025 11:08 am Post subject: |
|
|
jyoung,
When you build gcc it bootstraps itself. That means it builds three times.
1. gcc is built with any random C/C++ on the system. It need not be gcc
2. The gcc C/C++ compiler from 1. is used to build gcc C/++, so its now built with itself.
3. The gcc C/C++ from stage 2 builds gcc C/C++ again. This gcc C/C++ should be identical to the output from stage 2. If not the build fails.
Stage 3 continues by building all the languages you have asked for. This then gets installed.
When can see you have a linker error but not at which stage the build failed. For that we need the command that invoked the fail.
I'll infer its well into stage 3 from | Code: | | rm gfdl.pod gcc.pod gfortran.pod gcov-dump.pod gcov-tool.pod fsf-funding.pod gpl.pod cpp.pod gcov.pod lto-dump.pod |
which mentions fortran.
Fortran is not built in the first two stages. Only C and C++, which is all that's needed to build gcc.
The entire build log would be good.
Hmm ...
| Code: | make[2]: *** [Makefile:4876: all-stageprofile-gcc] Error 2
make[1]: *** [Makefile:24632: stageprofile-bubble] Error 2
make: *** [Makefile:24870: profiledbootstrap] Error 2 |
Profile Guided Optiminisation?
Don't do that to gcc.
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Portage & Programming
