Thanks for identifying it - good so I'm not crazy :) I tried your fix and I think it worked? I get this error when linking now: <.a file>: could not read symbols: Bad value collect2: error: ld returned 1 exit status I tried building the latest stable GCC, 4.8.1, and binutils, 2.23.2, but an error buildling it too: /lib64/ld-linux-x86-64.so.2: could not read symbols: Invalid operation This is on a RHEL4u8WS machine. On Wed, Jun 19, 2013 at 6:06 PM, Ian Lance Taylor <iant@xxxxxxxxxx> wrote: > On Wed, Jun 19, 2013 at 3:04 PM, Uri Moszkowicz <uri@xxxxxxxxx> wrote: >> Log uploaded here: >> >> http://www.4refs.com/gcc.log >> >> It seems to be looking in the right places just not for the right >> file. It looks for "real-ld", "collect-ld", and "ld-new" but not "ld". > > This looks like a bug. It looks like it has been fixed in current > mainline. It looks like when you build with the binutils as a sibling > directory, it finds ld-new in the ld directory. Then it mistakenly > starts looking for that, rather than ld. I haven't tried but you may > be able to work around this by using the GCC configure option > --with-plugin-ld=/path/to/your/ld. > > Ian
