http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54996
--- Comment #2 from lvd.mhm at gmail dot com 2012-10-28 15:25:28 UTC --- I was wrong not setting $PATH to just compiled binutils. However, even after setting correct $PATH or just compiling binutils to default /usr/local/bin, problem still persisted. I used clean x86_64 virtual machine with fresh ubuntu12.04.1 server install with just nothing installed except SSH and then packages needed to build binutils and gcc, and I've found, that bug exists when $PATH has ./ at first place. If there is no ./ in $PATH or ./ at the end, gcc compiles fine. Of course then same behavior repeats itself on hardware.
