From: Ian Lance Taylor <ian@cygnus.com>
To: kkaempf@progis.de
Cc: bfd@cygnus.com
Subject: Re: binutils 2.9 on sparc-unknown-linux-gnulibc1
Date: Wed, 08 Apr 1998 08:52:00 -0000 [thread overview]
Message-ID: <199804081552.LAA23951@subrogation.cygnus.com> (raw)
In-Reply-To: <19980408074808.17815.qmail@progis.de>
From: kkaempf@progis.de
Date: Wed, 8 Apr 1998 09:48:08 +0200 (MET DST)
Did a clean configure and build.
=== ld tests ===
FAIL: bootstrap
FAIL: bootstrap with --static
FAIL: bootstrap with --traditional-format
FAIL: bootstrap with --no-keep-memory
FAIL: cdtest
FAIL: cdtest with -Ur
=== ld Summary ===
# of expected passes 12
# of unexpected failures 6
I would guess that these are because there is no entry in
ld/configure.host for sparc-unknown-linux-gnulibc1. If the linker is
able to successfully link a program when invoked by gcc, then I
wouldn't worry about these errors.
See the other linux-gnu and linux*libc1 entries in ld/configure.host
for possible examples of how to set HOSTING_CRT0 and HOSTING_LIBS on
your system. I don't know what's right.
I don't plan to worry about this for the 2.9 release.
Ian
prev parent reply other threads:[~1998-04-08 8:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-04-08 0:48 kkaempf
1998-04-08 8:01 ` H.J. Lu
1998-04-08 8:52 ` Ian Lance Taylor [this message]
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=199804081552.LAA23951@subrogation.cygnus.com \
--to=ian@cygnus.com \
--cc=bfd@cygnus.com \
--cc=kkaempf@progis.de \
/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).