unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Stefan Kangas <stefan@marxist.se>
Cc: 57001@debbugs.gnu.org
Subject: bug#57001: make: No such file or directory after `rm loaddefs-gen.elc`
Date: Fri, 05 Aug 2022 14:05:44 +0200	[thread overview]
Message-ID: <87wnbmao9z.fsf@gnus.org> (raw)
In-Reply-To: <CADwFkmkyoTV7debP0YoysYiYmSQJAESGHj2UvBmeqvY+5JP4NQ@mail.gmail.com> (Stefan Kangas's message of "Fri, 5 Aug 2022 12:06:09 +0200")

Stefan Kangas <stefan@marxist.se> writes:

> I guess it's fixed by this, but it'd be better to byte-compile it:

Adding loaddefs-gen.elc as a dependency fixes this, so I've now done
that instead.





      reply	other threads:[~2022-08-05 12:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-05 10:06 bug#57001: make: No such file or directory after `rm loaddefs-gen.elc` Stefan Kangas
2022-08-05 12:05 ` Lars Ingebrigtsen [this message]

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=87wnbmao9z.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=57001@debbugs.gnu.org \
    --cc=stefan@marxist.se \
    /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).