gcc-3.4.2 produces vanilla,hardened,hardenednossp specs if built w/ hardened use flag, the hardenednossp specs is the same as hardened Reproducible: Always Steps to Reproduce: 1. 2. 3.
ayanami 3.4.2 # diff -u hardened.specs hardenednossp.specs --- hardened.specs 2004-10-14 01:53:19.393861136 -0400 +++ hardenednossp.specs 2004-10-14 01:53:19.393861136 -0400 @@ -30,7 +30,7 @@ cc1 -E %{traditional|ftraditional|traditional-cpp:-traditional-cpp} *cc1: -%(cc1_cpu) %{profile:-p} %{m32: %{!msse2:-mno-sse2} } %{!D__KERNEL__: %{!static: %{!fno-PIC: %{!fno-pic: %{!shared: %{!nostdlib: %{!nostartfiles: %{!fno-PIE: %{!fno-pie: %{!nopie: %{!fPIC:%{!fpic:-fPIE}}} } } } } } } } } %{!nostdlib: %{!fno-stack-protector: -fstack-protector %{!D_LIBC: %{!D_LIBC_REENTRANT: %{!fno-stack-protector-all:-fstack-protector-all}} } } } } +%(cc1_cpu) %{profile:-p} %{m32: %{!msse2:-mno-sse2} } %{!D__KERNEL__: %{!static: %{!fno-PIC: %{!fno-pic: %{!shared: %{!nostdlib: %{!nostartfiles: %{!fno-PIE: %{!fno-pie: %{!nopie: %{!fPIC:%{!fpic:-fPIE}}} } } } } } } } } %{!nostdlib: %{fstack-protector: -fstack-protector %{!D_LIBC: %{!D_LIBC_REENTRANT: %{!fno-stack-protector-all:-fstack-protector-all}} } } } } *cc1_options: %{shared:%{fPIE|fpie:%e-shared and -fPIE/fpie are incompatible}} %{pie:%{pg|p|profile:%e-pie and -pg|p|profile are incompatible}} %{pg:%{fomit-frame-pointer:%e-pg and -fomit-frame-pointer are incompatible}} %1 %{!Q:-quiet} -dumpbase %B %{d*} %{m*} %{a*} %{c|S:%{o*:-auxbase-strip %*}%{!o*:-auxbase %b}}%{!c:%{!S:-auxbase %b}} %{g*} %{O*} %{W*&pedantic*} %{w} %{std*} %{ansi} %{v:-version} %{pg:-p} %{p} %{f*} %{undef} %{Qn:-fno-ident} %{--help:--help} %{--target-help:--target-help} %{!fsyntax-only:%{S:%W{o*}%{!o*:-o %b.s}}} %{fsyntax-only:-o %j} %{-param*}
...I guess the logic for building the hardenednossp specs is b0rk3d for USE=hardened. :|
the diff from Travis is how it should look like, for me it is the same
this bug should be fixed now.