From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: "make autoloads" signals an error Date: Thu, 02 Jun 2022 14:53:23 +0300 Message-ID: <8335gnffik.fsf@gnu.org> References: <83ee08h9et.fsf@gnu.org> <87sfoozi14.fsf@gnus.org> <83a6awh7ts.fsf@gnu.org> <87ee085z6o.fsf@gnus.org> <87a6aw5yz2.fsf@gnus.org> <875ylk5yqk.fsf@gnus.org> <20220601175157.4u4a4liqfa3ayg5y@Ergus> <20220601182104.q7pwzhq2qdpof5wm@Ergus> <87tu931l4c.fsf@gnus.org> <87v8tjjsdy.fsf@wavexx.thregr.org> <87h753z8bw.fsf@gnus.org> <835yljfi6k.fsf@gnu.org> <875yljz50c.fsf@gnus.org> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="6213"; mail-complaints-to="usenet@ciao.gmane.io" Cc: wavexx@thregr.org, emacs-devel@gnu.org To: Lars Ingebrigtsen Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Thu Jun 02 13:57:56 2022 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nwjSd-0001Pk-NS for ged-emacs-devel@m.gmane-mx.org; Thu, 02 Jun 2022 13:57:55 +0200 Original-Received: from localhost ([::1]:56226 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1nwjSc-0007rT-GZ for ged-emacs-devel@m.gmane-mx.org; Thu, 02 Jun 2022 07:57:54 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:45782) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nwjO8-0004Ve-G7 for emacs-devel@gnu.org; Thu, 02 Jun 2022 07:53:18 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:55278) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nwjO7-00008T-OZ; Thu, 02 Jun 2022 07:53:15 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=03u9h7HRPcwPOYBt4QCWjBTdmJ7g56fxoA7CaOkDQ8U=; b=dHWz0CHvAvY9 fFB78S2rzpRNRPnXwMgFBC+5z/aNwpupdefEgD/lXp9updBO0Fdx3slKLeLebnSxU7ufhqJye4oXE Qdu7B26UZDVc0Agz22OoTGsiSxHe05LegDSIAZUCZGx748IyPgTeh9Y8JvAz6z5WYaVwOtUdBGpo9 IZwSJ+V//KE2eMM6fLD7DWz3ufYAFwzvItX1AQdGPf49VBaWQ48tSu4LSWS+42PyXmwxb3cugzjGw 1cAH1AZHyLl5PVyz6dZ+/x+wYpiVm08rP5laPwMYrJ2zwa0Q5xYstV0hORkPOrysLAxKH8Iz0+9Ph KBha5SCmE0EiM1PWCfQE+A==; Original-Received: from [87.69.77.57] (port=2793 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nwjO6-0001tx-Lu; Thu, 02 Jun 2022 07:53:15 -0400 In-Reply-To: <875yljz50c.fsf@gnus.org> (message from Lars Ingebrigtsen on Thu, 02 Jun 2022 13:20:03 +0200) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:290553 Archived-At: > From: Lars Ingebrigtsen > Cc: wavexx@thregr.org, emacs-devel@gnu.org > Date: Thu, 02 Jun 2022 13:20:03 +0200 > > 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? Ideally, it shouldn't modify the source tree, but: . if you build a release tarball, the *.elc files are already there in the source tree; . the *.elc files are platform-independent, so there shouldn't be a need to regenerate them for every build; . if you put the *.elc files in the build tree, you need to adjust load-path, since some of the files (the ones we don't byte-compile) will be in the source tree, and others in the build tree So the reason(s) to make changes here are weak enough for us to punt ;-)