From: Thomas Schwinge <tschwinge@gnu.org>
To: DJ Delorie <dj@redhat.com>
Cc: gcc-patches@gcc.gnu.org, Roland McGrath <roland@frob.com>
Subject: Re: gcc-4_2-branch: tiny issue with libiberty
Date: Sat, 17 Nov 2007 17:35:00 -0000 [thread overview]
Message-ID: <20071117134617.GM16318@fencepost.gnu.org> (raw)
In-Reply-To: <200711131558.lADFwUb2028139@greed.delorie.com>
[-- Attachment #1: Type: text/plain, Size: 1653 bytes --]
[Roland: for your information.]
Hello!
On Tue, Nov 13, 2007 at 10:58:30AM -0500, DJ Delorie wrote:
> > 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")
I absolutely agree to ``failing loudly'' instead of ``failing quietly'',
however I think that this is a non-argument for the issue at hand here,
as it only triggered, because that one prototype (of GNU libc's and BSD
libc's `psignal') happened to be different from the libiberty
implementation. Or do you want to suggest that you're going to introduce
such function signature changes for every libiberty-provided symbol? I
hope you don't. :-)
> Since our psignal should only get used on platforms without their own
> psignal, why does it matter?
So that the next person to see through this part of the libiberty sources
doesn't wonder why the libiberty `psignal' is (marginally) different from
the GNU libc or BSD libc one. I still uphold that my patch should be
installed, but that's not for me to decide, obviously.
As for the original report: this was while building a i586-pc-gnu cross
compiler from the gcc-4_2-branch sources. I can't reproduce the original
problem anymore and already lost the previous `config.log' file. I
suspect it was a bogon resulting from a stale `config.cache' file and
change in the target's libc.
Regards,
Thomas
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 191 bytes --]
next prev parent reply other threads:[~2007-11-17 13:46 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
2007-11-17 17:35 ` Thomas Schwinge [this message]
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=20071117134617.GM16318@fencepost.gnu.org \
--to=tschwinge@gnu.org \
--cc=dj@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=roland@frob.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).