From: Dan Kegel <dank@kegel.com>
To: Jonathan Wakely <cow@compsoc.man.ac.uk>
Cc: Karel Gardas <kgardas@objectsecurity.com>,
Christian Joensson <christian.joensson@gmail.com>,
Eric Botcazou <ebotcazou@libertysurf.fr>,
gcc@gcc.gnu.org, libstdc++@gcc.gnu.org
Subject: Re: libstdc++ required binutils version [was: Re: gcc 4.0.1 testsuite failures on sparc64-linux: 59 unexpected gcc failures]
Date: Tue, 12 Jul 2005 17:08:00 -0000 [thread overview]
Message-ID: <42D3F6E4.6080003@kegel.com> (raw)
In-Reply-To: <20050712122148.GA62290@compsoc.man.ac.uk>
Jonathan Wakely wrote:
>>>>>The minimum binutils for libstdc++ is now 2.15.90.0.1.1, I don't know
>>>>>about the rest of GCC.
>> ...
>>and IMHO testresults look quite good except abi_check, don't they? i.e. do
>>you mean updating binutils will resolve abi_check issue in libstdc++
>>testsuite?
>
> I'd assume yes, based on Benjamin's statement here:
> http://gcc.gnu.org/ml/libstdc++/2005-06/msg00132.html
Does 2.16 satisfy the minimum requirement? This should
be clearly spelled out in the doc. 2.15.90.0.1.1 is
linux-only.
- Dan
--
Trying to get a job as a c++ developer? See http://kegel.com/academy/getting-hired.html
prev parent reply other threads:[~2005-07-12 17:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-12 6:55 gcc 4.0.1 testsuite failures on sparc64-linux: 59 unexpected gcc failures Christian Joensson
2005-07-12 7:31 ` Eric Botcazou
2005-07-12 7:48 ` Christian Joensson
2005-07-12 10:21 ` Christian Joensson
2005-07-12 10:57 ` Jonathan Wakely
2005-07-12 11:24 ` Karel Gardas
2005-07-12 11:45 ` Jonathan Wakely
2005-07-12 11:55 ` libstdc++ required binutils version [was: Re: gcc 4.0.1 testsuite failures on sparc64-linux: 59 unexpected gcc failures] Karel Gardas
2005-07-12 12:22 ` Jonathan Wakely
2005-07-12 17:08 ` Dan Kegel [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=42D3F6E4.6080003@kegel.com \
--to=dank@kegel.com \
--cc=christian.joensson@gmail.com \
--cc=cow@compsoc.man.ac.uk \
--cc=ebotcazou@libertysurf.fr \
--cc=gcc@gcc.gnu.org \
--cc=kgardas@objectsecurity.com \
--cc=libstdc++@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).