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: Emacs 29.3 released Date: Sun, 24 Mar 2024 21:46:03 +0200 Message-ID: <86ttkvjtvo.fsf@gnu.org> References: <86edbzyavw.fsf@gnu.org> <86y1a7jwmi.fsf@gnu.org> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="28547"; mail-complaints-to="usenet@ciao.gmane.io" Cc: emacs-devel@gnu.org To: Corwin Brust Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sun Mar 24 20:47:19 2024 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 1roToM-0007Co-AA for ged-emacs-devel@m.gmane-mx.org; Sun, 24 Mar 2024 20:47:18 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1roTnF-0007q0-3g; Sun, 24 Mar 2024 15:46:09 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1roTnE-0007pq-2V for emacs-devel@gnu.org; Sun, 24 Mar 2024 15:46:08 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1roTnD-0002Eq-BR; Sun, 24 Mar 2024 15:46:07 -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=wGEcYtm9X5Vio4ggDkcvdy4Z52WY7SRfCt/XftjQiUk=; b=SFR2XUGQmGU9 ynqg6h1syCJhkPB6hbnkOoDMC1ECHUnw/kw6GvbkuRhkxq3Y38gemxiykqSunmp37HzydDasIKNcC 1lYy5GO5MJVH4KIu3xT0AK+R3YXPYmqT5N0lKHzf0AoWmiGAWaO5YQhb761TItkFD/0rGYGzdxvH1 68PU6x4GN3LFhaq6YtpSp45OphkkTiIfPN95nP2U9nFUcQsgWt0Rq9L42aUrJ8zxz5W1T1AenUa7J 2w6LNkiQl+Sb9ZSHxMdQM2csDanp1n7vPAPuhCVBvL3nFfdqpVqip+gM83SQPdhd6DZdhRSqZ9rcy YorWlbmPc63QEl3GGXHqhQ==; In-Reply-To: (message from Corwin Brust on Sun, 24 Mar 2024 14:36:08 -0500) 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-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:317270 Archived-At: > From: Corwin Brust > Date: Sun, 24 Mar 2024 14:36:08 -0500 > Cc: emacs-devel@gnu.org > > > I have no idea. Comparing the configure script for Emacs 29.2 and > > Emacs 29.3 doesn't show any differences, and neither does comparing > > the various Makefile's. > > > > If you build Emacs 29.2 in this manner, do you get all the *.el files > > compiled into *.eln, or do you see the same problem with Emacs 29.2? > > No, Building 29.2 from the release tarball (so, without running > autogen.sh) successfully precompiles all the ELNs as expected. Strange. I don't see this problem. > > One note, though: if you say --with-native-compilation=aot, you don't > > need the NATIVE_FULL_AOT=1 part. Not sure if this is relevant or not. > > > > A good point. I haven't tried removing this to see if anything > changes; 29.2 works properly, so I suspect this is a read herring but > I'll try removing it, nevertheless. > > I do get all full AOT build if I add ./autogen.sh to the start of my > recipe -- which is really weird. I find no differences between the > configure script provided with emacs-29.3 tarball and the one created > by running autogen.sh against the unpacked release tarball sources. I > have no idea why AOT is working in the latter case but not the first. FWIW, I've just built the 29.3 release tarball with the "--with-native-compilation=aot" option (and without NATIVE_FULL_AOT=1), and it builds all the *.eln files just fine. I didn't need to run autogen.sh. > I'm inclined to go ahead and publish using the version where I run > autogen.sh -- let me know if we prefer that we track this issue down > first, instead. I don't think autogen.sh can do any harm, but I cannot be sure without understanding why you see this weird problem.