From: Yuri D'Elia <wavexx@thregr.org>
To: emacs-devel@gnu.org
Subject: Re: "make autoloads" signals an error
Date: Thu, 02 Jun 2022 12:01:45 +0200 [thread overview]
Message-ID: <87v8tjjsdy.fsf@wavexx.thregr.org> (raw)
In-Reply-To: 87tu931l4c.fsf@gnus.org
On Thu, Jun 02 2022, Lars Ingebrigtsen wrote:
> Ergus <spacibba@aol.com> writes:
>
>> The problem seems to be when inside the source:
>>
>> mkdir build
>> cd build
>> ../configure ...
>>
>> When building in the path with ./configure or setting the configure with
>> the absolute path there is no problem.
>
> Sorry, I don't follow. What's the recipe to reproduce the problem?
I'm also experiencing this on a fresh checkout.
This happens when building emacs off-tree (which didn't seem to work to
well in the past.. but I consider good practice anyway..)
The instructions are clear: make a subdirectory inside the source tree,
then "configure" and make inside it exactly as he described. From a
checked-out tree:
mkdir build
cd build
../configure
make
next prev parent reply other threads:[~2022-06-02 10:01 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 [this message]
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
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
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=87v8tjjsdy.fsf@wavexx.thregr.org \
--to=wavexx@thregr.org \
--cc=emacs-devel@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).