From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: MPS: unable to build due to assertion violation in igc_dump_check_object_starts Date: Wed, 24 Jul 2024 14:27:28 +0300 Message-ID: <864j8f81y7.fsf@gnu.org> References: <861q3k9sfb.fsf@gnu.org> <86ikww7zvf.fsf@gnu.org> <86h6cg7y59.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="30478"; mail-complaints-to="usenet@ciao.gmane.io" Cc: gerd.moellmann@gmail.com, eller.helmut@gmail.com, emacs-devel@gnu.org To: Pip Cet Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Wed Jul 24 13:28:12 2024 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1sWaAG-0007lc-7o for ged-emacs-devel@m.gmane-mx.org; Wed, 24 Jul 2024 13:28:12 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1sWa9g-0006ag-8Z; Wed, 24 Jul 2024 07:27:36 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1sWa9d-0006aP-G3 for emacs-devel@gnu.org; Wed, 24 Jul 2024 07:27:33 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1sWa9c-0008Ma-20; Wed, 24 Jul 2024 07:27:32 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=MIME-version:References:Subject:In-Reply-To:To:From: Date; bh=p303mINOoBzPwn8IlQtuV2OZW+QeX2Gbwcd1cXdGEkQ=; b=KIttX7dyfEMJ2pfiZVj1 /hc7LGt3pYSO+CKpTNvhpLggIudQliQfg0DIalYpnmjeEdNRPqwdqqY10OW3hCyrXYNiuB+SFu4Ai uRVH+y0cXScu/yklaxrCseKzCzlKmWETHPPVed5yZcCO+M4dKxMSCkdVCnNFMKT6yuON5wAk1lzdn 4Q7eTtOvUb22FlZ2KhYIgWRFRrxoT1xGNq9mRVK8ubfqkaUyp4VaEVqZ1+8CmspksK7FndocWpNwn 9bCXW6xleb9HRh0IiuafaqtInVP693VW6pBKQn9yhe2/9gr89EMEFBY8DY4GGRWZPQjR9Gpy/f/uQ ktCv/35RXgC+gQ==; In-Reply-To: (message from Pip Cet on Tue, 23 Jul 2024 22:47:42 +0000) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:322038 Archived-At: > Date: Tue, 23 Jul 2024 22:47:42 +0000 > From: Pip Cet > Cc: Eli Zaretskii , eller.helmut@gmail.com, emacs-devel@gnu.org > > On Tuesday, July 23rd, 2024 at 19:30, Gerd Möllmann 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?) MinGW and MSYS is many packages, so if you ask about the timestamp, you need to tell which package are you asking about. E.g., the latest runtime of the MinGW I use is from 2021, not 2017. > 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. Yes, it builds now and seems to work, thanks. > 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? MPS doesn't support MinGW OOTB, so I needed to add that, and fix a few compilation warnings and errors. I can share my changes, if you want. The important part is to make sure the smoke test suite runs for you and passes all the tests. Those tests uncovered a subtle error in the code which I needed to fix. > (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') Never saw anything like that, but I didn't use Wine or Docker.