See bug #468540, because /usr/bin/lib is seen (checking for lib... /usr/bin/lib) it doesn't consider /usr/bin/ar and one would assume it to then succeed to compile with /usr/bin/lib. However, once it calls /usr/bin/lib we are presented with the error: > gcc-config: error: could not run/locate 'lib' We'll temporary remove tlib and lib from the detection such that it always picks /usr/bin/ar until this is resolved, please let us know if there are more appropritae fixes available for this.
i have no idea what you're talking about. gcc-config nor gcc install a `lib` or `tlib` symlink in /usr/bin/. if people are randomly doing: $ sudo ln -s ar /usr/bin/lib then i don't care. that's stupid and won't work.
Confirmed with pfl that nothing installs lib or tlib; seems like something outside of the Portage tree, I'll ask in the other bug how that got there.
