| Summary: | sys-devel/gcc-4.4.1 fail to create executables | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Dominique Michel <dominique.c.michel> |
| Component: | [OLD] Core system | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
| Status: | RESOLVED INVALID | ||
| Severity: | normal | CC: | zgredder |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | AMD64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: |
config.log
emerge --info |
||
Created attachment 202908 [details]
config.log
Created attachment 202910 [details]
emerge --info
It is the first time I get this kind of garbage at the end.
output of `gcc-config -l' ? # gcc-config -l [1] x86_64-pc-linux-gnu-3.4.6 * [2] x86_64-pc-linux-gnu-3.4.6-hardened [3] x86_64-pc-linux-gnu-3.4.6-hardenednopie [4] x86_64-pc-linux-gnu-3.4.6-hardenednopiessp [5] x86_64-pc-linux-gnu-3.4.6-hardenednossp [6] x86_64-pc-linux-gnu-4.4.1 I am merging gcc-4.3.4 now. It is why gcc is now 3.4.6. What happens if you switch back to 4.4.1? Will gcc-config complain? No:
# gcc-config x86_64-pc-linux-gnu-4.4.1
* Switching native-compiler to x86_64-pc-linux-gnu-4.4.1...
>>> Regenerating /etc/ld.so.cache... [ ok ]
* If you intend to use the gcc from the new profile in an already
* running shell, please remember to do:
* # source /etc/profile
And it even work now. It is compiling fftw now.
I guess that some dep get lost during "emerge --depclean". And that "revdep-rebuild" with gcc-4.3.4 fixed it.
That's good news. Looks like this bugreport may become closed. [anyone with proper permissions?] |
When compiling, gcc-4.4.1 just fail to create executables. # emerge -vp gcc These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild R ] sys-devel/gcc-4.4.1 USE="fortran gtk libffi mudflap (multilib) nls nptl openmp (-altivec) -bootstrap -build -doc (-fixed-point) -gcj -graphite (-hardened) -ip28 -ip32r10k -multislot (-n32) (-n64) -nocxx -objc -objc++ -objc-gc -test -vanilla" 0 kB Output of revdep-rebuild: >>> Emerging (1 of 8) sci-libs/fftw-3.2.2 * fftw-3.2.2.tar.gz RMD160 SHA1 SHA256 size ;-) ... [ ok ] * checking ebuild checksums ;-) ... [ ok ] * checking auxfile checksums ;-) ... [ ok ] * checking miscfile checksums ;-) ... [ ok ] * gcc-config: Active gcc profile is invalid! gcc-config: error: could not run/locate 'x86_64-pc-linux-gnu-gcc' * gcc-config: Active gcc profile is invalid! gcc-config: error: could not run/locate 'x86_64-pc-linux-gnu-gcc' * You are using gcc and OpenMP is only available with gcc >= 4.2 * If you want to build fftw with OpenMP, abort now, * and switch CC to an OpenMP capable compiler * Otherwise, we will build using POSIX threads. ... checking for x86_64-pc-linux-gnu-gcc... x86_64-pc-linux-gnu-gcc checking for C compiler default output file name... configure: error: in `/var/tmp/portage/sci-libs/fftw-3.2.2/work/fftw-3.2.2-single': configure: error: C compiler cannot create executables See `config.log' for more details. Reproducible: Always Steps to Reproduce: 1. emerge gcc-4.4.1 during world update 2. emerge --depclean; revdep-rebuild 3. emerge some package Actual Results: gcc-4.4.1 cannot create executables. Expected Results: Than gcc.4.4.1 can create executables.