GNU bug report logs - #78285
31.0.50; load-prefer-newer causes recursive load on Windows

Previous Next

Full log

Message #17 received at 78285 <at> debbugs.gnu.org (full text, mbox):

From: Gary Oberbrunner <garyo <at> oberbrunner.com>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: 78285 <at> debbugs.gnu.org
Subject: Re: bug#78285: 31.0.50;
 load-prefer-newer causes recursive load on Windows
Date: Wed, 7 May 2025 09:15:51 -0400

[Message part 1 (text/plain, inline)]

On Wed, May 7, 2025 at 8:50 AM Eli Zaretskii <eliz <at> gnu.org> wrote:

> > From: Gary Oberbrunner <garyo <at> oberbrunner.com>
> > Date: Wed, 7 May 2025 08:20:36 -0400
> > Cc: 78285 <at> debbugs.gnu.org
> >
> > > As can be seen from the above, your configuration loads
> > > elpaca-bootstrap.el, whose contents you haven''t shown.  Then Emacs
> > > loads loaddefs-gen.elc, which wants to load radix-tree.elc, but
> > > instead loads radix-tree.el.gz for some reason.
> >
> > Actually I gave a minimal one-line repro case without elpaca. Just
> create init.el with this:
> >
> > >   (setq load-prefer-newer t)
> >
> > and then check the *Messages* buffer.
>
> Granted, I already tried that, and it didn't happen for me.
>
> If the traces you show in your original report are not relevant for
> the reproduction recipe, please show the same traces for the latter.
>
> Did you make sure that all the *.elc files in the installation tree
> are newer that the corresponding *.el.gz files?
>

Ah, OK, good info. If it doesn't happen for you (I presume you're compiling
the latest master branch on Windows) then it may be specific to the
package.

Looking into it further, the .el.gz is newer than the .elc:

-rw-r--r-- 1 garyo garyo  7477 May  6 16:45 jka-compr.el.gz
-rw-r--r-- 1 garyo garyo 12168 Sep  3  2024 jka-compr.elc

so I think I understand the problem now. load-prefer-newer tells emacs to
use jka-compr.el.gz rather than jka-compr.elc, and to use that, it will
need to decompress it, which means it'll need to load the decompressor,
which comes from jka-compr. And boom.
Given the file dates above it's pretty clear the build I'm using is the
cause of the problem. So you can close this bug report and I'll follow up
there.

-- 
Gary

[Message part 2 (text/html, inline)]

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.