From: Christoph <cschol2112@googlemail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: getopt_.h on Windows
Date: Sun, 06 Feb 2011 21:14:43 -0700 [thread overview]
Message-ID: <4D4F71B3.8060906@gmail.com> (raw)
In-Reply-To: <831v3ktrsk.fsf@gnu.org>
On 2/6/2011 9:03 PM, Eli Zaretskii wrote:
> Always, or because getopt.in.h was changed lately? If the former,
> then I did something wrong, because that's not what I meant to happen.
> If the latter, someone needs to regenerate getopt_.h and commit it to
> the repository.
This is the error I get in a clean trunk checkout:
mingw32-make -w getopt_.h-CMD
mingw32-make[2]: Entering directory `D:/devel/emacs/emacs-bzr/trunk/lib'
getopt.in.h or ../arg-nonnull.h is newer than getopt_.h.
Run "gmake getopt_h" in the lib/ subdirectory.
You will need GNU Sed to be installed.
exit -1
mingw32-make[2]: *** [getopt_.h-CMD] Error -1
mingw32-make[2]: Leaving directory `D:/devel/emacs/emacs-bzr/trunk/lib'
mingw32-make[1]: *** [getopt_.h] Error 2
mingw32-make[1]: Leaving directory `D:/devel/emacs/emacs-bzr/trunk/lib'
mingw32-make: *** [bootstrap-gmake] Error 2
> Also, what do you mean by "manually"? The intent was to run a
> specific Make rule, not to create the file by hand.
Well, following the instructions above, i.e. goint to lib/ and running
mingw32-make getopt_.h. Manually as opposed to by a make rule.
> The need for regenerating getopt_.h does not depend on Sed, it depends
> on getopt.in.h being newer.
Sure, but in order to generate it, you need Sed, right?
>> Is there any reason we couldn't just check for Sed and abort
>> if it is not present and otherwise build getopt_.h automatically?
>
> Patches welcome, but please remember that Windows Makefiles support
> both a Unixy shell and the Windows cmd.exe, so whatever you want to
> add must work with both of them.
OK.
Thanks,
Christoph
next prev parent reply other threads:[~2011-02-07 4:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-07 2:09 getopt_.h on Windows Christoph
2011-02-07 4:03 ` Eli Zaretskii
2011-02-07 4:14 ` Christoph [this message]
2011-02-07 12:29 ` Andy Moreton
2011-02-07 13:56 ` Eli Zaretskii
2011-02-07 15:54 ` Andy Moreton
2011-02-07 19:15 ` Eli Zaretskii
2011-02-08 0:33 ` Sean Sieger
2011-02-07 22:17 ` Andreas Schwab
2011-02-07 23:19 ` Lennart Borgman
-- strict thread matches above, loose matches on Subject: below --
2011-02-08 1:31 grischka
2011-02-08 3:55 ` 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=4D4F71B3.8060906@gmail.com \
--to=cschol2112@googlemail.com \
--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).