From: Brad Lucier <lucier@math.purdue.edu>
To: phil@jaj.com (Phil Edwards)
Cc: lucier@math.purdue.edu (Brad Lucier),
gcc@gcc.gnu.org, libstdc++@gcc.gnu.org
Subject: Re: Mainline bootstrap failure linking .libs/libstdc++.so.5.0.0 on sparcv9-sun-solaris2.9
Date: Wed, 07 Aug 2002 17:27:00 -0000 [thread overview]
Message-ID: <200208080027.g780RUT29397@banach.math.purdue.edu> (raw)
In-Reply-To: <20020807132646.A22146@disaster.basement.lan>
> Looks like cxa_demangle.c and dyn-string.c are not being compiled with -fPIC.
> I believe this bug was just recently fixed on mainline in the past several
> hours.
Yes, thanks. I did update after the fix was included, but it seems that it
takes some time for check-ins to propagate to subversions.gnu.org.
Brad
next prev parent reply other threads:[~2002-08-07 17:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-07 10:09 Brad Lucier
2002-08-07 10:26 ` Phil Edwards
2002-08-07 17:27 ` Brad Lucier [this message]
2002-08-07 17:44 ` Phil Edwards
2002-08-10 8:27 ` Mainline bootstrap failure linking .libs/libstdc++.so.5.0.0 onsparcv9-sun-solaris2.9 Gerald Pfeifer
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=200208080027.g780RUT29397@banach.math.purdue.edu \
--to=lucier@math.purdue.edu \
--cc=gcc@gcc.gnu.org \
--cc=libstdc++@gcc.gnu.org \
--cc=phil@jaj.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).