From: DJ Delorie <dj@redhat.com>
To: "Ulrich Weigand" <uweigand@de.ibm.com>
Cc: vinschen@redhat.com, newlib@sourceware.org,
gcc-patches@gcc.gnu.org, yselkowitz@users.sourceforge.net,
ken.werner@de.ibm.com
Subject: Re: newlib vs. libiberty mismatch breaks build (Re: [PATCH] Export psignal on all platforms)
Date: Thu, 05 May 2011 18:27:00 -0000 [thread overview]
Message-ID: <201105051811.p45IBiQ7018870@greed.delorie.com> (raw)
In-Reply-To: <201105051732.p45HW6Oe020287@d06av02.portsmouth.uk.ibm.com> (uweigand@de.ibm.com)
IIRC there's a compile-time way to test for prototypes at least.
next prev parent reply other threads:[~2011-05-05 18:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20110504111745.GD26180@calimero.vinschen.de>
2011-05-05 9:11 ` Ulrich Weigand
2011-05-05 9:16 ` Corinna Vinschen
2011-05-05 9:24 ` Corinna Vinschen
2011-05-05 16:11 ` DJ Delorie
2011-05-05 16:54 ` Ulrich Weigand
2011-05-05 17:01 ` Corinna Vinschen
2011-05-05 17:02 ` DJ Delorie
2011-05-05 17:38 ` Ulrich Weigand
2011-05-05 18:27 ` DJ Delorie [this message]
2011-05-05 16:57 ` Corinna Vinschen
2011-05-05 17:03 ` 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=201105051811.p45IBiQ7018870@greed.delorie.com \
--to=dj@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=ken.werner@de.ibm.com \
--cc=newlib@sourceware.org \
--cc=uweigand@de.ibm.com \
--cc=vinschen@redhat.com \
--cc=yselkowitz@users.sourceforge.net \
/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).