unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Andrea Corallo <acorallo@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: mark@grosen.org, 73415@debbugs.gnu.org
Subject: bug#73415: 30.0.91; Emacs 30 build fails on Ubuntu 24.04
Date: Wed, 25 Sep 2024 14:34:49 -0400	[thread overview]
Message-ID: <yp1h6a3eg52.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <86v7yjbucj.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 25 Sep 2024 18:56:12 +0300")

Eli Zaretskii <eliz@gnu.org> writes:

>> From: Andrea Corallo <acorallo@gnu.org>
>> Cc: Mark Grosen <mark@grosen.org>,  73415@debbugs.gnu.org
>> Date: Wed, 25 Sep 2024 09:40:54 -0400
>> 
>> Eli Zaretskii <eliz@gnu.org> writes:
>> 
>> > 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.
>
> 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

  Andrea





  reply	other threads:[~2024-09-25 18:34 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 [this message]
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

  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=yp1h6a3eg52.fsf@fencepost.gnu.org \
    --to=acorallo@gnu.org \
    --cc=73415@debbugs.gnu.org \
    --cc=eliz@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).