From: Robert Pluim <rpluim@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: luangruo@yahoo.com, larsi@gnus.org, emacs-devel@gnu.org
Subject: Re: bug#54245: 29.0.50; select usage in GNUstep
Date: Mon, 14 Mar 2022 14:43:34 +0100 [thread overview]
Message-ID: <87v8wgejjt.fsf@gmail.com> (raw)
In-Reply-To: <83tuc0k7da.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 14 Mar 2022 15:10:09 +0200")
>>>>> On Mon, 14 Mar 2022 15:10:09 +0200, Eli Zaretskii <eliz@gnu.org> said:
>> I think this means we can now remove the checking for select in
>> configure, and the HAVE_SELECT define (I took a look, but then ran
>> into the w32 and msdos ports, and decided to stop :-) )
Eli> If that's your problem, you could convert HAVE_SELECT into DOS_NT, I
Eli> think.
Itʼs not really a problem, itʼs more "Is the issue serious enough to
potentially break builds for other people that I canʼt easily test"
Eli> The HAVE_SELECT in msdos.c is for the (old and quite defunct) MSDOS
Eli> build with Xlib (yes, there was such a beast: see those HAVE_X_WINDOWS
Eli> in msdos.c?), so IMNSHO we can simply drop HAVE_SELECT in msdos.c.
Although this makes it sound like Iʼm worrying too much about
potential breakage.
Robert
--
prev parent reply other threads:[~2022-03-14 13:43 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-04 15:30 bug#54245: 29.0.50; select usage in GNUstep Lars Ingebrigtsen
2022-03-04 16:10 ` Lars Ingebrigtsen
2022-03-04 16:15 ` Robert Pluim
2022-03-05 0:45 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-03-05 11:32 ` Robert Pluim
2022-03-05 19:00 ` Lars Ingebrigtsen
2022-03-14 9:22 ` Robert Pluim
2022-03-14 9:30 ` Po Lu
2022-03-14 13:12 ` Eli Zaretskii
2022-03-14 9:31 ` Lars Ingebrigtsen
2022-03-14 13:10 ` Eli Zaretskii
2022-03-14 13:20 ` Stefan Monnier
2022-03-14 13:48 ` Eli Zaretskii
2022-03-14 13:34 ` Po Lu
2022-03-14 13:59 ` Eli Zaretskii
2022-03-14 13:43 ` Robert Pluim [this message]
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=87v8wgejjt.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=larsi@gnus.org \
--cc=luangruo@yahoo.com \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.