public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: "Joseph S. Myers" <jsm28@cam.ac.uk>
To: pme@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org
Subject: Re: libstdc++/3497: after build problem
Date: Mon, 02 Jul 2001 13:16:00 -0000 [thread overview]
Message-ID: <20010702201603.22097.qmail@sourceware.cygnus.com> (raw)
The following reply was made to PR libstdc++/3497; it has been noted by GNATS.
From: "Joseph S. Myers" <jsm28@cam.ac.uk>
To: <pme@gcc.gnu.org>
Cc: <gcc-bugs@gcc.gnu.org>, <isabet@club-internet.fr>,
<gcc-gnats@gcc.gnu.org>
Subject: Re: libstdc++/3497: after build problem
Date: Mon, 2 Jul 2001 21:09:53 +0100 (BST)
On 2 Jul 2001 pme@gcc.gnu.org wrote:
> This is a binutils problem; there is a series of versions
> of binutils which don't work, and the missing __dso_handle
> symbol is the symptom. You should either downgrade your
> binutils to an older version, or (preferably) upgrade to a
> newer version, such as 2.12.
Closing a PR is hardly a complete fix to this problem - if some binutils
versions don't work, we should test for the bug in configure and refuse to
configure with broken binutils. If the requirement for recent binutils is
platform-independent, we should also document it generally in
doc/install.texi and remove the documentation under specific targets
mentioning various old versions that are required.
--
Joseph S. Myers
jsm28@cam.ac.uk
next reply other threads:[~2001-07-02 13:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-02 13:16 Joseph S. Myers [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-07-02 13:26 Phil Edwards
2001-07-02 13:01 pme
2001-06-30 6:16 isabet
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=20010702201603.22097.qmail@sourceware.cygnus.com \
--to=jsm28@cam.ac.uk \
--cc=gcc-prs@gcc.gnu.org \
--cc=pme@gcc.gnu.org \
/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).