From: Stephen Leake <stephen_leake@stephe-leake.org>
To: emacs-devel <emacs-devel@gnu.org>
Subject: Re: build failure emacs-26 branch on Mingw64
Date: Mon, 01 Jan 2018 11:51:12 -0600 [thread overview]
Message-ID: <86zi5xtqlr.fsf@stephe-leake.org> (raw)
In-Reply-To: <CAPM58oim=cXjrgM7un828TJ9nZxyiWUkLGafrW7+GWDdBWTHNg@mail.gmail.com> (Richard Copley's message of "Mon, 1 Jan 2018 13:15:02 +0000")
Richard Copley <rcopley@gmail.com> writes:
> On 1 January 2018 at 12:51, Andreas Schwab <schwab@linux-m68k.org> wrote:
>> On Jan 01 2018, Stephen Leake <stephen_leake@stephe-leake.org> wrote:
>>
>>> The sed command that gives the error is:
>>>
>>> -e 's;\(#.*PATH_SITELOADSEARCH\).*$$;\1 "'"$${w32locallisppath//;/\\;}"'";'
>>>
>>> There is an unquoted ; in the replacement, but quoting that does not fix
>>> the error.
>>
>> The regexp separator for the s command should be changed to something
>> else than `;' to avoid a quoting nightmare.
>>
>>> I'm guessing the reference to 'w32locallisppath' is supposed to replace
>>> the Unix path separator : with the Windows path separator ; .
>>
>> No, it replaces `;' with `\;' so that it can be interpolated into the
>> replacement part of the s command.
>
> Building the emacs-26 branch from scratch works fine for me.
I'm guessing you are using the same tools I am.
Are you running configure from the mingw64 shell? Which make is
first in path?
As discussed in the thread on my other build failure, this is fixed by
using /usr/bin/make
> If I insert an echo command in Makefile (see patch below), then run
> "make epaths-force-w32",
You can get the same effect by removing the '@'; that makes the entire
command visible.
--
-- Stephe
prev parent reply other threads:[~2018-01-01 17:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-01 11:34 build failure emacs-26 branch on Mingw64 Stephen Leake
2018-01-01 12:33 ` Stephen Leake
2018-01-01 12:51 ` Andreas Schwab
2018-01-01 13:15 ` Richard Copley
2018-01-01 17:51 ` Stephen Leake [this message]
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=86zi5xtqlr.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).