[SOLVED] gcc 5.4.0 vs hardening

[therealjrd]

Hi all. I'm trying to do some upgrading, in preparation for moving to profile 17. I'm still at 13.

I have a VM on which I do most of my package building, before I try it out on any of my live server machines. I seem to have gotten my VM into a state where it will only build hardened compilers, even though I'm not running a hardened profile. When I

# gcc-config -l

I get only the plain x86_64-pc-linux-gnu-5.4.0, no -vanilla or -hardened* variants. The same seems to be true for 6.4.0.

I've tried switching back to an old 4.9.3 gcc which I haven't unmerged yet, same thing. I get the same results regardless of which version I use to compile the new ones. I've confirmed that I'm running profile default/linux/amd64/13.0/no-multilib

I have a feeling I've busted something in the env, but I don't know what. Before I blow the whole thing away and start over, does anybody have any ideas what I've done to myself?

Thanks in advance . . .

[AndrewAmmerlaan]

[therealjrd]

[therealjrd]

Closing the loop, yes, switching to a non-hardened profile and rebuilding the toolchain did what I expected.

I have a separate problem stemming from this exercise, will post separately.

Thanks!