binutils expects internal gcc objects to have a single letter suffix (e.g. crtbeginT.o crtbeginS.o), so using two letters means we have to patch binutils in the places we notice. it'll be easier if we rename our custom crtbegin object to match what everything else expects.
Not that it makes much difference, but why "H"? Did you have some acronym in mind?
Will rename crtbeginTS.o to crtbeginP.o Fix will be in next bump of piepatch for gcc 4.5 and gcc 4.6
pick any letter that isn't already used. i just picked "H" for "hardened".
(In reply to comment #3) > pick any letter that isn't already used. i just picked "H" for "hardened". Magnus suggested "P" for pie. Let's go with that because its more specific as a description of the type of hardening. Magnus ok? (And please, no one notice that it can also stand for other types of hardening that begin with the letter "p" ... sssh!)
(In reply to comment #4) > (In reply to comment #3) > > pick any letter that isn't already used. i just picked "H" for "hardened". > > Magnus suggested "P" for pie. Let's go with that because its more specific as > a description of the type of hardening. Magnus ok? > > (And please, no one notice that it can also stand for other types of hardening > that begin with the letter "p" ... sssh! Thats is okey Doing testing on the new piepatchset.
Fixed in gcc-4.6.2 with piepatchset 0.5.0
Fixed in gcc-4.5.3-r2 with piepatchset 0.4.6
FYI i'm dropping this patch starting with 2.26.1 since it's been in gcc long enough. i'll prob drop it from older binutils too, just not do an explicit patchset push for it.
