From: Christopher Faylor <cgf@redhat.com>
To: gcc-patches@gcc.gnu.org
Cc: DJ Delorie <dj@redhat.com>
Subject: Re: [PATCH] Fix libiberty to detect new cygwin exports
Date: Wed, 15 Aug 2001 15:24:00 -0000 [thread overview]
Message-ID: <20010815182421.A17077@redhat.com> (raw)
In-Reply-To: <20010815180621.A16847@redhat.com>
On Wed, Aug 15, 2001 at 06:06:21PM -0400, Christopher Faylor wrote:
>Wed Aug 15 18:00:49 2001 Christopher Faylor <cgf@cygnus.com>
>
> * configure.in: Under cygwin, add checks for newly exported sys_errlist
> and sys_nerr. Collapse two identical if/cases into one.
> * configure: Regenerate.
Sorry. DJ has enlightened me that the "Collapse" part of this patch is pretty
obviously wrong, so I withdraw it.
cgf
next prev parent reply other threads:[~2001-08-15 15:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-15 15:06 Christopher Faylor
2001-08-15 15:24 ` Christopher Faylor [this message]
2001-08-15 15:24 ` Richard Henderson
2001-08-15 15:24 ` Christopher Faylor
2001-08-16 10:49 ` [RFA] Fix libiberty to detect new cygwin export, try 2 Christopher Faylor
2001-08-16 13:38 ` DJ Delorie
2001-08-17 13:17 ` Christopher Faylor
2001-08-16 16:47 ` [PATCH] Fix libiberty to detect new cygwin exports Richard Henderson
2001-08-17 13:16 ` Christopher Faylor
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=20010815182421.A17077@redhat.com \
--to=cgf@redhat.com \
--cc=dj@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
/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).