From: James E Wilson <wilson@specifixinc.com>
To: Steve Ellcey <sje@cup.hp.com>
Cc: drow@false.org, binutils@sources.redhat.com, "H. J. Lu" <hjl@lucon.org>
Subject: Re: Patch for IA64 HP-UX build
Date: Thu, 05 May 2005 17:52:00 -0000 [thread overview]
Message-ID: <1115315340.8413.0.camel@aretha.corp.specifixinc.com> (raw)
In-Reply-To: <200505051657.JAA17339@hpsje.cup.hp.com>
On Thu, 2005-05-05 at 09:57, Steve Ellcey wrote:
> configure.in: Add ACX_HEADER_STRING check.
> configure: Regenerate.
> config.in: Regenerate.
> sysdep.h: Change ifdefs around include of string.h and strings.h.
OK.
--
Jim Wilson, GNU Tools Support, http://www.SpecifixInc.com
next prev parent reply other threads:[~2005-05-05 17:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-04 23:59 Steve Ellcey
2005-05-05 1:58 ` James E Wilson
2005-05-05 16:18 ` Steve Ellcey
2005-05-05 16:32 ` Steve Ellcey
2005-05-05 16:37 ` Steve Ellcey
2005-05-05 16:48 ` Daniel Jacobowitz
2005-05-05 17:14 ` Steve Ellcey
2005-05-05 17:52 ` James E Wilson [this message]
2005-05-05 19:28 ` James E Wilson
2005-05-05 16:58 ` H. J. Lu
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=1115315340.8413.0.camel@aretha.corp.specifixinc.com \
--to=wilson@specifixinc.com \
--cc=binutils@sources.redhat.com \
--cc=drow@false.org \
--cc=hjl@lucon.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).