From: Stefan Kangas <stefankangas@gmail.com>
To: Ken Brown <kbrown@cornell.edu>, 74805@debbugs.gnu.org
Subject: bug#74805: 30.0.92; Trying to build scratch/igc on Cygwin
Date: Thu, 12 Dec 2024 03:05:58 -0800 [thread overview]
Message-ID: <CADwFkmm239=FLBPnFzJgsueAmSXM04VpyFF8s8GMGnj1Ee7OBQ@mail.gmail.com> (raw)
In-Reply-To: <0e6c2f69-9c33-48d7-87ab-2b13de857f71@cornell.edu>
Ken Brown <kbrown@cornell.edu> writes:
> I've made a first attempt to port mps to Cygwin. If anyone else is
> interested in seeing this or helping, you can find my work at
>
> https://github.com/kbrow1i/mps-cygwin
>
> This is a fork of the mps git repo with two commits on top.
>
> 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. Before I do that, however, I'd
> like to check and see if test failures on scratch/igc are to be
> expected. Are people testing other platforms seeing this too?
Do we expect upstream to be amenable to eventually taking these patches?
I see that they officially only support "Windows Vista or later, on
IA-32 and x86-64, using Microsoft Visual C/C++".
next prev parent reply other threads:[~2024-12-12 11:05 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
2024-12-12 11:05 ` Stefan Kangas [this message]
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='CADwFkmm239=FLBPnFzJgsueAmSXM04VpyFF8s8GMGnj1Ee7OBQ@mail.gmail.com' \
--to=stefankangas@gmail.com \
--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).