From: Mark Grosen <mark@grosen.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Andrea Corallo <acorallo@gnu.org>, 73415@debbugs.gnu.org
Subject: bug#73415: 30.0.91; Emacs 30 build fails on Ubuntu 24.04
Date: Tue, 24 Sep 2024 15:53:23 -0700 [thread overview]
Message-ID: <CAL8ugEe_o07wida7qHN05eUEaVZ1vsvE1D2Q_kpBBE35RxTjow@mail.gmail.com> (raw)
In-Reply-To: <86frps2rwn.fsf@gnu.org>
> Thanks, but 400KB of pure space is too much to just increase the size
> without understanding why this is needed. Did you really need 400KB,
> or would a smaller number do? If the latter, what is the smallest
> addition that avoids the overflow in your case?
290000 is the smallest that works, with or without --with-pgtk
> . what was the absolute file name of the top-level directory where
> you unpacked the pretest tarball (assuming that this happens with
> building the pretest, not a Git checkout)?
This is built from git checkout of emacs-30 or emacs-30.0.91 in
/home/mark/Stuff/emacs
I did some more experiments and found that my original build commands
fail but the first suggested one
in INSTALL.repo works.
> . what were the commands you used to build?
Fails:
git clean -fdx
make bootstrap -j12
./configure --with-webp
make -j12
Works:
git clean -fdx
make -j12 configure="--with-webp"
However, the first way does work if there are no 'configure' options.
Any option to configure causes a failure.
> . does the problem go away if you build a "normal" Emacs, i.e. not a
PGTK build?
no, only if there are no options
Thanks for your help.
Mark
Mark
On Sat, Sep 21, 2024 at 10:12 PM Eli Zaretskii <eliz@gnu.org> wrote:
>
> > From: Mark Grosen <mark@grosen.org>
> > Date: Sat, 21 Sep 2024 14:52:45 -0700
> >
> > Building Emacs 30.0.91 and later on Ubuntu 24.04 fails with a
> > "Pure Lisp overflowed" error. To workaround this issue, I used
> > the following build steps:
> >
> > make bootstrap MYCPPFLAGS='-DSYSTEM_PURESIZE_EXTRA=200000'
> > ./configure
> > make MYCPPFLAGS='-DSYSTEM_PURESIZE_EXTRA=400000'
> >
> > Note that the 'bootstrap' build required a smaller extra size
> > on my system.
> >
> > With these changes, the build succeeded and Emacs appears to
> > function normally. This was required on the current emacs-30
> > branch.
>
> Thanks, but 400KB of pure space is too much to just increase the size
> without understanding why this is needed. Did you really need 400KB,
> or would a smaller number do? If the latter, what is the smallest
> addition that avoids the overflow in your case?
>
> Also, please answer the following questions:
>
> . what was the absolute file name of the top-level directory where
> you unpacked the pretest tarball (assuming that this happens with
> building the pretest, not a Git checkout)?
> . what were the commands you used to build?
> . does the problem go away if you build a "normal" Emacs, i.e. not a
> PGTK build?
next prev parent reply other threads:[~2024-09-24 22:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-21 21:52 bug#73415: 30.0.91; Emacs 30 build fails on Ubuntu 24.04 Mark Grosen
2024-09-22 5:12 ` Eli Zaretskii
2024-09-24 22:53 ` Mark Grosen [this message]
2024-09-25 11:51 ` Eli Zaretskii
2024-09-25 13:40 ` Andrea Corallo
2024-09-25 15:56 ` Eli Zaretskii
2024-09-25 18:34 ` Andrea Corallo
2024-09-26 3:29 ` Mark Grosen
2024-09-26 6:32 ` Eli Zaretskii
2024-09-26 21:51 ` Mark Grosen
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=CAL8ugEe_o07wida7qHN05eUEaVZ1vsvE1D2Q_kpBBE35RxTjow@mail.gmail.com \
--to=mark@grosen.org \
--cc=73415@debbugs.gnu.org \
--cc=acorallo@gnu.org \
--cc=eliz@gnu.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 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.