From: Eli Zaretskii <eliz@gnu.org>
To: "Gerd Möllmann" <gerd.moellmann@gmail.com>
Cc: larsi@gnus.org, 57309@debbugs.gnu.org, akrl@sdf.org
Subject: bug#57309: 29.0.50; Build error "trying to dump non fixed-up eln file"
Date: Sun, 21 Aug 2022 17:02:59 +0300 [thread overview]
Message-ID: <83v8qlbsoc.fsf@gnu.org> (raw)
In-Reply-To: <m2bksd66pr.fsf@Mini.fritz.box> (message from Gerd Möllmann on Sun, 21 Aug 2022 15:56:16 +0200)
> From: Gerd Möllmann <gerd.moellmann@gmail.com>
> Cc: larsi@gnus.org, 57309@debbugs.gnu.org, akrl@sdf.org
> Date: Sun, 21 Aug 2022 15:56:16 +0200
>
> diff --git a/Makefile.in b/Makefile.in
> index 78103f897f..7541e8d6b6 100644
> --- a/Makefile.in
> +++ b/Makefile.in
> @@ -367,7 +367,7 @@ .PHONY:
> # .pdmp containing the new autoloads.
> .PHONY: src-depending-on-lisp
> src-depending-on-lisp: lisp
> - ${MAKE} -C src
> + ${MAKE} -C src BIN_DESTDIR='$(BIN_DESTDIR)' ELN_DESTDIR='$(ELN_DESTDIR)'
>
> # If configure were to just generate emacsver.tex from emacsver.tex.in
> # in the normal way, the timestamp of emacsver.tex would always be
>
>
> Everything falls back on oneself :-).
Right. As it should.
> (BTW, doesn't GNU make have an 'export', or do I misremember that.
It does.
next prev parent reply other threads:[~2022-08-21 14:02 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-20 12:55 bug#57309: 29.0.50; Build error "trying to dump non fixed-up eln file" Gerd Möllmann
2022-08-20 13:07 ` Lars Ingebrigtsen
2022-08-20 13:12 ` Gerd Möllmann
2022-08-20 13:18 ` Lars Ingebrigtsen
2022-08-20 13:21 ` Gerd Möllmann
2022-08-20 13:26 ` Eli Zaretskii
2022-08-20 13:29 ` Lars Ingebrigtsen
2022-08-20 13:45 ` Eli Zaretskii
2022-08-21 11:55 ` Lars Ingebrigtsen
2022-08-20 13:27 ` Lars Ingebrigtsen
2022-08-20 13:37 ` Gerd Möllmann
2022-08-20 14:32 ` Gerd Möllmann
2022-08-20 15:08 ` Gerd Möllmann
2022-08-21 7:03 ` Gerd Möllmann
2022-08-21 8:50 ` Gerd Möllmann
2022-08-21 10:13 ` Eli Zaretskii
2022-08-21 10:45 ` Gerd Möllmann
2022-08-21 10:58 ` Eli Zaretskii
2022-08-22 8:43 ` Andrea Corallo
2022-08-20 15:25 ` Eli Zaretskii
2022-08-21 6:39 ` Gerd Möllmann
2022-08-21 6:43 ` Eli Zaretskii
2022-08-21 6:47 ` Gerd Möllmann
2022-08-21 7:03 ` Eli Zaretskii
2022-08-21 7:13 ` Gerd Möllmann
2022-08-21 11:57 ` Lars Ingebrigtsen
2022-08-21 12:28 ` Gerd Möllmann
2022-08-21 12:36 ` Eli Zaretskii
2022-08-21 12:46 ` Gerd Möllmann
2022-08-21 12:55 ` Eli Zaretskii
2022-08-21 13:08 ` Gerd Möllmann
2022-08-21 13:19 ` Eli Zaretskii
2022-08-21 13:11 ` Gerd Möllmann
2022-08-21 13:14 ` Gerd Möllmann
2022-08-21 13:39 ` Gerd Möllmann
2022-08-21 13:45 ` Eli Zaretskii
2022-08-21 13:56 ` Gerd Möllmann
2022-08-21 14:02 ` Eli Zaretskii [this message]
2022-08-22 8:49 ` Andrea Corallo
2022-08-22 8:56 ` Gerd Möllmann
2022-08-22 9:35 ` Andrea Corallo
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=83v8qlbsoc.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=57309@debbugs.gnu.org \
--cc=akrl@sdf.org \
--cc=gerd.moellmann@gmail.com \
--cc=larsi@gnus.org \
/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).