From: DJ Delorie <dj@redhat.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gcc-patches@gcc.gnu.org, gdb-patches@sourceware.org
Subject: Re: MinGW compilation warnings in libiberty's waitpid.c
Date: Sat, 20 May 2017 05:02:00 -0000 [thread overview]
Message-ID: <xnwp9cgvuu.fsf@greed.delorie.com> (raw)
In-Reply-To: <83inlbcqsp.fsf@gnu.org> (message from Eli Zaretskii on Mon, 08 May 2017 18:27:18 +0300)
Please try this patch, since my mingw environment is old:
Index: libiberty/ChangeLog
===================================================================
--- libiberty/ChangeLog (revision 248307)
+++ libiberty/ChangeLog (working copy)
@@ -1,3 +1,7 @@
+2017-05-19 Eli Zaretskii <eliz@gnu.org>
+
+ * configure.ac (*-*-mingw*): Don't build waitpid.c.
+
2017-05-02 Iain Buclaw <ibuclaw@gdcproject.org>
* d-demangle.c (dlang_hexdigit): New function.
Index: libiberty/configure.ac
===================================================================
--- libiberty/configure.ac (revision 248307)
+++ libiberty/configure.ac (working copy)
@@ -493,7 +493,6 @@
AC_LIBOBJ([strnlen])
AC_LIBOBJ([strverscmp])
AC_LIBOBJ([vasprintf])
- AC_LIBOBJ([waitpid])
for f in $funcs; do
case "$f" in
next prev parent reply other threads:[~2017-05-20 1:28 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-08 15:30 Eli Zaretskii
2017-05-19 15:40 ` Pedro Alves
2017-05-19 17:26 ` Eli Zaretskii
2017-05-20 5:02 ` DJ Delorie [this message]
2017-05-21 16:12 ` Eli Zaretskii
2017-05-22 19:55 ` DJ Delorie
2017-05-23 19:26 ` Eli Zaretskii
2017-05-23 19:38 ` DJ Delorie
2017-05-24 2:26 ` Eli Zaretskii
2017-05-24 3:31 ` DJ Delorie
2017-05-24 18:47 ` Eli Zaretskii
2017-05-24 22:16 ` DJ Delorie
2017-05-26 8:54 ` Eli Zaretskii
2017-05-26 16:38 ` Joel Brobecker
2017-05-26 18:04 ` Eli Zaretskii
2017-05-27 0:28 ` Joel Brobecker
2017-05-26 18:14 ` DJ Delorie
2017-05-27 15:58 ` Iain Buclaw
2017-05-30 17:23 ` Joel Brobecker
2017-06-06 17:54 ` Iain Buclaw
2017-06-07 12:38 ` Joel Brobecker
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=xnwp9cgvuu.fsf@greed.delorie.com \
--to=dj@redhat.com \
--cc=eliz@gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=gdb-patches@sourceware.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).