From: James E Wilson <wilson@specifixinc.com>
To: sje@cup.hp.com
Cc: binutils@sources.redhat.com
Subject: Re: Another HP-UX IA64 Build patch
Date: Thu, 05 May 2005 20:12:00 -0000 [thread overview]
Message-ID: <1115323807.8413.102.camel@aretha.corp.specifixinc.com> (raw)
In-Reply-To: <200505051714.KAA17413@hpsje.cup.hp.com>
[-- Attachment #1: Type: text/plain, Size: 579 bytes --]
On Thu, 2005-05-05 at 10:14, Steve Ellcey wrote:
> Here is the second of my IA64 HP-UX build patches. This one involves
> the declaration of basename() in include/libiberty.h. What do people
> think about using the prototype version whenever we are compiling with
> GCC?
Never mind, I see the problem. The question about the prototype
confused me, and put me on the wrong track. Try this patch. We need to
include sysdep.h before libiberty.h, so that libiberty.h gets the proper
HAVE_DECL_BASENAME definition.
--
Jim Wilson, GNU Tools Support, http://www.SpecifixInc.com
[-- Attachment #2: patch.include.order --]
[-- Type: text/plain, Size: 735 bytes --]
2005-05-05 James E Wilson <wilson@specifixinc.com>
* ia64-opc.c: Include sysdep.h before libiberty.h.
Index: ia64-opc.c
===================================================================
RCS file: /cvs/src/src/opcodes/ia64-opc.c,v
retrieving revision 1.8
diff -p -p -r1.8 ia64-opc.c
*** ia64-opc.c 3 Mar 2005 11:49:49 -0000 1.8
--- ia64-opc.c 5 May 2005 20:05:54 -0000
***************
*** 20,27 ****
02111-1307, USA. */
#include "ansidecl.h"
- #include "libiberty.h"
#include "sysdep.h"
#include "ia64-asmtab.h"
#include "ia64-asmtab.c"
--- 20,27 ----
02111-1307, USA. */
#include "ansidecl.h"
#include "sysdep.h"
+ #include "libiberty.h"
#include "ia64-asmtab.h"
#include "ia64-asmtab.c"
next prev parent reply other threads:[~2005-05-05 20: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
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 [this message]
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=1115323807.8413.102.camel@aretha.corp.specifixinc.com \
--to=wilson@specifixinc.com \
--cc=binutils@sources.redhat.com \
--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).