https://sourceware.org/bugzilla/show_bug.cgi?id=18450
--- Comment #2 from darlingm at gmail dot com --- To clarify, are you saying this is a GCC bug, then? Or, do you mean something else - like user error? (I think I'm following the proper procedure for a gcc/binutils combined build.) BTW, this happens on stage 2. Uncombined build works just fine... If I: mkdir binutils.build.gcc492 cd binutils.build.gcc492 ../gcc.binutils.combined/binutils-gdb.git/configure --disable-multilib && make && sudo make install ^^ this uses gcc 4.9.2 Or, even if I: mkdir gcc.build.gcc cd gcc.build.gcc ../gcc.binutils.combined/gcc.git/configure --disable-multilib && make && sudo make install hash -r // add /usr/local/lib64 to ldconfig, and run ldconfig mkdir ../binutils.build.gcc6 cd ../binutils.build.gcc6 ../gcc.binutils.combined/binutils-gdb.git/configure --disable-multilib && make && sudo make install ^^ case uses gcc6 // then I can even ldconfig mkdir ../gcc.build.gcc6.with.new.binutils cd ../gcc.build.gcc6.with.new.binutils ../gcc.binutils.combined/gcc.git/configure --disable-multilib && make && sudo make install -- You are receiving this mail because: You are on the CC list for the bug. _______________________________________________ bug-binutils mailing list bug-binutils@gnu.org https://lists.gnu.org/mailman/listinfo/bug-binutils
