From: Eli Zaretskii <eliz@gnu.org>
To: spwhitton@spwhitton.name, rlb@defaultvalue.org
Cc: emacs-devel@gnu.org
Subject: Re: Possibly defaulting native-compile-target-directory to XDG_CACHE_HOME/...
Date: Sun, 25 Dec 2022 11:22:53 +0200 [thread overview]
Message-ID: <835ydz4z2q.fsf@gnu.org> (raw)
In-Reply-To: <83fsd43rtl.fsf@gnu.org> (message from Eli Zaretskii on Sun, 25 Dec 2022 08:44:54 +0200)
> Date: Sun, 25 Dec 2022 08:44:54 +0200
> From: Eli Zaretskii <eliz@gnu.org>
> Cc: rlb@defaultvalue.org, emacs-devel@gnu.org
>
> > From: Sean Whitton <spwhitton@spwhitton.name>
> > Cc: Rob Browning <rlb@defaultvalue.org>, emacs-devel@gnu.org
> > Date: Sat, 24 Dec 2022 16:03:36 -0700
> >
> > On Sun 18 Dec 2022 at 10:48AM +02, Eli Zaretskii wrote:
> >
> > > Anyway, what happens if you try this with Emacs 29? Emacs 28 is in
> > > the past for us: there will be no more releases from the emacs-28
> > > branch. And on Emacs 29 we made some changes which I think should
> > > prevent these problems.
> >
> > Could you remind me which changes you mean?
>
> I don't have the pointers at the moment, so I can only point to the
> "Native Compilation" section of NEWS and to Git logs. Sorry.
And also the changes that prevent compiling trampolines in async
subprocesses, see commits 1a8015b837 and 5ad5b797f7.
next prev parent reply other threads:[~2022-12-25 9:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-16 6:08 Possibly defaulting native-compile-target-directory to XDG_CACHE_HOME/ Rob Browning
2022-12-17 12:08 ` Eli Zaretskii
2022-12-17 17:42 ` Rob Browning
2022-12-17 18:04 ` Eli Zaretskii
2022-12-17 20:37 ` Rob Browning
2022-12-17 20:59 ` Rob Browning
2022-12-18 8:48 ` Eli Zaretskii
2022-12-24 23:03 ` Sean Whitton
2022-12-25 6:44 ` Eli Zaretskii
2022-12-25 9:22 ` Eli Zaretskii [this message]
2022-12-17 15:58 ` Stefan Monnier
2022-12-17 17:38 ` Rob Browning
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=835ydz4z2q.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=rlb@defaultvalue.org \
--cc=spwhitton@spwhitton.name \
/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.