From: scottb <scottb@netwinder.org>
To: binutils mailing list <binutils@sourceware.cygnus.com>
Subject: Patch for make check failures on ARM Linux...
Date: Fri, 03 Sep 1999 14:00:00 -0000 [thread overview]
Message-ID: <37D0364E.86EBAE24@netwinder.org> (raw)
Hi,
All the tests in ld/testsuite/ld-bootstrap/bootstrap.exp were failing.
This was because HOSTING_CRT0 and HOSTING_LIBS were incorrect. This
patch fixes this problem.
Scott
1999-09-03 Scott Bambrough <scottb@netwinder.org>
* ld/configure.host: Added HOSTING_CRT0, HOSTING_LIBS for
target "armv*-*-linux-gnu*"]
Index: ld/configure.host
===================================================================
RCS file: /cvs/binutils/binutils/ld/configure.host,v
retrieving revision 1.5
diff -u -p -w -r1.5 configure.host
--- configure.host 1999/08/19 07:34:07 1.5
+++ configure.host 1999/09/02 21:04:40
@@ -35,6 +35,11 @@ alpha*-*-*)
NATIVE_LIB_DIRS=/usr/ccs/lib
;;
+armv*-*-linux-gnu*)
+ HOSTING_CRT0='-p -dynamic-linker `fgrep ld-linux.so \`${CC} --print-file-name=specs\` | sed -e "s,.*-dynamic-linker[ ][ ]*\(.*/ld-linux.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='`if [ -f ../gcc/libgcc.a ] ; then echo ../gcc/libgcc.a ; else ${CC} -print-libgcc-file-name; fi` -L`dirname \`${CC} --print-file-name=libc.so\`` -lc `if [ -f ../gcc/libgcc.a ] ; then echo ../gcc/libgcc.a ; else ${CC} -print-libgcc-file-name; fi` `if [ -f ../gcc/crtend.o ]; then echo ../gcc/crtend.o; else ${CC} --print-file-name=crtend.o; fi` `${CC} --print-file-name=crtn.o`'
+ ;;
+
i[3456]86-*-bsd* | i[3456]86-*-freebsd* | i[3456]86-*-netbsd*)
# The new BSD `make' has a bug: it doesn't pass empty arguments in
# shell commands. So we need to make this value non-empty in order
next reply other threads:[~1999-09-03 14:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-09-03 14:00 scottb [this message]
1999-09-03 16:11 Philip Blundell
1999-09-06 2:53 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=37D0364E.86EBAE24@netwinder.org \
--to=scottb@netwinder.org \
--cc=binutils@sourceware.cygnus.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).