From: Eli Zaretskii <eliz@gnu.org>
To: Ken Brown <kbrown@cornell.edu>
Cc: 74805@debbugs.gnu.org
Subject: bug#74805: 30.0.92; Trying to build scratch/igc on Cygwin
Date: Thu, 12 Dec 2024 21:25:47 +0200 [thread overview]
Message-ID: <861pyczosk.fsf@gnu.org> (raw)
In-Reply-To: <baca5037-fac8-47e9-b582-9b82d17780a7@cornell.edu> (message from Ken Brown on Thu, 12 Dec 2024 13:12:46 -0500)
> Date: Thu, 12 Dec 2024 13:12:46 -0500
> Cc: 74805@debbugs.gnu.org
> From: Ken Brown <kbrown@cornell.edu>
>
> >> https://github.com/kbrow1i/mps-cygwin
> >>
> >> This is a fork of the mps git repo with two commits on top.
> >
> > Thanks, good news! Could you please post the patches here, so that
> > they are recorded in our bug tracker?
>
> Unfortunately, the approach I tried, which was suggested by one of the
> MPS developers, fails badly. I already mentioned the test failures, but
> now I've tried to run Emacs interactively, and I can't even get a
> directory listing. For the record, I'm attaching the patches I've
> accumulated so far, but I'll have to try a completely different
> approach. This will probably take me a while.
> >
> >> With the current attempt, I can build the scratch/igc branch, but there
> >> are many test failures. For example, when I run the process-tests, I
> >> get 19 failures and 8 skipped tests. But on the master branch I get no
> >> failures and only 3 skipped.
> >>
> >> This probably means that my current attempt to port mps is no good, and
> >> I have to go back to the drawing board.
> >
> > Did you run the MPS test suite, and if you did, were there any
> > failures? My suggestion is to make sure the MPS test suite passes
> > cleanly, including in several consecutive runs (when I ported MPS to
> > 32-bit MinGW, I had intermittent failures which only happened once in
> > several runs, until I fixed that).
>
> There are lots of test failures. Back to the drawing board.
OK, thanks.
FTR, I built the official released version of MPS, not their latest
code in the repository. So maybe try that as well at some point,
perhaps the development version has new bugs.
What I did was to take the MSVC makefiles they provide and produce
equivalent MinGW makefiles (for GNU Make) instead, using the same
source files. The rest was just to resolve any compilation warnings
or errors. HTH.
next prev parent reply other threads:[~2024-12-12 19:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-11 22:50 bug#74805: 30.0.92; Trying to build scratch/igc on Cygwin Ken Brown
2024-12-11 23:47 ` Pip Cet via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-12 18:14 ` Ken Brown
2024-12-11 23:57 ` Andrea Corallo
2024-12-12 6:09 ` Eli Zaretskii
2024-12-12 18:12 ` Ken Brown
2024-12-12 19:25 ` Eli Zaretskii [this message]
2024-12-12 11:05 ` Stefan Kangas
2024-12-12 11:30 ` Eli Zaretskii
2024-12-12 12:06 ` Gerd Möllmann
2024-12-12 14:38 ` Eli Zaretskii
2024-12-12 15:01 ` Gerd Möllmann
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=861pyczosk.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=74805@debbugs.gnu.org \
--cc=kbrown@cornell.edu \
/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).