From: James E Wilson <wilson@specifixinc.com>
To: Steve Ellcey <sje@cup.hp.com>
Cc: drow@false.org, binutils@sources.redhat.com
Subject: Re: Another HP-UX IA64 Build patch
Date: Thu, 05 May 2005 18:12:00 -0000 [thread overview]
Message-ID: <1115316630.8413.20.camel@aretha.corp.specifixinc.com> (raw)
In-Reply-To: <200505051751.KAA17543@hpsje.cup.hp.com>
On Thu, 2005-05-05 at 10:51, Steve Ellcey wrote:
> I see it doesn't have the const modifier that libiberty has. I didn't
> get a warning or error presumbably because the build didn't include
> libgen.h.
This is a libiberty bug. Try "man basename" on a linux system, and it
will tell you that there are two versions of basename. The posix one
which takes a char * argument, and a glibc _GNU_SOURCE one which takes a
const char * argument. So this probably should be something like
#if defined(_GNU_SOURCE)
extern char *basename (const char *);
#elif defined...
extern char *basename (char *);
#else
extern char *basename ();
#endif
But it appears that nobody is including libgen.h anywhere, or we would
have caught this before.
For now, I think just adding __hpux__ to the list is fine, and we can
worry about the wrong prototype later, when and if it causes a problem.
--
Jim Wilson, GNU Tools Support, http://www.SpecifixInc.com
next prev parent reply other threads:[~2005-05-05 18:10 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 [this message]
2005-05-05 18:16 ` Daniel Jacobowitz
2005-05-05 19:17 ` James E Wilson
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=1115316630.8413.20.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).