unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Bob Floyd" <bobfloyd@comcast.net>
To: <emacs-devel@gnu.org>
Subject: Compiling with MSYS2
Date: Mon, 9 Aug 2021 12:32:18 -0700	[thread overview]
Message-ID: <001701d78d55$46389990$d2a9ccb0$@net> (raw)

[-- Attachment #1: Type: text/plain, Size: 2256 bytes --]

HI,

 

Am attempting to compile emacs on Windows 64 by following instructions
INSTALL.W64\nt - emacs.git - Emacs source repository (gnu.org)
<https://git.savannah.gnu.org/cgit/emacs.git/tree/nt/INSTALL.W64>  and ran
into this configuration problem. Anyone have insight into the issue?

 

# ./autogen.sh

Checking whether you have the necessary tools...

(Read INSTALL.REPO for more details on building Emacs) Checking for autoconf
(need at least version 2.65) ... ok Your system has the required tools.

Building aclocal.m4 ...

Running 'autoreconf -fi -I m4' ...

Configuring local git repository...

'.git/config' -> '.git/config.~1~'

git config transfer.fsckObjects 'true'

git config diff.cpp.xfuncname '!^[
\t]*[A-Za-z_][A-Za-z_0-9]*:[[:space:]]*($|/[/*])

^((::[[:space:]]*)?[A-Za-z_][A-Za-z_0-9]*[[:space:]]*\(.*)$

^((#define[[:space:]]|DEFUN).*)$'

git config diff.elisp.xfuncname
'^\([^[:space:]]*def[^[:space:]]+[[:space:]]+([^()[:space:]]+)'

git config diff.m4.xfuncname '^((m4_)?define|A._DEFUN(_ONCE)?)\([^),]*'

git config diff.make.xfuncname
'^([$.[:alnum:]_].*:|[[:alnum:]_]+[[:space:]]*([*:+]?[:?]?|!?)=|define .*)'

git config diff.shell.xfuncname
'^([[:space:]]*[[:alpha:]_][[:alnum:]_]*[[:space:]]*\(\)|[[:alpha:]_][[:alnu
m:]_]*=)'

git config diff.texinfo.xfuncname '^@node[[:space:]]+([^,[:space:]][^,]+)'

Installing git hooks...

'build-aux/git-hooks/commit-msg' -> '.git/hooks/commit-msg'

'build-aux/git-hooks/pre-commit' -> '.git/hooks/pre-commit'

'build-aux/git-hooks/prepare-commit-msg' -> '.git/hooks/prepare-commit-msg'

'.git/hooks/applypatch-msg.sample' -> '.git/hooks/applypatch-msg'

'.git/hooks/pre-applypatch.sample' -> '.git/hooks/pre-applypatch'

You can now run './configure'.

 

Bob@Cache MSYS /c/EmacsGit/emacs

# ./configure --prefix=/c/emacs/emacsgit --without-dbus

configure: loading site script /etc/config.site checking for xcrun... no
checking for GNU Make... make checking build system type... x86_64-pc-msys
checking host system type... x86_64-pc-msys

configure: error: Emacs does not support 'x86_64-pc-msys' systems.

If you think it should, please send a report to bug-gnu-emacs@gnu.org.

Check 'etc/MACHINES' for recognized configuration names.

 

Bob@Cache MSYS /c/EmacsGit/emacs

#

 

 


[-- Attachment #2: Type: text/html, Size: 5653 bytes --]

             reply	other threads:[~2021-08-09 19:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-09 19:32 Bob Floyd [this message]
2021-08-09 22:12 ` Compiling with MSYS2 Óscar Fuentes
2021-08-10  8:48 ` Arthur Miller

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='001701d78d55$46389990$d2a9ccb0$@net' \
    --to=bobfloyd@comcast.net \
    --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).