emacs-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Failure building Emacs master on MSYS2 [MSYS2 PKG]


From: Bruno Haible
Subject: Re: Failure building Emacs master on MSYS2 [MSYS2 PKG]
Date: Wed, 07 May 2025 01:00:40 +0200

Angelo Graziosi wrote:
> wget source.tar.gz
> unpack source.tar.gz
> cd source
> ./configure
> make
> 
> 
> So there are not files generated by previous builds...
> 
> I use as source: 
> http://git.savannah.gnu.org/cgit/emacs.git/snapshot/emacs-master.tar.gz

These cannot be what you do. Because the emacs-master.tar.gz (and likewise
https://cgit.git.savannah.gnu.org/cgit/emacs.git/snapshot/emacs-71ee484cac3e0e5b68f006b4cca81c13ca6ce11e.tar.gz
 )
does not contain a configure script.

I turned on my MSYS2 VM and was about to attempt to reproduce your issue.
But I can't do that if you provide insufficient "How to reproduce"
information. I don't want to spend my time _guessing_ what the commands
on your side had been. You need to tell us these commands up-front.

Additionally, your configure command from
<https://lists.gnu.org/archive/html/emacs-devel/2025-05/msg00154.html>

./configure --prefix="/${PREFIXNAME}" \
                --build=x86_64-pc-cygwin \
                --without-dbus \
                --without-pop \
                --with-modules \
                --without-native-compilation \
                ${CHECK_OPT} \
                CFLAGS="-O2" || error_msg "Failure running configure"

is wrong: It lacks the option
  --host=x86_64-w64-mingw32
In an environment like this, you *must* specify the --host option,
otherwise configure tests may come out with the wrong results,
which in turn can produce the 'wint_t' error that you saw.
For more information about tested (working) recipes how to configure
GNU packages, see [1].

Also, the --build=x86_64-pc-cygwin option may be wrong, since you
are on MSYS2, not on Cygwin, and there are some differences
between both environments. It's generally best to *not* specify
a --build option, since config.guess is good enough on all platforms
I've seen in the last 20 years.

Bruno

[1] https://gitlab.com/ghwiki/gnow-how/-/wikis/Platforms/Configuration






reply via email to

[Prev in Thread] Current Thread [Next in Thread]