From: Tom Tromey <tom@tromey.com>
To: Pedro Alves <pedro@palves.net>
Cc: Tom Tromey <tom@tromey.com>,
Mike Frysinger via Gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH 4/4] gnulib: import select
Date: Thu, 10 Jun 2021 12:11:22 -0600 [thread overview]
Message-ID: <87v96lio8l.fsf@tromey.com> (raw)
In-Reply-To: <YMFe/1a0iQOfvbE3@vapier> (Mike Frysinger's message of "Wed, 9 Jun 2021 20:38:23 -0400")
Mike> hmm, so how gnulib is integrated leads to "interesting" behavior. we don't
Mike> run configure against it, we only compile+link against it. so when gdb's
Mike> configure probes sys/select.h, it doesn't find it. and then the mingw files
Mike> (and files it includes) that are protected by HAVE_SYS_SELECT_H are not used.
If gnulib provides a header, and we definitely want to use it in gdb,
then I think the configury and the cpp checks can just be removed.
Tom
next prev parent reply other threads:[~2021-06-10 18:11 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-29 17:25 [PATCH 1/4] gnulib: import chown Mike Frysinger via Gdb-patches
2021-05-29 17:25 ` [PATCH 2/4] sim: v850: assume chown is available Mike Frysinger via Gdb-patches
2021-05-29 17:25 ` [PATCH 3/4] gnulib: import netdb Mike Frysinger via Gdb-patches
2021-06-07 14:27 ` Tom Tromey
2021-05-29 17:25 ` [PATCH 4/4] gnulib: import select Mike Frysinger via Gdb-patches
2021-06-07 14:29 ` Tom Tromey
2021-06-08 4:52 ` Mike Frysinger via Gdb-patches
2021-06-08 12:37 ` Tom Tromey
2021-06-09 12:27 ` Pedro Alves
2021-06-09 16:52 ` Mike Frysinger via Gdb-patches
2021-06-09 18:12 ` Pedro Alves
2021-06-09 18:32 ` Mike Frysinger via Gdb-patches
2021-06-09 23:30 ` Pedro Alves
2021-06-10 0:38 ` Mike Frysinger via Gdb-patches
2021-06-10 18:11 ` Tom Tromey [this message]
2021-06-07 14:23 ` [PATCH 1/4] gnulib: import chown Tom Tromey
2021-06-07 14:31 ` Eli Zaretskii via Gdb-patches
2021-06-08 1:15 ` Mike Frysinger via Gdb-patches
2021-06-08 2:32 ` Eli Zaretskii via Gdb-patches
2021-06-08 4:14 ` 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=87v96lio8l.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=pedro@palves.net \
/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