From: Eli Zaretskii via Gdb-patches <gdb-patches@sourceware.org>
To: Mike Frysinger <vapier@gentoo.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] gnulib: import sys_wait
Date: Mon, 14 Jun 2021 17:43:23 +0300 [thread overview]
Message-ID: <83v96g5wxg.fsf@gnu.org> (raw)
In-Reply-To: <YMdpGwJPJOBR/Efe@vapier> (message from Mike Frysinger on Mon, 14 Jun 2021 10:35:07 -0400)
> Date: Mon, 14 Jun 2021 10:35:07 -0400
> From: Mike Frysinger <vapier@gentoo.org>
> Cc: gdb-patches@sourceware.org
>
> > AFAIU, this conflicts with what we have in gdbsupport/gdb_wait.h and
> > use in windows-nat.c and win32-low.cc. Worse, the Gnulib emulation of
> > this for Windows is (IMNSHO) less useful, since it doesn't support any
> > abnormal termination except the equivalent of SIGABRT (which causes
> > the Windows runtime to exit with status = 3). I tried to convince the
> > Gnulib folks to adopt a more useful emulation, similar to what we have
> > in gdb_wait.h, but AFAIR Bruno Haible rejected the idea.
>
> i don't think there's any conflicts. gdb* dirs probe the env w/out gnulib,
> so they'll see sys/wait.h is not available, and then the gdb_wait.h and such
> files will continue to be used.
>
> > Did you need this Gnulib module because those sims don't use
> > gdbsupport? And if so, is it possible to somehow avoid clashes
> > between this Gnulib module and what we have in gdb_wait.h?
>
> sim/ doesn't use gdbsupport/. the gdbsupport/ dir assumes it's used with
> only gdb/, and is C++, so i don't think trying to generalize it is worth
> the effort.
OK, if there are no conflicts here, then apologies for the noise. (I
never build the sim subdirectory in my builds of GDB.)
next prev parent reply other threads:[~2021-06-14 14:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-13 5:25 Mike Frysinger via Gdb-patches
2021-06-14 12:18 ` Eli Zaretskii via Gdb-patches
2021-06-14 14:35 ` Mike Frysinger via Gdb-patches
2021-06-14 14:43 ` Eli Zaretskii via Gdb-patches [this message]
2021-06-14 19:35 ` Mike Frysinger via Gdb-patches
2021-06-30 7:03 ` Mike Frysinger via Gdb-patches
2021-08-18 16:19 ` Mike Frysinger via Gdb-patches
2021-09-04 1:15 ` Mike Frysinger via Gdb-patches
2021-09-03 20:54 ` Simon Marchi via Gdb-patches
2021-09-04 7:41 ` Mike Frysinger via Gdb-patches
2021-09-07 14:51 ` Simon Marchi via Gdb-patches
2021-09-08 0:55 ` Mike Frysinger via Gdb-patches
2021-09-08 14:41 ` Simon Marchi via Gdb-patches
2021-09-08 20:20 ` Mike Frysinger via Gdb-patches
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=83v96g5wxg.fsf@gnu.org \
--to=gdb-patches@sourceware.org \
--cc=eliz@gnu.org \
--cc=vapier@gentoo.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