From: Thien-Thi Nguyen <ttn@gnuvola.org>
To: Alexander Klimov <alserkli@inbox.ru>
Cc: emacs-devel@gnu.org
Subject: Re: preprocessing Makefile
Date: Thu, 19 Jul 2007 12:02:26 +0200 [thread overview]
Message-ID: <873azkzp71.fsf@ambire.localdomain> (raw)
In-Reply-To: <TheMailAgent.1cc348f24426e8a@26af22b499cdfd71bde4b> (Alexander Klimov's message of "Thu\, 19 Jul 2007 12\:41\:57 +0300 \(IDT\)")
() Alexander Klimov <alserkli@inbox.ru>
() Thu, 19 Jul 2007 12:41:57 +0300 (IDT)
One solution is to set CPP="gcc -E -undef" or at least -Ulinux in my
case, but I am not sure if this does not introduce other problems
(currently bootstrap fails for me even on a system that does not
have this problem with paths).
another one is to ditch the preprocessing altogether, shifting such
configuration duties fully to autoconf. i wonder why this was never
done. too hairy? certainly mucking w/ the preprocessor (generally,
build flow) was a large part of the pain for the vms port.
i understand that early autoconf was not up to the task of configuring
emacs, but perhaps these days it can be cajoled to DTRT. does anyone
object to this kind of revamp? if so, why?
thi
next prev parent reply other threads:[~2007-07-19 10:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-19 9:41 preprocessing Makefile Alexander Klimov
2007-07-19 10:02 ` Thien-Thi Nguyen [this message]
2007-07-19 21:21 ` Richard Stallman
2007-07-20 22:37 ` Thien-Thi Nguyen
2007-07-20 23:30 ` Thien-Thi Nguyen
2007-07-23 8:36 ` Alexander Klimov
2007-07-23 13:54 ` Alexander Klimov
2008-03-11 13:48 ` Alexander Klimov
2008-07-01 3:16 ` Glenn Morris
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=873azkzp71.fsf@ambire.localdomain \
--to=ttn@gnuvola.org \
--cc=alserkli@inbox.ru \
--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).