From: Paul Eggert <eggert@cs.ucla.edu>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 13026-done@debbugs.gnu.org
Subject: bug#13026: Assume POSIX 1003.1-1988 or later for signal.h.
Date: Fri, 07 Dec 2012 18:40:57 -0800 [thread overview]
Message-ID: <50C2A8B9.3030205@cs.ucla.edu> (raw)
In-Reply-To: <83k3sxr5j6.fsf@gnu.org>
On 12/04/2012 11:17 AM, Eli Zaretskii wrote:
> This will need additions to lib/makefile.w32-in, to get the new
> modules to compile into libgnu.a.
I added enough so that I think it should compile, as trunk bzr
111151, and I'm marking this bug as fixed. Someone with
Microsoft expertise should look at that as I expect more
needs to be added to the Microsoftish build procedure.
As an aside, it'd be nicer if lib/Makefile were computed more
automatically from lib/gnulib.mk on Microsoft platforms, so
that this sort of thing wouldn't require manual editing.
> The likes of "#ifdef SIGFOO" are not Autoconf tests.
Yes, but I was talking more about the Autoconf style, which is to
look for individual features rather than operating systems. This
style tends to work better when porting among a large number of
platforms. The style doesn't always require Autoconf help.
It's true that the style has some downsides too, but they're less
important in practice. Here, in particular, I don't expect
many readers of the Emacs source code would think that
Emacs works only on POSIXish platforms, given all the
occurrences of "#ifdef WINDOWSNT" and "#ifdef DOS_NT" that
they'd find with even a casual perusal.
next prev parent reply other threads:[~2012-12-08 2:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-29 6:52 bug#13026: Assume POSIX 1003.1-1988 or later for signal.h Paul Eggert
2012-11-29 17:33 ` Eli Zaretskii
2012-11-29 21:38 ` Paul Eggert
2012-11-30 8:54 ` Eli Zaretskii
2012-12-03 1:31 ` Paul Eggert
2012-12-04 19:17 ` Eli Zaretskii
2012-12-08 2:40 ` Paul Eggert [this message]
2012-12-08 10:09 ` Eli Zaretskii
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=50C2A8B9.3030205@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=13026-done@debbugs.gnu.org \
--cc=eliz@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).