From: Eric Blake <eblake@redhat.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: bruno@clisp.org, Paul Eggert <eggert@cs.ucla.edu>,
bug-gnulib@gnu.org, emacs-devel@gnu.org
Subject: Re: syncing Emacs from sources maintained elsewhere
Date: Fri, 28 Jan 2011 15:40:08 -0700 [thread overview]
Message-ID: <4D4345C8.3040105@redhat.com> (raw)
In-Reply-To: <83zkqkhd0j.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1310 bytes --]
On 01/28/2011 03:36 PM, Eli Zaretskii wrote:
>> Date: Fri, 28 Jan 2011 13:06:21 -0800
>> From: Paul Eggert <eggert@cs.ucla.edu>
>> CC: Bruno Haible <bruno@clisp.org>, bug-gnulib@gnu.org,
>> emacs-devel@gnu.org
>>
>> Gnulib uses #include_next only on compilers that support
>> #include_next, and uses plain #include (to an absolute file name)
>> otherwise.
>
> Yes, I saw that. But I don't see how I can use that trick in this
> case. Unlike gnulib, which does this for the machine where the
> software is built, I need to produce a getopt.h file that will work on
> any machine. And since there's no standard place to install system
> headers on Windows machines, I don't see what absolute file name I
> could possibly use. Maybe I'm missing something.
Can you assume that emacs will always be built with gcc on Windows, or
are there people that insist on building with a non-free compiler?
#include_next is supported by gcc, so the question boils down to one of
how many compilers you are trying to support (and whether those other
compilers also have either #include_next or something else that
functions the same and can still be #ifdef/#Pragma'd into the header).
--
Eric Blake eblake@redhat.com +1-801-349-2682
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 619 bytes --]
next prev parent reply other threads:[~2011-01-28 22:40 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-11 0:50 syncing Emacs from sources maintained elsewhere Paul Eggert
2011-01-11 1:38 ` Miles Bader
2011-01-11 4:39 ` Paul Eggert
2011-01-17 20:37 ` Paul Eggert
2011-01-17 21:35 ` Stefan Monnier
2011-01-17 22:12 ` Paul Eggert
2011-01-18 10:11 ` Andy Moreton
2011-01-18 15:20 ` Eli Zaretskii
2011-01-18 18:13 ` Paul Eggert
2011-01-18 22:57 ` Eli Zaretskii
2011-01-19 0:36 ` Paul Eggert
2011-01-19 15:03 ` Eli Zaretskii
2011-01-19 1:20 ` Glenn Morris
2011-01-19 6:04 ` Paul Eggert
[not found] ` <4D368D16.7020702@swipnet.se>
2011-01-19 9:00 ` Glenn Morris
2011-01-19 10:38 ` Paul Eggert
2011-01-19 15:54 ` bug#7859: " Jan Djärv
2011-01-19 23:44 ` Paul Eggert
2011-01-20 0:21 ` Eli Zaretskii
2011-01-20 6:45 ` Jan Djärv
2011-01-20 7:51 ` Paul Eggert
2011-01-20 11:26 ` Jan D.
2011-01-19 23:49 ` Paul Eggert
2011-01-20 2:30 ` Tom Tromey
2011-01-20 0:27 ` Eric Blake
2011-01-23 12:39 ` Eli Zaretskii
2011-01-23 20:38 ` Paul Eggert
2011-01-24 4:08 ` Eli Zaretskii
2011-01-24 23:48 ` Paul Eggert
2011-01-25 4:02 ` Eli Zaretskii
2011-01-26 15:43 ` Eli Zaretskii
2011-01-27 9:22 ` Paul Eggert
2011-01-27 9:55 ` Eli Zaretskii
2011-01-27 10:29 ` Bruno Haible
2011-01-28 10:09 ` Eli Zaretskii
2011-01-28 21:06 ` Paul Eggert
2011-01-28 22:36 ` Eli Zaretskii
2011-01-28 22:40 ` Eric Blake [this message]
2011-01-29 8:48 ` Eli Zaretskii
2011-01-29 9:32 ` Simon Josefsson
2011-01-29 10:24 ` Eli Zaretskii
2011-01-27 20:50 ` gnulib strftime, Emacs, and nanosecond-resolution time stamps Paul Eggert
2011-01-24 6:18 ` syncing Emacs from sources maintained elsewhere Ralf Wildenhues
2011-01-29 10:04 ` Eli Zaretskii
2011-01-31 8:19 ` Paul Eggert
2011-01-29 12:53 ` Eli Zaretskii
2011-01-29 15:46 ` Chong Yidong
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=4D4345C8.3040105@redhat.com \
--to=eblake@redhat.com \
--cc=bruno@clisp.org \
--cc=bug-gnulib@gnu.org \
--cc=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).