From: Eli Zaretskii <eliz@gnu.org>
To: DJ Delorie <dj@redhat.com>
Cc: gcc-patches@gcc.gnu.org, gdb-patches@sourceware.org
Subject: Re: MinGW compilation warnings in libiberty's waitpid.c
Date: Sun, 21 May 2017 15:32:00 -0000 [thread overview]
Message-ID: <83wp9ans43.fsf@gnu.org> (raw)
In-Reply-To: <xnwp9cgvuu.fsf@greed.delorie.com> (message from DJ Delorie on Fri, 19 May 2017 21:28:25 -0400)
> From: DJ Delorie <dj@redhat.com>
> Cc: gcc-patches@gcc.gnu.org, gdb-patches@sourceware.org
> Date: Fri, 19 May 2017 21:28:25 -0400
>
>
> 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
>
Hmm... no, this doesn't solve the problem. The expansion of AC_LIBOBJ
for waitpid is gone from the configure script, but the value of
LIBOBJS in libiberty/Makefile still includes waitpid.o. What else is
related to this?
One caveat: I needed to hack config/override.m4 to allow me to run
autoconf 2.69 I have installed, because otherwise it insists on
autoconf 2.64 which I don't have. I hope this isn't the reason for
the incomplete solution.
next prev parent reply other threads:[~2017-05-21 15:32 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-08 15:27 Eli Zaretskii
2017-05-19 15:36 ` Pedro Alves
2017-05-19 17:25 ` Eli Zaretskii
2017-05-20 1:28 ` DJ Delorie
2017-05-21 15:32 ` Eli Zaretskii [this message]
2017-05-22 19:38 ` DJ Delorie
2017-05-23 19:25 ` Eli Zaretskii
2017-05-23 19:37 ` DJ Delorie
2017-05-24 2:23 ` Eli Zaretskii
2017-05-24 2:26 ` DJ Delorie
2017-05-24 18:31 ` Eli Zaretskii
2017-05-24 21:36 ` DJ Delorie
2017-05-26 8:08 ` Eli Zaretskii
2017-05-26 16:30 ` Joel Brobecker
2017-05-26 17:43 ` Eli Zaretskii
2017-05-26 22:02 ` Joel Brobecker
2017-05-26 18:04 ` DJ Delorie
2017-05-27 11:16 ` Iain Buclaw
2017-05-30 17:11 ` 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=83wp9ans43.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=dj@redhat.com \
--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