From: Lynn Winebarger <owinebar@gmail.com>
To: Andrea Corallo <akrl@sdf.org>
Cc: Eli Zaretskii <eliz@gnu.org>,
Michael Albinus <michael.albinus@gmx.de>,
emacs-devel <emacs-devel@gnu.org>
Subject: Re: Loading tramp for dump goes into infinite regress
Date: Wed, 3 Aug 2022 05:58:17 -0400 [thread overview]
Message-ID: <CAM=F=bA_FcNOy8YMqmGuGXbhHnhRQiesDe+KqXm+GUia_O9ewA@mail.gmail.com> (raw)
In-Reply-To: <CAM=F=bCePsB+wJseZYWSFYmBNoDh3ZxpzdYNcYSgC8nNZoGtCA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1333 bytes --]
On Sun, Jul 31, 2022, 4:22 PM Lynn Winebarger <owinebar@gmail.com> wrote:
> On Mon, Jul 25, 2022, 4:11 PM Andrea Corallo <akrl@sdf.org> wrote:
>
>>
>> BTW I think so far we do not support re-dumping Emacs twice with native
>> code. This is not a deep technical limitaiton, it's only because how we
>> fixup relative eln paths to support installed and non installed builds,
>> we should probably work on this limitation...
>
>
> I still can't figure out why building with native compilation and a
> site-load file was producing an error about trying to load an incoherent
> ELN file.
>
I found the problem - when I run make in the src directory, the variables
for the ELN and bin destinations are blank, which causes the code in loadup
that is supposed to make the compilation unit names into pairs to not
bother.
Maybe these two variables should get constructed in src/Makefile.in?
Running make from the src directory shouldn't result in an unusable dump
file.
I'd probably make the code in loadup either throw an error or come up with
some reasonable default. If you insist on having the final installation
specified, then it should just error during the build instead of producing
a dump guaranteed to fail when loaded. Otherwise, either use some dummy
values or just treat the build directory as the install directory.
Lynn
[-- Attachment #2: Type: text/html, Size: 2144 bytes --]
next prev parent reply other threads:[~2022-08-03 9:58 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 [this message]
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 ` Loading tramp for dump goes into infinite regress Eli Zaretskii
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='CAM=F=bA_FcNOy8YMqmGuGXbhHnhRQiesDe+KqXm+GUia_O9ewA@mail.gmail.com' \
--to=owinebar@gmail.com \
--cc=akrl@sdf.org \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=michael.albinus@gmx.de \
/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).