Summary: | (toolchain) Can't compile a non-hardened gcc 3.4.3 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Olivier Galibert <galibert> |
Component: | Hardened | Assignee: | The Gentoo Linux Hardened Team <hardened> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Olivier Galibert
2004-12-27 17:17:57 UTC
Have you tried to select a different profile with gcc-config? E.g. the "vanilla" profile. make sure the env var GCC_SPECS is not set. echo $GCC_SPECS GCC_SPECS is indeed set to hardened through /etc/csh.env while the vanilla profile is selected. Interesting. I guess that's a bug of env-update (and hence portage) then. I'll try to trace it. OG. remove the entry in /etc/env.d/gcc/ upgrade gcc-config and relogin to your tty's that still have it set in the env. Note: it was not hardened@ that made the GCC_SPECS bug. To see what's bins have been compiled with the hardened specs you can do something like this. # note this will take a while. for bin in $(for f in $(echo $PATH | tr : ' '); do file $f/* | grep ELF" "[36][24]-bit" "[LM]SB" shared object"; done | cut -d : -f 1) ; do qpkg -f $bin ; done | sort -u | less Thanks. A too old gcc-config was indeed the fundamental problem. All looks well now. OG. |