From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: wavexx@thregr.org, emacs-devel@gnu.org
Subject: Re: "make autoloads" signals an error
Date: Thu, 02 Jun 2022 13:20:03 +0200 [thread overview]
Message-ID: <875yljz50c.fsf@gnus.org> (raw)
In-Reply-To: <835yljfi6k.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 02 Jun 2022 13:55:47 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
> I think you didn't clean your tree?
Wasn't part of the recipe. :-/
Anyway, I'm testing the same in Emacs 28 just to see how it's supposed
to work -- and is an out-of-build tree supposed to write the .elc files
in the tree? I.e., build/lisp/ remains empty after finishing the build?
(Except for a Makefile.)
The problem seems to be that loaddefs-gen tries to put the generated
files into build/lisp/, and then Emacs can't find them. So I'll adjust
that to put them into lisp-directory instead. But isn't this a bug?
That is, an out-of-tree build shouldn't alter the source tree at all I'd
have thought?
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2022-06-02 11:20 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-01 12:10 "make autoloads" signals an error Eli Zaretskii
2022-06-01 12:26 ` Lars Ingebrigtsen
2022-06-01 12:44 ` Eli Zaretskii
2022-06-01 12:46 ` Lars Ingebrigtsen
2022-06-01 12:50 ` Lars Ingebrigtsen
2022-06-01 12:56 ` Lars Ingebrigtsen
2022-06-01 17:51 ` Ergus
2022-06-01 18:21 ` Ergus
2022-06-02 9:16 ` Lars Ingebrigtsen
2022-06-02 10:01 ` Yuri D'Elia
2022-06-02 10:08 ` Lars Ingebrigtsen
2022-06-02 10:48 ` Lars Ingebrigtsen
2022-06-02 10:55 ` Eli Zaretskii
2022-06-02 11:20 ` Lars Ingebrigtsen [this message]
2022-06-02 11:53 ` Eli Zaretskii
2022-06-02 11:59 ` Lars Ingebrigtsen
2022-06-02 12:05 ` Eli Zaretskii
2022-06-03 3:13 ` Lars Ingebrigtsen
2022-06-03 5:57 ` Eli Zaretskii
2022-06-02 12:54 ` Andreas Schwab
2022-06-02 11:55 ` Lars Ingebrigtsen
2022-06-01 13:11 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=875yljz50c.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=wavexx@thregr.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.