From: Glenn Morris <rgm@gnu.org>
To: Espen Wiborg <espenhw@grumblesmurf.org>
Cc: emacs-pretest-bug@gnu.org, kifer@cs.sunysb.edu
Subject: Re: make bootsrap problems
Date: Tue, 27 May 2008 15:29:00 -0400 [thread overview]
Message-ID: <v17idf5ywz.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <874p8jvpfr.fsf@grumblesmurf.org> (Espen Wiborg's message of "Tue, 27 May 2008 15:36:56 +0200")
Espen Wiborg wrote:
> The problem is that the generated sed script is missing a line
> continuation backslash.
It works for me on several varieties of RHEL, and on Debian testing.
> The following patch fixes:
Not for me. Applying this patch, my generated Makefile.in ends up
containing:
ELCFILES = \\
$(lisp)/abbrev.elc \
rather than
ELCFILES = \
$(lisp)/abbrev.elc \
I guess it's something to do with sed and/or /bin/sh versions.
(It's not vital that this command work for everyone, though of course
that is what I would like.)
> Index: lisp/Makefile.in
> ===================================================================
> RCS file: /cvsroot/emacs/emacs/lisp/Makefile.in,v
> retrieving revision 1.123
> diff -c -r1.123 Makefile.in
> *** lisp/Makefile.in 27 May 2008 02:14:46 -0000 1.123
> --- lisp/Makefile.in 27 May 2008 13:21:27 -0000
> ***************
> *** 164,170 ****
> ## building Emacs.
> update-elclist:
> echo "/^ELCFILES/,/^$$/c\\" > temp.sed
> ! echo "ELCFILES = \\\\\\" >> temp.sed
> exclude=`echo $(COMPILE_FIRST) | sed -e 's, ,\\\\|,g' -e 's,\/,\\\\/,g'`; \
> ls $(lisp)/*.elc $(lisp)/*/*.elc | sed -e "/$$exclude/d" -e "s|^$(lisp)| \$$(lisp)|" -e 's/$$/ \\\\\\/' -e '$$ s/ \\\\//' >> temp.sed
> echo "" >> temp.sed
> --- 164,170 ----
> ## building Emacs.
> update-elclist:
> echo "/^ELCFILES/,/^$$/c\\" > temp.sed
> ! echo "ELCFILES = \\\\\\\\\\" >> temp.sed
> exclude=`echo $(COMPILE_FIRST) | sed -e 's, ,\\\\|,g' -e 's,\/,\\\\/,g'`; \
> ls $(lisp)/*.elc $(lisp)/*/*.elc | sed -e "/$$exclude/d" -e "s|^$(lisp)| \$$(lisp)|" -e 's/$$/ \\\\\\/' -e '$$ s/ \\\\//' >> temp.sed
> echo "" >> temp.sed
>
> Thermodynamics in a nutshell:
> 1st Law: You can't win. (Energy is conserved)
> 2nd Law: You can't break even. (Entropy)
> 0th Law: You can't even quit the game. (Closed systems) -- Taki Kogoma
I thought that was C.P. Snow.
next prev parent reply other threads:[~2008-05-27 19:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-27 9:56 make bootsrap problems Michael Kifer
2008-05-27 10:44 ` David Kastrup
2008-05-27 13:36 ` Espen Wiborg
2008-05-27 19:29 ` Glenn Morris [this message]
2008-05-28 0:44 ` Glenn Morris
2008-05-28 1:04 ` Glenn Morris
2008-05-28 7:08 ` Espen Wiborg
-- strict thread matches above, loose matches on Subject: below --
2008-05-28 7:57 Angelo Graziosi
2008-05-28 8:02 ` 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=v17idf5ywz.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=emacs-pretest-bug@gnu.org \
--cc=espenhw@grumblesmurf.org \
--cc=kifer@cs.sunysb.edu \
/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).