From: Ken Brown <kbrown@cornell.edu>
To: cygwin-apps@cygwin.com
Subject: Re: libgccjit-0
Date: Sun, 11 Apr 2021 16:29:32 -0400 [thread overview]
Message-ID: <1c31d670-2f14-1c20-18d7-dc8a93d74846@cornell.edu> (raw)
In-Reply-To: <878s5oy53y.fsf@Rainer.invalid>
On 4/11/2021 3:48 PM, Achim Gratz wrote:
> Ken Brown via Cygwin-apps writes:
>> On 4/11/2021 11:49 AM, Achim Gratz wrote:
>>> Both architectures? For whatever reasons the gcc testsuite on x86
>>> always bombed out on these, so I have no idea if it works there.
>>
>> Yes, it works on x86 too.
>
> Great. So I'll have to update the MingW64 toolchains to 10.3 as well
> (these will not get libgccjit since I'd have to pull in the patches from
> MSys and I don't think there's a consumer for it anyway) and think about
> the packaging again. Not sure when I'll get around to wrap things up.
Sorry, I spoke too soon. It's not even working right on x86_64. In my first
build, the ordinary byte-compiled files (.elc) were already present, and that
somehow prevented the native-compiled files (.eln) from being built. I just
tried 'make bootstrap' and the build won't complete because of fork errors like
this (on x86_64):
0 [main] emacs 5400 child_info_fork::abort: address space needed by
'jit-lock-05ec1a9b-73eb7028.eln' (0x400000) is already occupied
In an earlier attempt it was a different .eln file that was involved, but the
address was the same (0x400000).
I have no idea what's going on.
Ken
next prev parent reply other threads:[~2021-04-11 20:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-10 16:23 libgccjit-0 Achim Gratz
2021-04-11 15:18 ` libgccjit-0 Ken Brown
2021-04-11 15:49 ` libgccjit-0 Achim Gratz
2021-04-11 18:53 ` libgccjit-0 Ken Brown
2021-04-11 19:48 ` libgccjit-0 Achim Gratz
2021-04-11 20:29 ` Ken Brown [this message]
2021-04-12 5:55 ` libgccjit-0 ASSI
2021-04-12 12:18 ` libgccjit-0 Ken Brown
2021-04-12 17:58 ` libgccjit-0 Ken Brown
2021-04-12 18:27 ` libgccjit-0 Achim Gratz
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=1c31d670-2f14-1c20-18d7-dc8a93d74846@cornell.edu \
--to=kbrown@cornell.edu \
--cc=cygwin-apps@cygwin.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.
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).