GNU bug report logs - #73415
30.0.91; Emacs 30 build fails on Ubuntu 24.04

Previous Next

Full log

View this message in rfc822 format

From: Andrea Corallo <acorallo <at> gnu.org>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: Mark Grosen <mark <at> grosen.org>, 73415 <at> debbugs.gnu.org
Subject: bug#73415: 30.0.91; Emacs 30 build fails on Ubuntu 24.04
Date: Wed, 25 Sep 2024 09:40:54 -0400

Eli Zaretskii <eliz <at> gnu.org> writes:

>> From: Mark Grosen <mark <at> grosen.org>
>> Date: Tue, 24 Sep 2024 15:53:23 -0700
>> Cc: Andrea Corallo <acorallo <at> gnu.org>, 73415 <at> debbugs.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.
>
> Thanks, in that case I think this is a known issue, and we decided not
> to fix it on the emacs-30 release branch because building the pretest
> tarball (which doesn't require to go via bootstrap) works with the
> original pure-size.
>
> Andrea, what did we decide regarding the long-term solution for this?
> Did we mean to somehow solve the issue with dynamic doc strings?

AFAIR we dedided that for master we®'ll extend the code to support
native compiled functions with lazy docs and we'll emit them even while
native compiling.

  Andrea

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.