From: Eli Zaretskii <eliz@gnu.org>
To: Mark Grosen <mark@grosen.org>
Cc: acorallo@gnu.org, 73415-done@debbugs.gnu.org
Subject: bug#73415: 30.0.91; Emacs 30 build fails on Ubuntu 24.04
Date: Thu, 26 Sep 2024 09:32:59 +0300 [thread overview]
Message-ID: <86cykqc4bo.fsf@gnu.org> (raw)
In-Reply-To: <CAL8ugEdB2k1etQs14-bGo5N_wW+_KH8C5VGP8R=Pmq69=UucHQ@mail.gmail.com> (message from Mark Grosen on Wed, 25 Sep 2024 20:29:06 -0700)
> From: Mark Grosen <mark@grosen.org>
> Date: Wed, 25 Sep 2024 20:29:06 -0700
> Cc: Eli Zaretskii <eliz@gnu.org>, 73415@debbugs.gnu.org
>
> >> OK, so the decision is indeed not to try solving this on emacs-30. I
> >> wasn't sure.
>
> > That was my understanding at least, as we could not find a simple
> > fix/workaround with limited impact we could install in emacs-30. Of
> > course if you have a different suggestion please voice it.
>
> Thanks for the feedback. I know how to build more efficiently now, so my
> issue is closed.
Thanks, closing the bug.
> I will leave it to you if this warrants a line in the changelog or
> INSTALL.repo.
We might do that, but I'd first need to understand better your reasons
for using "make bootstrap" when building from a tarball. The Emacs
release and pretest tarballs are intentionally prepared to make the
build as fast as possible, which is why all the platform-independent
files produced by bootstrapping (notably, the configure script, all
the *.elc files, and all the Info manuals) are included in the
tarball. So why did you decide to bootstrap?
next prev parent reply other threads:[~2024-09-26 6:32 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
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 [this message]
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
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=86cykqc4bo.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=73415-done@debbugs.gnu.org \
--cc=acorallo@gnu.org \
--cc=mark@grosen.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).