From: Po Lu <luangruo@yahoo.com>
To: emacs-devel@gnu.org
Cc: Paul Eggert <eggert@cs.ucla.edu>
Subject: Re: master f6fb2b9e1f: Port better to C23 bool+true+false keywords
Date: Wed, 28 Sep 2022 19:15:20 +0800 [thread overview]
Message-ID: <87leq37nsn.fsf@yahoo.com> (raw)
In-Reply-To: <20220928080912.B925DC00615@vcs2.savannah.gnu.org> (Paul Eggert's message of "Wed, 28 Sep 2022 04:09:11 -0400 (EDT)")
One of the gnulib changes results in this on MS-DOS:
In file included from ./stdlib.h:100,
from ./stdlib.h:36,
from getopt.c:27:
./unistd.h:663:3: #error "Please include config.h first."
In file included from ./stdlib.h:100,
from ./stdlib.h:36,
from getopt.c:27:
./unistd.h:1058: error: syntax error before "extern"
In file included from ./stdlib.h:36,
from getopt.c:27:
./stdlib.h:804: error: syntax error before "extern"
getopt.c:381: error: syntax error before "int"
getopt.c: In function `_getopt_initialize':
getopt.c:388: error: `d' undeclared (first use in this function)
getopt.c:388: error: (Each undeclared identifier is reported only once
getopt.c:388: error: for each function it appears in.)
getopt.c:395: error: `optstring' undeclared (first use in this function)
getopt.c:405: error: `posixly_correct' undeclared (first use in this function)
that is after I added
/^ASSERT_H *=/s/@[^@\n]*@/alloca.h/
and
s/= @GL_GENERATE_ASSERT_H_CONDITION@/= 0/
to sedlibmk.inp, and
/^#undef HAVE_STDBOOL_H/#define HAVE_STDBOOL_H/
to sed2v2.inp. AFAICT, both headers are present in DJGPP.
_LIBC is also not defined, so getopt is really including config.h. Any
ideas?
next parent reply other threads:[~2022-09-28 11:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <166435255086.25417.1796739399648878324@vcs2.savannah.gnu.org>
[not found] ` <20220928080912.B925DC00615@vcs2.savannah.gnu.org>
2022-09-28 11:15 ` Po Lu [this message]
2022-09-28 15:41 ` master f6fb2b9e1f: Port better to C23 bool+true+false keywords Eli Zaretskii
2022-09-29 0:17 ` Po Lu
2022-09-29 6:10 ` Eli Zaretskii
2022-09-28 16:57 ` Paul Eggert
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=87leq37nsn.fsf@yahoo.com \
--to=luangruo@yahoo.com \
--cc=eggert@cs.ucla.edu \
--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).