unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Pip Cet <pipcet@protonmail.com>
To: "Gerd Möllmann" <gerd.moellmann@gmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>,
	eller.helmut@gmail.com, emacs-devel@gnu.org
Subject: Re: MPS: unable to build due to assertion violation in igc_dump_check_object_starts
Date: Tue, 23 Jul 2024 22:47:42 +0000	[thread overview]
Message-ID: <DnyvB6h1bZ74lXZavREamEoj25lp6wnm_dfwFfcN4qt5PKsqy8BhT7-pYmUZeRs9ZfC9DSYairE0ngTPEEYYg0_x05S9rC3ItNJHu80aKBA=@protonmail.com> (raw)
In-Reply-To: <m21q3jrjmi.fsf@pro2.fritz.box>

On Tuesday, July 23rd, 2024 at 19:30, Gerd Möllmann <gerd.moellmann@gmail.com> wrote:
> Gerd Möllmann gerd.moellmann@gmail.com writes:
> 
> > Will apply the whole patch and report back.
> 
> And that works like a charm :-). Thanks, Pip!

I finally managed to build a working 32-bit emacs.exe using MSYS (I think that's what Eli is using; the 2017 release, right?) under Wine, and I can confirm it dumps and appears to work now, with the patch. The dumped bignum has the right value. I hope that's true for Eli's machine as well. I'm building without native compilation, though.

While we're on the subject, though, I had to modify mps a little to build with GCC. Are other people using a different compiler for mps? Or are there patches somewhere?

(I also ran into the "Write error to standard output: Success" issue, possibly because I ran wine from within Docker, so I ended up removing the failure exits from 'close_output_streams')

Pip



  reply	other threads:[~2024-07-23 22:47 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-23 12:58 MPS: unable to build due to assertion violation in igc_dump_check_object_starts Eli Zaretskii
2024-07-23 14:10 ` Gerd Möllmann
2024-07-23 14:26   ` Eli Zaretskii
2024-07-23 14:40     ` Eli Zaretskii
2024-07-23 14:52       ` Gerd Möllmann
2024-07-23 15:43         ` Eli Zaretskii
2024-07-23 16:29           ` Gerd Möllmann
2024-07-23 18:00             ` Eli Zaretskii
2024-07-23 18:37               ` Eli Zaretskii
2024-07-23 18:40                 ` Pip Cet
2024-07-23 18:48                   ` Gerd Möllmann
2024-07-23 19:12                     ` Pip Cet
2024-07-23 19:25                       ` Gerd Möllmann
2024-07-23 19:30                         ` Gerd Möllmann
2024-07-23 22:47                           ` Pip Cet [this message]
2024-07-24  3:50                             ` Gerd Möllmann
2024-07-24 11:27                             ` Eli Zaretskii
2024-07-24  8:01                   ` Helmut Eller
2024-07-24  8:21                     ` Pip Cet
2024-07-24  8:33                       ` Helmut Eller
2024-07-24  9:20                         ` Pip Cet
2024-07-24  9:39                           ` Helmut Eller
2024-07-24  9:54                             ` Pip Cet
2024-07-24 11:40                               ` Helmut Eller
2024-07-24 12:25                                 ` Pip Cet
2024-07-24 11:44                         ` Eli Zaretskii
2024-07-23 18:50                 ` Gerd Möllmann
2024-07-23 18:42               ` Gerd Möllmann
2024-07-23 18:49                 ` Eli Zaretskii
2024-07-23 18:59                   ` Gerd Möllmann
2024-07-23 14:42     ` Pip Cet
2024-07-23 16:28 ` Pip Cet

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='DnyvB6h1bZ74lXZavREamEoj25lp6wnm_dfwFfcN4qt5PKsqy8BhT7-pYmUZeRs9ZfC9DSYairE0ngTPEEYYg0_x05S9rC3ItNJHu80aKBA=@protonmail.com' \
    --to=pipcet@protonmail.com \
    --cc=eliz@gnu.org \
    --cc=eller.helmut@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=gerd.moellmann@gmail.com \
    /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).