From: DJ Delorie <dj@redhat.com>
To: Corinna Vinschen <vinschen@redhat.com>
Cc: rearnsha@arm.com, gcc-patches@gcc.gnu.org
Subject: Re: Libiberty: POSIXify psignal definition
Date: Wed, 18 May 2011 00:15:00 -0000 [thread overview]
Message-ID: <201105171648.p4HGmiOG011405@greed.delorie.com> (raw)
In-Reply-To: <20110517163313.GU5248@calimero.vinschen.de> (message from Corinna Vinschen on Tue, 17 May 2011 18:33:13 +0200)
> What I don't understand is why the newlib change broke older compilers.
Older compilers have the older libiberty. At the moment, libiberty
cannot be built by *any* released gcc, because you cannot *build* any
released gcc, because it cannot build its target libiberty.
> The function has been added to newlib and the definitions in newlib are
> correct.
"Correct" is irrelevent. They don't match libiberty, so the build
breaks.
> If this is refering to the fact that libiberty doesn't grok
> automatically if a symbol has been added to newlib, then that's a
> problem in libiberty, not in newlib.
It's a problem in every released gcc at the moment, so no released gcc
can be built for a newlib target, without hacking the sources.
> Otherwise, if you're building an older compiler, just use an older
> newlib as well.
The only option here is to not release a newlib at all until a fixed
gcc release happens, then, and require that fixed gcc for that version
of newlib forward.
next prev parent reply other threads:[~2011-05-17 16:49 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-05 7:39 Corinna Vinschen
2011-05-05 7:55 ` Andrew Pinski
2011-05-05 9:00 ` Corinna Vinschen
2011-05-05 17:32 ` Andrew Pinski
2011-05-17 18:28 ` Richard Earnshaw
2011-05-17 18:32 ` DJ Delorie
2011-05-17 19:34 ` Richard Earnshaw
2011-05-17 19:47 ` Corinna Vinschen
2011-05-18 0:15 ` DJ Delorie [this message]
2011-05-18 18:38 ` Richard Earnshaw
2011-05-18 19:05 ` DJ Delorie
2011-05-18 19:27 ` Corinna Vinschen
2011-05-18 20:19 ` Joseph S. Myers
2011-05-18 20:26 ` DJ Delorie
2011-05-18 20:31 ` Joseph S. Myers
2011-05-26 16:46 ` DJ Delorie
2011-06-08 12:21 ` Hans-Peter Nilsson
2011-06-08 13:12 ` Richard Earnshaw
2011-06-08 14:09 ` DJ Delorie
2011-06-20 16:57 ` Removing target-libiberty (was: Re: Libiberty: POSIXify psignal definition) Hans-Peter Nilsson
2011-06-20 17:03 ` Joseph S. Myers
2011-06-22 18:44 ` Hans-Peter Nilsson
2011-06-22 19:37 ` DJ Delorie
2011-06-22 21:40 ` Hans-Peter Nilsson
2011-05-17 20:03 ` Libiberty: POSIXify psignal definition DJ Delorie
2011-05-17 19:42 ` Corinna Vinschen
2011-05-17 21:23 ` DJ Delorie
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=201105171648.p4HGmiOG011405@greed.delorie.com \
--to=dj@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=rearnsha@arm.com \
--cc=vinschen@redhat.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).