From: "H. Dieter Wilhelm" <dieter@duenenhof-wilhelm.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: luangruo@yahoo.com, Corwin Brust <corwin@bru.st>,
stefan@marxist.se, drew.adams@oracle.com, emacs-devel@gnu.org
Subject: Re: [External] : Emacs pretest 28.0.91 is out
Date: Wed, 12 Jan 2022 22:15:57 +0100 [thread overview]
Message-ID: <86mtk0u036.fsf@duenenhof-wilhelm.de> (raw)
In-Reply-To: <83wnj55d5d.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 12 Jan 2022 14:53:02 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Corwin Brust <corwin@bru.st>
>> Date: Tue, 11 Jan 2022 22:07:41 -0600
>> Cc: Po Lu <luangruo@yahoo.com>, Stefan Kangas <stefan@marxist.se>,
>> Drew Adams <drew.adams@oracle.com>,
>> "emacs-devel@gnu.org" <emacs-devel@gnu.org>
>>
>> Please note that this build does **not** enable native-compilation nor
>> does it include gccjit (in deps). I'm working on the assumption that
>> the Phillip's build scripts should be enhanced so we can build (and
>> distribute) windows binaries both with and without native compilation
>> enabled.
> I'm not sure this is correct/justified. Wouldn't it be better to have
> just one build that could support both variants? It is supposed to
> work that way, but I don't think anyone tested this in practice. It
> would be good to see if that indeed works as intended, and if not,
> report the issues which prevent that.
I don't quite understand, does this mean that ALL .elc files are getting
.eln companions?
Or can this work as under Gnu-Linux with JIT compilation?
> Specifically, I suggest to build Emacs _with_ native-compilation
> support, then try using that on a system that has neither libgccjit
> nor gcc/Binutils installed.
OK, I can check this in the office.
Dieter
--
Best wishes
H. Dieter Wilhelm
Zwingenberg, Germany
next prev parent reply other threads:[~2022-01-12 21:15 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-10 22:39 Emacs pretest 28.0.91 is out Stefan Kangas
2022-01-11 2:16 ` [External] : " Drew Adams
2022-01-11 2:28 ` Po Lu
2022-01-11 3:28 ` Corwin Brust
2022-01-11 21:43 ` H. Dieter Wilhelm
2022-01-12 4:07 ` Corwin Brust
2022-01-12 12:53 ` Eli Zaretskii
2022-01-12 21:15 ` H. Dieter Wilhelm [this message]
2022-01-13 6:30 ` Eli Zaretskii
2022-01-13 7:15 ` H. Dieter Wilhelm
2022-01-13 9:08 ` Eli Zaretskii
2022-01-13 21:41 ` H. Dieter Wilhelm
2022-01-12 20:55 ` H. Dieter Wilhelm
-- strict thread matches above, loose matches on Subject: below --
2022-01-11 2:45 Tom Davey
2022-01-17 19:47 ` chad
2022-01-17 22:15 ` Corwin Brust
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=86mtk0u036.fsf@duenenhof-wilhelm.de \
--to=dieter@duenenhof-wilhelm.de \
--cc=corwin@bru.st \
--cc=drew.adams@oracle.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=luangruo@yahoo.com \
--cc=stefan@marxist.se \
/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).