unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Issue building on MSWindows + msys
Date: Thu, 16 Nov 2023 07:45:01 +0200	[thread overview]
Message-ID: <831qcqqmjm.fsf@gnu.org> (raw)
In-Reply-To: <D7CBF573-2B2F-4B0C-A822-4307B135110D@aol.com> (message from Ergus on Wed, 15 Nov 2023 23:00:03 +0100)

> Date: Wed, 15 Nov 2023 23:00:03 +0100
> From: Ergus <spacibba@aol.com>
> 
> >Did you update any of your system utilities (like Grep) or libraries
> >lately?
> >
> Hi Eli:
> 
> I made a clean msys2 install and installed the same packages I had before. Everything from the official msys repositories 

I asked whether some of the system utilities and libraries are now
different from what they were before the clean install.  Because some
of those updates, and not some change in Emacs, could be the reason
for the problem you see.  For example, if you now have the latest
version of GCC, try to downgrade to the previous major GCC release,
and see if that helps.

> The issue is weird because the compilation continues after the error, and completes apparently successfully (ignoring the errors). Except if I try 'make -j' In that case the error aborts the build.

This could mean some issue with Make or with Bash.  But it's hard to
say without seeing the full output of the build that continues.

(In general, this should be discussed on the bug tracker, not here.)

> After compiling and installing, the new emacs installation actually works, but it shows some issues. However, I will double check them before opening a bug report. For example the history search (up arrow) in the mini buffer is not working and says that there is no history match... (But the history file is there and is not corrupted)

It should have been a bug report to begin with.



      reply	other threads:[~2023-11-16  5:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <pq5oqtzlurtwkspcesdvk7rtrtdu6ye6t6wnioto6wzx257vsm.ref@jdinp4e6ahna>
2023-11-15 14:57 ` Issue building on MSWindows + msys Ergus
2023-11-15 16:45   ` Eli Zaretskii
2023-11-15 18:18     ` Corwin Brust
2023-11-15 22:00     ` Ergus
2023-11-16  5:45       ` Eli Zaretskii [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=831qcqqmjm.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=help-gnu-emacs@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.
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).