all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stephen Leake <stephen_leake@stephe-leake.org>
To: emacs-devel <emacs-devel@gnu.org>
Subject: Re: build failure 2 emacs-26 branch on Mingw64
Date: Mon, 01 Jan 2018 12:41:55 -0600	[thread overview]
Message-ID: <86vaglto98.fsf@stephe-leake.org> (raw)
In-Reply-To: <CAPM58ohUdCm60=YyggV_7C0kwemNAYdjJsc0O8dHLQaw7UiE4w@mail.gmail.com> (Richard Copley's message of "Mon, 1 Jan 2018 17:52:33 +0000")

Richard Copley <rcopley@gmail.com> writes:

> On 1 January 2018 at 17:41, Stephen Leake
> <stephen_leake@stephe-leake.org> wrote:
>> Eli Zaretskii <eliz@gnu.org> writes:
>>
>>> On January 1, 2018 3:41:17 PM GMT+02:00, Richard Copley <rcopley@gmail.com> wrote:
>>>> > $ make --version
>>>> > GNU Make 4.2.1
>>>> > Built for x86_64-w64-mingw32
>>>> > Copyright (C) 1988-2016 Free Software Foundation, Inc.
>>>>
>>>> You have a native make on the path in your MSYS bash process.
>>>> "make" should be the MSYS make:
>>>>
>>>> $ make --version
>>>> GNU Make 4.2.1
>>>> Built for x86_64-pc-msys
>>>> Copyright (C) 1988-2016 Free Software Foundation, Inc.
>>>
>>> Right.  And I believe Sed is not an MSYS Sed, either, because that one
>>> should be version 4.2.2, not 4.4.
>>> Which could also explain the other problem Stephen reported.
>>
>> Hmm. Then the instructions in nt/INSTALL.W64 are wrong; it says to run
>> autgen and configure from the mingw64.exe shell, which puts mingw64/bin
>> first in path.
>
> I think what's unusual about your setup is that you have the native
> GNU Make installed under the name "make.exe" on your path. By default,
> MSYS2 installs it as "mingw32-make.exe". 

Ah, you are correct. I did that on purpose, so I can just run 'make' and
C-c C-k in an Emacs *compilation* buffer can interrupt it. But I forgot
about it until now ...

>> I'll try rebuilding using the msys shell and/or msys make from the mingw
>> shell, and propose a patch for INSTALL.W64

export MAKE=/usr/bin/bash; configure

works for me.

But since I have a non-standard mingw setup, there's no need to change
INSTALL.W64; I'll just keep better notes on my own config.

Thanks.

-- 
-- Stephe



  reply	other threads:[~2018-01-01 18:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-01 13:19 build failure 2 emacs-26 branch on Mingw64 Stephen Leake
2018-01-01 13:41 ` 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 [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=86vaglto98.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 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.