From: David Engster <deng@randomsample.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: acm@muc.de, emacs-devel@gnu.org
Subject: Re: Difficulty building older Emacsen: <tab> characters seemingly fouling things up.
Date: Sat, 06 Jun 2015 17:13:12 +0200 [thread overview]
Message-ID: <87sia4g99z.fsf@isaac.fritz.box> (raw)
In-Reply-To: <83sia4nafd.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 06 Jun 2015 18:06:30 +0300")
Eli Zaretskii writes:
>> Date: Sat, 06 Jun 2015 18:00:36 +0300
>> From: Eli Zaretskii <eliz@gnu.org>
>> Cc: emacs-devel@gnu.org
>>
>> Looks like line 143 should have had a backslash at its end, but
>> doesn't. Likewise, line 144 should have ended with a backslash I
>> don't understand how did it happen, as lib-src/Makefile.in from Emacs
>> 23.1 have these present.
>
> I seem to remember that the behavior of cpp changed at some point, and
> we needed to invoke it with the -traditional switch in order to avoid
> some trouble, perhaps precisely this one. (You may remember that in
> those days we used cpp to process Makefile.in files into Makefiles.)
>
> So perhaps reconfigure with "CPP='gcc -E -traditional' or somesuch.
Yes, one needs this change to compile older Emacsen:
http://article.gmane.org/gmane.emacs.diffs/102980
Building older Emacsen can be quite frustrating. I think I also had
problems with linking crt1.o or somesuch when creating older Emacs
binaries for the Buildbot.
-David
next prev parent reply other threads:[~2015-06-06 15:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-06 14:22 Difficulty building older Emacsen: <tab> characters seemingly fouling things up Alan Mackenzie
2015-06-06 15:00 ` Eli Zaretskii
2015-06-06 15:06 ` Eli Zaretskii
2015-06-06 15:13 ` David Engster [this message]
2015-06-14 19:22 ` Alan Mackenzie
2015-06-14 21:47 ` David Engster
2015-06-16 17:46 ` Alan Mackenzie
2015-06-06 15:05 ` Andreas Schwab
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87sia4g99z.fsf@isaac.fritz.box \
--to=deng@randomsample.de \
--cc=acm@muc.de \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.