From: Krishnakumar B <kitty@cs.wustl.edu>
To: "H . J . Lu" <hjl@lucon.org>
Cc: Janis Johnson <janis187@us.ibm.com>,
gcc@gcc.gnu.org, binutils@sourceware.cygnus.com
Subject: Re: Linking libstdc++ with gcc-3.0.2 prerelease fails on IA64
Date: Mon, 15 Oct 2001 11:26:00 -0000 [thread overview]
Message-ID: <15307.10804.121457.337095@samba.doc.wustl.edu> (raw)
In-Reply-To: <20011015110436.A2529@lucon.org>
On Monday, 15 October 2001, H . J . Lu wrote:
> On Mon, Oct 15, 2001 at 10:26:55AM -0700, Janis Johnson wrote:
> > On Sun, Oct 14, 2001 at 06:38:26PM -0500, Krishnakumar B wrote:
> > >
> > > I am trying to bootstrap IA-64. During the link stage of libstdc++, I get
> > > the following message. I can reproduce the failure at the same stage with
> > > the snapshots 200011001 and 20011007 also.
> > >
> > > .libs/string-inst.o:/u/kitty/tools/gcc-3.0.2-20011014/ia64-redhat-linux/ia64-redhat-linux/libstdc++-v3/include/bits/basic_string.h:238:
> > > unsupported reloc
> >
> > I see this with the mainline CVS. Rather than looking into it I've just
> > avoided building c++ and java. Unless someone already knows what the
> > problem is I can look into it.
> >
>
> I believe it is a binutils bug. Please tell me how to reproduce it. I
> will make sure it is fixed.
Just try bootstrapping gcc on IA64. Linking libstdc++ fails with this
error. True for both the mainline or prerelease. I resorted to linking
using binutils 2.11.90.0.8 though I am sure that it will link with any
binutils other than 2.11.92.0.5.
-kitty.
>
> Thanks.
>
>
> H.J.
--
Krishnakumar B <kitty at cs dot wustl dot edu>
Distributed Object Computing Laboratory, Washington University in St.Louis
next prev parent reply other threads:[~2001-10-15 11:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-14 16:39 Krishnakumar B
2001-10-15 10:24 ` Janis Johnson
2001-10-15 11:04 ` H . J . Lu
2001-10-15 11:26 ` Krishnakumar B [this message]
2001-10-15 11:59 ` H . J . Lu
2001-10-15 14:14 ` Janis Johnson
2001-10-15 11:32 ` Janis Johnson
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=15307.10804.121457.337095@samba.doc.wustl.edu \
--to=kitty@cs.wustl.edu \
--cc=binutils@sourceware.cygnus.com \
--cc=gcc@gcc.gnu.org \
--cc=hjl@lucon.org \
--cc=janis187@us.ibm.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).