From: Eli Zaretskii <eliz@gnu.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: emacs-devel@gnu.org
Subject: Resolving conflicts between gnulib and nt/inc headers
Date: Sat, 30 Mar 2013 20:29:11 +0300 [thread overview]
Message-ID: <83ehew4x08.fsf@gnu.org> (raw)
In my work on building the w32 Emacs by running the Posix configury, I
hit a problem with headers produced in lib/ which conflict with the
headers we have in nt/inc/ and with the MinGW system headers.
In the current Windows build scripts, most of the lib/*.in.h templates
are not edited into the corresponding *.h files, so these problems
never arise. But when using the Posix build procedure, lib/Makefile
is produced such that most of these headers are generated
unconditionally (so I cannot control that from the configure script).
Here's a partial list of those headers:
inttypes.h
sys/stat.h
time.h
signal.h
stdio.h
For now, I'm forced to use a very dirty trick: define some macro that
forces gnulib headers to just #include_next the same header either
from nt/inc or from the syste, include directory. E.g., to bypass
gnulib's time.h, I define _GL_TIME_H (yuck!). But I certainly hope
there is a cleaner way, or perhaps gnulib maintainers could add a
cleaner way if there isn't one already. E.g., how can I prevent
certain headers from being produced from their *.in.h templates?
Any suggestions are welcome. TIA.
P.S. Progress report: (1) the configure script runs and produces a
correct src/config.h; (2) the programs in lib-src compile and link OK;
(3) C sources in src/ compile with a few warnings and one error.
next reply other threads:[~2013-03-30 17:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-30 17:29 Eli Zaretskii [this message]
2013-03-30 19:00 ` Resolving conflicts between gnulib and nt/inc headers Paul Eggert
2013-03-30 21:21 ` 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=83ehew4x08.fsf@gnu.org \
--to=eliz@gnu.org \
--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).