all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Andrea Corallo <akrl@sdf.org>
To: "Gerd Möllmann" <gerd.moellmann@gmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>, larsi@gnus.org, 57309@debbugs.gnu.org
Subject: bug#57309: 29.0.50; Build error "trying to dump non fixed-up eln file"
Date: Mon, 22 Aug 2022 08:49:30 +0000	[thread overview]
Message-ID: <xjf7d30fysl.fsf@ma.sdf.org> (raw)
In-Reply-To: <m2bksd66pr.fsf@Mini.fritz.box> ("Gerd Möllmann"'s message of "Sun, 21 Aug 2022 15:56:16 +0200")

Gerd Möllmann <gerd.moellmann@gmail.com> writes:

> Eli Zaretskii <eliz@gnu.org> writes:
>
>>> Note that --bin-dest and --eln-dest have no arguments.
>>
>> Their values are defined in the top-level Makefile.  Why are they
>> empty in your case?
>
> Exactly.
>
> 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 :-).
>
> (BTW, doesn't GNU make have an 'export', or do I misremember that.
> Whatever....)
>
> I'll commit this soon.

Sorry for the naive question but I just skimmed the whole thread.  Can
we consider this bug understood or there's something that still need
investigation/fix?

Thanks

  Andrea





  parent reply	other threads:[~2022-08-22  8:49 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
2022-08-22  8:49                               ` Andrea Corallo [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=xjf7d30fysl.fsf@ma.sdf.org \
    --to=akrl@sdf.org \
    --cc=57309@debbugs.gnu.org \
    --cc=eliz@gnu.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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.