This is the mail archive of the binutils@sources.redhat.com mailing list for the binutils project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

ld testsuite breaks with latest GCC-4.0


Hi

In case you haven't already heard, GCC-4.0 no longer installs a "specs"
file. See these threads:

  http://gcc.gnu.org/ml/gcc-patches/2004-12/msg01459.html
  http://gcc.gnu.org/ml/gcc-patches/2004-12/msg01574.html
  
The ld testsuite currently attempts some grovelling around in the gcc specs
file to find out various bits of information. This from ld/configure.host
(excuse the wrap):


  *-*-linux*)
  HOSTING_CRT0='-dynamic-linker `egrep "ld[^ ]*\.so" \`${CC} --print-file-name=specs\` | sed 
-e "s,.*-dynamic-linker[   ][ ]*\(.*/ld[^ ]*\.so..\).*,\1,"` `${CC} --print-file-name=crt1.o` 
`${CC} --print-file-name=crti.o` `if [ -f ../gcc/crtbegin.o ]; then echo ../gcc/crtbegin.o; else 
${CC} --print-file-name=crtbegin.o; fi`'

  
With latest GCC-4.0, `gcc --print-file-name=specs' spits out nothing which
breaks the whole ld testsuite:


Using /temptools/src/binutils-2.15.94.0.2/ld/testsuite/config/default.exp as tool-and-target-specific interface file.
ERROR: tcl error sourcing tool-and-target-specific interface file /temptools/src/binutils-2.15.94.0.2/ld/testsuite/config/default.exp.
Error getting native link files: -dynamic-linker /usr/lib/crt1.o /usr/lib/crti.o /temptools/lib/gcc/i686-pc-linux-gnu/4.0.0/crtbegin.o
grep: specs: No such file or directory
Error getting native link files: -dynamic-linker /usr/lib/crt1.o /usr/lib/crti.o /temptools/lib/gcc/i686-pc-linux-gnu/4.0.0/crtbegin.o
grep: specs: No such file or directory
    while executing


Clearly, changes will be needed. I'm not sure what the best solution is but
I have a feeling that it will probably involve:

  `gcc -dumpspecs'

but that might have the potential to break older GCC's. Dunno.

Thoughts?

Thanks
Greg

PS - I'm using the latest HJ release but the code in question from CVS trunk
looks the same.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]