From: Christopher Faylor <cgf@redhat.com>
To: gcc-patches@gcc.gnu.org
Cc: DJ Delorie <dj@redhat.com>
Subject: [RFA] Fix libiberty to detect new cygwin export, try 2
Date: Thu, 16 Aug 2001 10:49:00 -0000 [thread overview]
Message-ID: <20010816134928.A7982@redhat.com> (raw)
In-Reply-To: <20010815214854.A18174@redhat.com>
Here is a much simpler version of the previous patch, worked out
in communication with DJ Delorie.
cgf
2001-08-16 Christopher Faylor <cgf@cygnus.com>
* configure.in: Always set HAVE_SYS_ERRLIST when targetting cygwin.
* configure: Regenerate.
Index: configure.in
===================================================================
RCS file: /cvs/uberbaum/libiberty/configure.in,v
retrieving revision 1.33
diff -p -r1.33 configure.in
*** configure.in 2001/07/05 17:24:39 1.33
--- configure.in 2001/08/16 17:45:02
*************** if test -n "${with_target_subdir}"; then
*** 177,182 ****
--- 177,187 ----
# Of the functions in $checkfuncs, newlib only has strerror.
AC_DEFINE_NOAUTOHEADER(HAVE_STRERROR)
+ case "${with_target_subdir}" in
+ *-*-cygwin*)
+ AC_DEFINE(HAVE_SYS_ERRLIST)
+ ;;
+ esac
setobjs=yes
fi
next prev parent reply other threads:[~2001-08-16 10:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-15 15:06 [PATCH] Fix libiberty to detect new cygwin exports Christopher Faylor
2001-08-15 15:24 ` Richard Henderson
2001-08-15 15:24 ` Christopher Faylor
2001-08-16 10:49 ` Christopher Faylor [this message]
2001-08-16 13:38 ` [RFA] Fix libiberty to detect new cygwin export, try 2 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
2001-08-15 15:24 ` 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=20010816134928.A7982@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).