It appears as though gcc-config -O is unable to figure out what the current profile is. Reproducible: Always Steps to Reproduce: 1. run gcc-config -l, to list your profiles 2. run gcc-config -O Actual Results: agave ~ # 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.1.2 * agave ~ # gcc-config -O * No profile selected, unable to utilize --use-old This is a major problem for me because the LDFLAGS in /etc/env.d/05gcc* aren't updated properly when gcc is installed. Some programs crash because they can't find libstdc++.so.5 I verified this problem ~x86 and ~amd64 I used 'gcc-config $(gcc-config -c)' to workaround it.
Created attachment 152651 [details, diff] Possible fix The problem comes about because a config file was renamed, /etc/env.d/gcc/config is now called /etc/env.d/gcc/config-x86_64-pc-linux-gnu The attached patch fixes the problem, but I'm not sure if it's the correct fix.
Looks good enough to me, and it works. Fixed in the tree. Thanks
