From: James E Wilson <wilson@specifixinc.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: Steve Ellcey <sje@cup.hp.com>, binutils@sources.redhat.com
Subject: Re: Another HP-UX IA64 Build patch
Date: Thu, 05 May 2005 19:17:00 -0000 [thread overview]
Message-ID: <1115319939.8413.35.camel@aretha.corp.specifixinc.com> (raw)
In-Reply-To: <20050505181241.GA19179@nevyn.them.org>
On Thu, 2005-05-05 at 11:12, Daniel Jacobowitz wrote:
> Wait, huh? What do glibc's quirks have to do with HP/UX's libgen.h?
> If you use <libgen.h> on a glibc system you're going to get it without
> the const, no matter what _GNU_SOURCE says.
The prototype in libiberty.h disagrees with POSIX, which means it
disagrees with all systems other than a glibc system. Thus confusion.
The confusion is solved by pointing out the glibc quirk. That was all I
was trying to do.
However, I don't think think this matters much. As I said in the
earlier message, I think we should just use this for hpux anyways.
We change libiberty only when and if a problem arises, and I don't
expect one to arise. The declarations in libiberty shouldn't be used if
there is a system declaration, so there shouldn't be a possibility of a
mismatch here unless there are configure problems.
--
Jim Wilson, GNU Tools Support, http://www.SpecifixInc.com
next prev parent reply other threads:[~2005-05-05 19:05 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-05 17:26 Steve Ellcey
2005-05-05 17:41 ` Daniel Jacobowitz
2005-05-05 17:55 ` Steve Ellcey
2005-05-05 18:12 ` James E Wilson
2005-05-05 18:16 ` Daniel Jacobowitz
2005-05-05 19:17 ` James E Wilson [this message]
2005-05-05 19:32 ` DJ Delorie
2005-05-05 19:47 ` James E Wilson
2005-05-05 21:40 ` Andreas Schwab
2005-05-05 21:43 ` DJ Delorie
2005-05-05 18:10 ` James E Wilson
2005-05-05 20:12 ` James E Wilson
2005-05-05 20:42 ` Steve Ellcey
2005-05-05 21:36 ` DJ Delorie
2005-05-05 21:41 ` James E Wilson
2005-05-05 22:46 ` DJ Delorie
2005-05-06 1:57 ` James E Wilson
2005-05-06 1:58 ` DJ Delorie
2005-05-09 23:28 ` Steve Ellcey
2005-05-09 23:33 ` DJ Delorie
2005-05-12 16:37 ` Steve Ellcey
2005-05-05 22:06 ` James E Wilson
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=1115319939.8413.35.camel@aretha.corp.specifixinc.com \
--to=wilson@specifixinc.com \
--cc=binutils@sources.redhat.com \
--cc=drow@false.org \
--cc=sje@cup.hp.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).