From: DJ Delorie <dj@redhat.com>
To: tschwinge@gnu.org
Cc: gcc-patches@gcc.gnu.org
Subject: Re: gcc-4_2-branch: tiny issue with libiberty
Date: Tue, 13 Nov 2007 16:43:00 -0000 [thread overview]
Message-ID: <200711131558.lADFwUb2028139@greed.delorie.com> (raw)
In-Reply-To: <20071113154239.GH21016@fencepost.gnu.org> (message from Thomas Schwinge on Tue, 13 Nov 2007 16:42:39 +0100)
> Nevertheless, I don't understand why you don't want to adapt the
> parameters to what other systems (glibc, BSD) are using? Why should
> libiberty provide a (marginally) different version of `psignal'?
Well, for starters, it helps us find build problems like yours :-)
(I'm a big fan of choosing "fail loudly" over "fail quietly")
Since our psignal should only get used on platforms without their own
psignal, why does it matter?
next prev parent reply other threads:[~2007-11-13 15:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-13 8:42 Thomas Schwinge
2007-11-13 9:25 ` DJ Delorie
2007-11-13 14:02 ` Thomas Schwinge
2007-11-13 14:37 ` DJ Delorie
2007-11-13 16:29 ` Thomas Schwinge
2007-11-13 16:43 ` DJ Delorie [this message]
2007-11-17 17:35 ` Thomas Schwinge
2007-11-19 10:06 ` Ben Elliston
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=200711131558.lADFwUb2028139@greed.delorie.com \
--to=dj@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=tschwinge@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).