unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Kun Liu <kun.liu@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 55277@debbugs.gnu.org
Subject: bug#55277: 29.0.50; Commit 8fce81897d no longer generates eln files
Date: Thu, 5 May 2022 12:06:44 -0700	[thread overview]
Message-ID: <CA+Nei8PJnZE7OJqTgdmiV4BHWw1iAG3sGvgDboZ_SpedYNrfvQ@mail.gmail.com> (raw)
In-Reply-To: <83y1zf25m7.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 1024 bytes --]

On Thu, May 5, 2022 at 11:32 AM Eli Zaretskii <eliz@gnu.org> wrote:

> > From: Kun Liu <kun.liu@gmail.com>
> > Date: Thu, 5 May 2022 10:45:50 -0700
> >
> > I did a completely fresh install.
>
> What do you mean by that?  Do you mean that you have built Emacs anew
> after updating from the upstream Git repository, and then installed
> the new Emacs you've built?
>
> Yes I pulled from the master and did a new build and install.


> > I noticed under
> > ~/.emacs.d/eln-cache/29.0.50-a2ce0d0a there are only two files
> >
> >
> subr--trampoline-61626f72742d7265637572736976652d65646974_abort_recursive_edit_0.eln
> > subr--trampoline-746f702d6c6576656c_top_level_0.eln
>
> This is expected, I think.  Assuming you indeed built a new version of
> Emacs, the *.eln files produced during the build are not installed
> under ~/.emacs.d/eln-cache/.
>
> Is this a new behavior? Could you please tell me where *.eln files are at
now?


> So I don't necessarily see any sign of a problem in your report.  Did
> I miss something?
>

[-- Attachment #2: Type: text/html, Size: 1789 bytes --]

  reply	other threads:[~2022-05-05 19:06 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-05 17:45 bug#55277: 29.0.50; Commit 8fce81897d no longer generates eln files Kun Liu
2022-05-05 18:31 ` Eli Zaretskii
2022-05-05 19:06   ` Kun Liu [this message]
2022-05-05 19:26     ` Eli Zaretskii
2022-05-05 20:32       ` Kun Liu
2022-05-06  7:04         ` Eli Zaretskii
2022-05-06 15:10           ` Kun Liu
2022-05-06 15:58             ` Eli Zaretskii

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=CA+Nei8PJnZE7OJqTgdmiV4BHWw1iAG3sGvgDboZ_SpedYNrfvQ@mail.gmail.com \
    --to=kun.liu@gmail.com \
    --cc=55277@debbugs.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 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).