From: Eli Zaretskii <eliz@gnu.org>
To: Ken Brown <kbrown@cornell.edu>
Cc: tom@tromey.com, emacs-devel@gnu.org
Subject: Re: 32-bit MinGW build with JIT
Date: Tue, 28 Aug 2018 19:58:50 +0300 [thread overview]
Message-ID: <83zhx62zsl.fsf@gnu.org> (raw)
In-Reply-To: <8e78c287-f22d-19f2-889e-312d130cda5b@cornell.edu> (message from Ken Brown on Tue, 28 Aug 2018 09:12:40 -0400)
> Cc: tom@tromey.com, emacs-devel@gnu.org
> From: Ken Brown <kbrown@cornell.edu>
> Date: Tue, 28 Aug 2018 09:12:40 -0400
>
> On 8/28/2018 1:25 AM, Eli Zaretskii wrote:
> >> I can't test 64-bit Cygwin because libjit doesn't build there. (My
> >> understanding from the libjit TODO file and the libjit mailing list
> >> archives is that it doesn't build on 64-bit MS-Windows either.)
> >
> > Can you please point me to the relevant messages in the mailing-list
> > archives?
>
> https://lists.gnu.org/archive/html/dotgnu-libjit/2009-10/msg00012.html
> https://lists.gnu.org/archive/html/dotgnu-libjit/2009-10/msg00011.html
> https://lists.gnu.org/archive/html/dotgnu-libjit/2012-08/msg00003.html
Thanks. One of these:
https://lists.gnu.org/archive/html/dotgnu-libjit/2012-08/msg00000.html
points to the bug tracker:
https://savannah.gnu.org/patch/?group=dotgnu-pnet
where one can find relevant patches. Perhaps they can be rebased on
the current libjit trunk and re-submitted to the current maintainer?
next prev parent reply other threads:[~2018-08-28 16:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-16 14:09 32-bit MinGW build with JIT Eli Zaretskii
2018-08-16 17:35 ` Eli Zaretskii
2018-08-18 9:14 ` Eli Zaretskii
2018-08-19 15:24 ` Tom Tromey
2018-08-19 15:37 ` Eli Zaretskii
2018-08-19 15:50 ` Tom Tromey
2018-08-19 16:15 ` Eli Zaretskii
2018-08-27 19:52 ` Ken Brown
2018-08-28 5:25 ` Eli Zaretskii
2018-08-28 13:12 ` Ken Brown
2018-08-28 16:58 ` Eli Zaretskii [this message]
2018-08-19 17:11 ` Paul Eggert
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83zhx62zsl.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=kbrown@cornell.edu \
--cc=tom@tromey.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.