From: Greg Schafer <gschafer@zip.com.au>
To: binutils@sources.redhat.com
Subject: [PATCH] Re: ld testsuite breaks with latest GCC-4.0
Date: Sun, 02 Jan 2005 06:24:00 -0000 [thread overview]
Message-ID: <20050102062400.GA18827@tigers-lfs.nsw.bigpond.net.au> (raw)
In-Reply-To: <20050102051144.GA8032@nevyn.them.org>
[-- Attachment #1: Type: text/plain, Size: 665 bytes --]
On Sun, Jan 02, 2005 at 12:11:44AM -0500, Daniel Jacobowitz wrote:
> On Sun, Jan 02, 2005 at 03:44:51PM +1100, Greg Schafer wrote:
> > 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.
>
> That should work, as far back as I know of.
I was just worried that some installations may be using an altered "on disk"
specs file.
Anyhow, the attached patch makes it work for me on i686-pc-linux-gnu. But it
also affects the ia64-*-aix* target but I have no way of testing that.
Regards
Greg
[-- Attachment #2: ld.patch --]
[-- Type: text/plain, Size: 2246 bytes --]
2005-01-02 Greg Schafer <gschafer@zip.com.au>
* configure.host: Use "${CC} -dumpspecs" instead of
"${CC} --print-file-name=specs" to appease GCC versions >= 4.0.
Index: ld/configure.host
===================================================================
RCS file: /cvs/src/src/ld/configure.host,v
retrieving revision 1.36
diff -u -r1.36 configure.host
--- ld/configure.host 17 May 2004 19:50:16 -0000 1.36
+++ ld/configure.host 2 Jan 2005 06:03:40 -0000
@@ -33,7 +33,7 @@
;;
*-*-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`'
+ HOSTING_CRT0='-dynamic-linker `${CC} -dumpspecs | egrep "ld[^ ]*\.so" | 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`'
HOSTING_LIBS='-L`dirname \`${CC} --print-file-name=libc.so\`` '"$HOSTING_LIBS"' `if [ -f ../gcc/crtend.o ]; then echo ../gcc/crtend.o; else ${CC} --print-file-name=crtend.o; fi` `${CC} --print-file-name=crtn.o`'
;;
@@ -146,7 +146,7 @@
;;
ia64-*-aix*)
- HOSTING_CRT0='-dynamic-linker `egrep "libc.so" \`${CC} --print-file-name=specs\` | sed -e "s,.*-dynamic-linker[ ][ ]*\(.*/libc.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`'
+ HOSTING_CRT0='-dynamic-linker `${CC} -dumpspecs | egrep "libc.so" | sed -e "s,.*-dynamic-linker[ ][ ]*\(.*/libc.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`'
HOSTING_LIBS='-L`dirname \`${CC} --print-file-name=libc.so\`` '"$HOSTING_LIBS"' `if [ -f ../gcc/crtend.o ]; then echo ../gcc/crtend.o; else ${CC} --print-file-name=crtend.o; fi` `${CC} --print-file-name=crtn.o`'
;;
next prev parent reply other threads:[~2005-01-02 6:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-02 4:45 Greg Schafer
2005-01-02 5:11 ` Daniel Jacobowitz
2005-01-02 6:24 ` Greg Schafer [this message]
2005-01-03 20:51 ` [PATCH] " 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=20050102062400.GA18827@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).