From: Eli Zaretskii <eliz@gnu.org>
To: Eric Marsden <eric.marsden@risk-engineering.org>
Cc: 74744@debbugs.gnu.org
Subject: bug#74744: Build failure: SEGV in temacs (with "Pure Lisp storage overflowed")
Date: Mon, 09 Dec 2024 18:27:47 +0200 [thread overview]
Message-ID: <86h67cddoc.fsf@gnu.org> (raw)
In-Reply-To: <43753bef-994f-4a90-9867-ab9f9fc112e0@risk-engineering.org> (message from Eric Marsden on Mon, 9 Dec 2024 16:23:56 +0100)
> Date: Mon, 9 Dec 2024 16:23:56 +0100
> Cc: 74744@debbugs.gnu.org
> From: Eric Marsden <eric.marsden@risk-engineering.org>
>
> On 09/12/2024 16:03, Eli Zaretskii wrote:
> > And if you enlarge PURESIZE, does the segfault go away?
> >
> > Also, please try without --enable-link-time-optimization and without
> > the -flto=8 -ffat-lto-objects compiler options.
>
> Thanks, inspired by Pip's suggestion I used
>
> ./configure --with-options
> make FAST=true bootstrap
>
> which worked, so I have not investigated further. I was not anticipating
> that the default make recipe might fail due to pre-existing object files.
Yes, pure space can overflow if loadup loads byte-compiled files.
This is a known subtlety that sometimes pops up.
prev parent reply other threads:[~2024-12-09 16:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-09 10:48 bug#74744: Build failure: SEGV in temacs (with "Pure Lisp storage overflowed") Eric Marsden
2024-12-09 12:41 ` Pip Cet via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-09 15:03 ` Eli Zaretskii
[not found] ` <43753bef-994f-4a90-9867-ab9f9fc112e0@risk-engineering.org>
2024-12-09 16:27 ` Eli Zaretskii [this message]
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=86h67cddoc.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=74744@debbugs.gnu.org \
--cc=eric.marsden@risk-engineering.org \
/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).