public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Greg Schafer <gschafer@zip.com.au>
To: binutils@sources.redhat.com
Subject: ld testsuite breaks with latest GCC-4.0
Date: Sun, 02 Jan 2005 04:45:00 -0000	[thread overview]
Message-ID: <20050102044451.GA24007@tigers-lfs.nsw.bigpond.net.au> (raw)

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.

             reply	other threads:[~2005-01-02  4:45 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-02  4:45 Greg Schafer [this message]
2005-01-02  5:11 ` Daniel Jacobowitz
2005-01-02  6:24   ` [PATCH] " Greg Schafer
2005-01-03 20:51     ` James E Wilson
2005-01-04 10:30     ` Nick Clifton
2005-01-04 10:43     ` Jakub Jelinek
2005-01-04 22:47       ` Greg Schafer
2005-01-06 12:25         ` Greg Schafer
2005-01-10 14:58           ` Nick Clifton

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20050102044451.GA24007@tigers-lfs.nsw.bigpond.net.au \
    --to=gschafer@zip.com.au \
    --cc=binutils@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).