From: Stephen Leake <stephen_leake@stephe-leake.org>
To: emacs-devel <emacs-devel@gnu.org>
Subject: build failure 2 emacs-26 branch on Mingw64
Date: Mon, 01 Jan 2018 07:19:05 -0600 [thread overview]
Message-ID: <86d12tvhrq.fsf@stephe-leake.org> (raw)
Building emacs-26 branch on Mingw64, in a fresh checkout, make fails
with:
make[2]: Leaving directory 'C:/Projects/emacs/emacs-26/lisp'
make[1]: *** No rule to make target '../lisp/\n', needed by '../etc/DOC'. Stop.
make[1]: Leaving directory 'C:/Projects/emacs/emacs-26/src'
make: *** [Makefile:415: src] Error 2
This is due to a bad sed command for building lisp.mk. The current
command is:
${AM_V_GEN}( printf 'shortlisp = \\\n'; \
sed -n 's/^[ \t]*(load "\([^"]*\)".*/\1/p' $< | \
sed -e 's/$$/.elc \\/' -e 's/\.el\.elc/.el/'; \
echo "" ) > $@
The escaped backslashes need to be doubled:
${AM_V_GEN}( printf 'shortlisp = \\\\\n'; \
sed -n 's/^[ \t]*(load "\([^"]*\)".*/\1/p' $< | \
sed -e 's/$$/.elc \\\\/' -e 's/\.el\.elc/.el/'; \
echo "" ) > $@
There are three executables involved that determine the backslash
quoting required: make, bash, and sed. I have:
$ make --version
GNU Make 4.2.1
Built for x86_64-w64-mingw32
Copyright (C) 1988-2016 Free Software Foundation, Inc.
$ bash --version
GNU bash, version 4.4.12(1)-release (x86_64-pc-msys)
Copyright (C) 2016 Free Software Foundation, Inc.
$ sed --version
sed (GNU sed) 4.4
Copyright (C) 2017 Free Software Foundation, Inc.
all installed by mingw64 pacman fairly recently; the executable files
are all dated Feb 2017.
--
-- Stephe
next reply other threads:[~2018-01-01 13:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-01 13:19 Stephen Leake [this message]
2018-01-01 13:41 ` build failure 2 emacs-26 branch on Mingw64 Richard Copley
2018-01-01 14:05 ` Eli Zaretskii
2018-01-01 17:41 ` Stephen Leake
2018-01-01 17:52 ` Richard Copley
2018-01-01 18:41 ` Stephen Leake
2018-01-01 19:57 ` 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=86d12tvhrq.fsf@stephe-leake.org \
--to=stephen_leake@stephe-leake.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).