From: Ian Lance Taylor <iant@google.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: joseph@codesourcery.com, gcc-patches@gcc.gnu.org,
gdb-patches@sources.redhat.com
Subject: Re: needed-list fails in libiberty
Date: Wed, 15 Apr 2009 13:50:00 -0000 [thread overview]
Message-ID: <m33acayqkj.fsf@google.com> (raw)
In-Reply-To: <837i1mmiyh.fsf@gnu.org> (Eli Zaretskii's message of "Wed\, 15 Apr 2009 11\:15\:02 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> > 2009-04-14 Eli Zaretskii <eliz@gnu.org>
>> >
>> > * Makefile.in (needed-list): Target removed (not used in GCC
>> > 3.0 and later). All references deleted.
>>
>> This is OK if you've done a clean bootstrap on a primary platform.
>
> You mean, bootstrapping GCC? Or something else?
Yes, bootstrapping gcc. This is a normal requirement for a gcc patch,
as documented at http://gcc.gnu.org/contribute.html#testing . My
concern here is merely to make sure that we aren't missing a hidden
dependency of libstdc++ on libiberty; such dependencies have certainly
been missed in the past. For a patch like this only the libiberty
testsuite need be run.
> Would this platform be good enough?
>
> Linux fencepost 2.6.16.29-xen #1 SMP Wed Dec 6 07:32:36 EST 2006 x86_64 GNU/Linux
Yes. The current list of primary platforms may be found at
http://gcc.gnu.org/gcc-4.5/criteria.html .
Thanks.
Ian
next prev parent reply other threads:[~2009-04-15 13:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-14 14:10 Eli Zaretskii
2009-04-14 14:19 ` Joseph S. Myers
2009-04-14 14:42 ` Eli Zaretskii
2009-04-15 0:30 ` Ian Lance Taylor
2009-04-15 8:15 ` Eli Zaretskii
2009-04-15 13:50 ` Ian Lance Taylor [this message]
2009-04-16 17:47 ` Eli Zaretskii
2009-04-25 9:58 ` Eli Zaretskii
2009-04-25 22:41 ` Ian Lance Taylor
2009-04-26 17:44 ` Eli Zaretskii
2009-04-26 2:23 ` DJ Delorie
2009-04-26 17:44 ` Eli Zaretskii
-- strict thread matches above, loose matches on Subject: below --
2009-04-14 14:10 Eli Zaretskii
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=m33acayqkj.fsf@google.com \
--to=iant@google.com \
--cc=eliz@gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=joseph@codesourcery.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