From: Andrea Corallo <akrl@sdf.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: htl10@users.sourceforge.net, 60208@debbugs.gnu.org
Subject: bug#60208: 28.1; Resource exhaustion with emacs 28's native compilation; need "-Q" for trampoline
Date: Wed, 21 Dec 2022 22:30:47 +0000 [thread overview]
Message-ID: <xjfbknwbd9k.fsf@ma.sdf.org> (raw)
In-Reply-To: <835ye4c4ar.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 21 Dec 2022 14:46:52 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Andrea Corallo <akrl@sdf.org>
>> Cc: Hin-Tak Leung <htl10@users.sourceforge.net>, 60208@debbugs.gnu.org
>> Date: Wed, 21 Dec 2022 09:25:38 +0000
>>
>> Eli Zaretskii <eliz@gnu.org> writes:
>>
>> > Andrea, do you see any problems with adding -Q to the async
>> > compilation command line, to avoid processing site-init files?
>>
>> Hi Eli,
>>
>> no I don't.
>>
>> > Did we
>> > have any reasons not to do that from the beginning, or was it just an
>> > omission?
>>
>>
>> Not that I remember. Actually I think we should do this for all
>> compilations (sync and async).
>>
>> If okay I can push the fix on emacs-29.
>
> Yes, please.
Done with e59216d3be8.
Best Regards
Andrea
next prev parent reply other threads:[~2022-12-21 22:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <974722961.3073608.1671487166201.ref@mail.yahoo.com>
2022-12-19 21:59 ` bug#60208: 28.1; Resource exhaustion with emacs 28's native compilation; need "-Q" for trampoline Hin-Tak Leung
2022-12-20 3:32 ` Eli Zaretskii
2022-12-20 9:30 ` Hin-Tak Leung
2022-12-20 14:16 ` Eli Zaretskii
2022-12-21 9:25 ` Andrea Corallo
2022-12-21 12:46 ` Eli Zaretskii
2022-12-21 22:30 ` Andrea Corallo [this message]
2022-12-22 0:33 ` Hin-Tak Leung
2022-12-22 7:21 ` Eli Zaretskii
2022-12-22 13:46 ` Hin-Tak Leung
2022-12-22 15:22 ` Eli Zaretskii
2022-12-22 16:32 ` Hin-Tak Leung
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=xjfbknwbd9k.fsf@ma.sdf.org \
--to=akrl@sdf.org \
--cc=60208@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=htl10@users.sourceforge.net \
/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).