From: Eli Zaretskii <eliz@gnu.org>
To: Lynn Winebarger <owinebar@gmail.com>
Cc: michael.albinus@gmx.de, emacs-devel@gnu.org
Subject: Re: Loading tramp for dump goes into infinite regress
Date: Sun, 24 Jul 2022 19:23:07 +0300 [thread overview]
Message-ID: <83bktefpjo.fsf@gnu.org> (raw)
In-Reply-To: <CAM=F=bAXoFexw3VP48dB+yBaVDf-ufDSizBxA3r-gt=_dqcJ2w@mail.gmail.com> (message from Lynn Winebarger on Sun, 24 Jul 2022 12:00:42 -0400)
> From: Lynn Winebarger <owinebar@gmail.com>
> Date: Sun, 24 Jul 2022 12:00:42 -0400
> Cc: michael.albinus@gmx.de, emacs-devel@gnu.org
>
> Additional note - if I delete the tramp-<hashes>.eln file from
> BUILD/native-lisp/28.1-<hash>/ without touching the corresponding elc
> file, the loading proceeds - although there are still issues to
> resolve in the subsequent tramp-X files being loaded.
If you remove the .eln file, Emacs will load the .elc file instead.
So I'm not really sure what does this factoid teach us.
Are you saying that if you try your "mega-dump" in a build without
native-compilation, it works without problems, and only the build with
native-compilation fails?
prev parent reply other threads:[~2022-07-24 16:23 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-24 0:47 Loading tramp for dump goes into infinite regress Lynn Winebarger
2022-07-24 7:55 ` Michael Albinus
2022-07-24 12:05 ` Lynn Winebarger
2022-07-24 12:23 ` Eli Zaretskii
2022-07-24 13:30 ` Lynn Winebarger
2022-07-24 13:34 ` Eli Zaretskii
2022-07-24 14:05 ` Lynn Winebarger
2022-07-24 14:09 ` Eli Zaretskii
2022-07-24 14:28 ` Lynn Winebarger
2022-07-24 16:00 ` Lynn Winebarger
2022-07-24 16:20 ` Lynn Winebarger
2022-07-24 16:31 ` Eli Zaretskii
2022-07-25 12:49 ` Lynn Winebarger
2022-07-25 13:56 ` Eli Zaretskii
2022-07-26 11:24 ` Lynn Winebarger
2022-07-27 0:58 ` Lynn Winebarger
2022-07-27 2:48 ` Lynn Winebarger
2022-07-27 8:31 ` Lynn Winebarger
2022-08-09 12:29 ` Lynn Winebarger
2022-08-09 12:36 ` Po Lu
2022-08-09 13:22 ` Lynn Winebarger
2022-08-09 13:42 ` Po Lu
2022-08-09 15:55 ` Lynn Winebarger
2022-07-25 16:54 ` Stefan Monnier
2022-07-25 17:05 ` Stefan Monnier
2022-07-26 0:28 ` Lynn Winebarger
2022-07-26 1:10 ` Lynn Winebarger
2022-08-06 6:07 ` Lynn Winebarger
2022-08-06 12:57 ` Lynn Winebarger
2022-08-06 15:39 ` Lynn Winebarger
2022-08-06 20:23 ` Working fully native-compiled "mega dump" (was Re: Loading tramp for dump goes into infinite regress) Lynn Winebarger
2022-08-06 20:52 ` Lynn Winebarger
2022-07-25 20:11 ` Loading tramp for dump goes into infinite regress Andrea Corallo
2022-07-31 20:22 ` Lynn Winebarger
2022-08-03 9:58 ` Lynn Winebarger
2022-08-03 12:22 ` Eli Zaretskii
2022-08-03 14:53 ` Native-compilation build process (was Re: Loading tramp for dump goes into infinite regress) Lynn Winebarger
2022-08-03 16:15 ` Eli Zaretskii
2022-08-04 3:33 ` Lynn Winebarger
2022-08-05 1:57 ` Lynn Winebarger
2022-07-24 16:23 ` Eli Zaretskii [this message]
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=83bktefpjo.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=michael.albinus@gmx.de \
--cc=owinebar@gmail.com \
/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).