unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Paul Eggert <eggert@cs.ucla.edu>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: bug#13026: Assume POSIX 1003.1-1988 or later for signal.h.
Date: Sat, 08 Dec 2012 09:34:05 -0800	[thread overview]
Message-ID: <50C37A0D.4030307@cs.ucla.edu> (raw)
In-Reply-To: <831uf0n964.fsf@gnu.org>

On 12/08/2012 02:13 AM, Eli Zaretskii wrote:
>> Date: Fri, 07 Dec 2012 18:40:57 -0800
>> > From: Paul Eggert <eggert@cs.ucla.edu>
>> > 
>> > 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.

> That requires Windows to use the Posix configure script.

I was thinking of something more modest, namely to change
nt/configure.bat to copy the needed rules from
lib/gnulib.mk to lib/Makefile.  This step wouldn't
all need to be done in configure.bat; it could be
precomputed on a POSIXish platform, if the Windows tools
aren't up to doing what 'sed' can do.  Ideally lib/makefile.w32-in
could just say "include gnulib.mk" but it might need
to include a modified version of gnulib.mk instead.

But if the plan is to port 'configure' to Windows perhaps
this idea would be a distraction.



  reply	other threads:[~2012-12-08 17:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <50B7062F.1010901@cs.ucla.edu>
     [not found] ` <83sj7suxdn.fsf@gnu.org>
     [not found]   ` <50B7D5BC.5060606@cs.ucla.edu>
     [not found]     ` <83ehjbv5cc.fsf@gnu.org>
     [not found]       ` <50BC0104.3070303@cs.ucla.edu>
     [not found]         ` <83k3sxr5j6.fsf@gnu.org>
     [not found]           ` <50C2A8B9.3030205@cs.ucla.edu>
2012-12-08 10:13             ` bug#13026: Assume POSIX 1003.1-1988 or later for signal.h Eli Zaretskii
2012-12-08 17:34               ` Paul Eggert [this message]
2012-12-08 18:45                 ` Gnulib automation on Windows (was: bug#13026: Assume POSIX 1003.1-1988 or later for signal.h.) 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=50C37A0D.4030307@cs.ucla.edu \
    --to=eggert@cs.ucla.edu \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@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).