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: Lisp files that load cl-lib in problematical ways Date: Tue, 24 Oct 2023 16:51:26 +0300 Message-ID: <83jzrcku1t.fsf@gnu.org> References: <83ttqnm4ti.fsf@gnu.org> <83lebyu5yx.fsf@gnu.org> <4684f43123d7dee59461@heytings.org> <835y2xo1a5.fsf@gnu.org> <4684f4312391906f6101@heytings.org> <831qdlo084.fsf@gnu.org> <83msw8n43r.fsf@gnu.org> <87y1fs75mx.fsf@localhost> <837cncmewi.fsf@gnu.org> <87fs209ora.fsf@localhost> <83pm14kwz0.fsf@gnu.org> <87cyx49nt2.fsf@localhost> <83msw8kw2f.fsf@gnu.org> <87a5s89mcy.fsf@localhost> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="19113"; mail-complaints-to="usenet@ciao.gmane.io" Cc: stefankangas@gmail.com, gregory@heytings.org, rms@gnu.org, emacs-devel@gnu.org To: Ihor Radchenko , Andrea Corallo Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Tue Oct 24 15:53:05 2023 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 1qvHqD-0004lx-7F for ged-emacs-devel@m.gmane-mx.org; Tue, 24 Oct 2023 15:53:05 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qvHpJ-0003BD-7F; Tue, 24 Oct 2023 09:52:10 -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 1qvHp7-00039M-4o for emacs-devel@gnu.org; Tue, 24 Oct 2023 09:52:00 -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 1qvHp6-000193-HJ; Tue, 24 Oct 2023 09:51:56 -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=0nKbgN2ne9IvuAmxCyzRHkirSAk2jUlZqh35yPfp0Is=; b=ahSUgo3G4dp1 wzmqe/aCpeWl9TSQDqIOfMTXTwMZe2UEt2jcEERX8FU8I04mUMF5hcuLKIJnLbSXrxZiTCUozT427 +wI/vA6/BC8IUlFVYN5G4NM8XoqfVnasFebJ7kt6Rda0SP8W1W7xvKqUU2+53QAelaT3D8OVVmLbN FUiNxRbV5J99tXsRQdxsGCcLWRU9phncd1JWPakafSANEWMWp/+pXpNhF0vDMoFhL0rZG9HX5SVmK T+9V+wpMM8JDwxXnI6yJZ95NZPfsC4+E8DU4sBbWwd6Y+3gtX28b5xLebJBtKk4rkhlqp3ulnrSJK yt7w195OJobdo11ZxpcEfg==; In-Reply-To: <87a5s89mcy.fsf@localhost> (message from Ihor Radchenko on Tue, 24 Oct 2023 13:33:01 +0000) 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:311793 Archived-At: > From: Ihor Radchenko > Cc: stefankangas@gmail.com, gregory@heytings.org, rms@gnu.org, > emacs-devel@gnu.org > Date: Tue, 24 Oct 2023 13:33:01 +0000 > > ----- /tmp/dump.el ----- > (require 'cl-lib) > (dump-emacs-portable "/tmp/emacs-dumped") > -------- end ----------- > > and got surprised by > > > ./src/emacs -Q --batch -l /tmp/dump.el > Dumping fingerprint: 83db7cb9b32874a4c4a0b923b2ca94f0d08a9a22ff41e18a2f92290276ef7d07 > > Error: error ("Trying to dump non fixed-up eln file") > mapbacktrace(#f(compiled-function (evald func args flags) #)) > debug-early-backtrace() > debug-early(error (error "Trying to dump non fixed-up eln file")) > dump-emacs-portable("/tmp/emacs-dumped") > eval-buffer(# nil "/tmp/dump.el" nil t) > load-with-code-conversion("/tmp/dump.el" "/tmp/dump.el" nil t) > load("/tmp/dump.el" nil t) > command-line-1(("-l" "/tmp/dump.el")) > command-line() > normal-top-level() > Trying to dump non fixed-up eln file > > Is it a bug? Or do I miss something important? I think you are trying to do something that isn't supported. Andrea, am I right? Your original idea was to add stuff to loadup, not to dump an already dumped Emacs, and with AOT *.eln stuff on top of that. Preloaded *.eln files are handled specially by loadup.el during the dumping process, and you tried doing that without observing the protocol of *.eln dumping.