unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: joakim@verona.se
Cc: 53038@debbugs.gnu.org
Subject: bug#53038: 28.0.50; problem building
Date: Fri, 07 Jan 2022 16:09:59 +0100	[thread overview]
Message-ID: <87ee5jd1ko.fsf@gnus.org> (raw)
In-Reply-To: <87y23t3oqg.fsf@tanaka.verona.se> (joakim@verona.se's message of "Wed, 05 Jan 2022 21:35:19 +0100")

joakim@verona.se writes:

> This is not a bug report of a running emacs, its a bug report of
> building emacs from a fresh checkout. I include the complete build output.

If this build is really happening in a fresh checkout, then there's
something very wrong on your machine somewhere, because your compilation
full is full of:

> Reloading stale leim-list.el
> Loading /mnt/fast/emacs2022/emacs/lisp/leim/leim-list.el (source)...

Which seems to indicate that your build is somehow picking up .el files
from somewhere else.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  parent reply	other threads:[~2022-01-07 15:09 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-05 20:35 bug#53038: 28.0.50; problem building joakim
2022-01-06 23:44 ` bug#53038: more info, build problems joakim
2022-01-07  6:56   ` bug#53038: 28.0.50; problem building Eli Zaretskii
2022-01-07  8:44     ` joakim
2022-01-07 11:44       ` Eli Zaretskii
2022-01-07 12:08         ` joakim
2022-01-07 12:24           ` Eli Zaretskii
2022-01-07 12:39             ` joakim
2022-01-07 12:55               ` Eli Zaretskii
2022-01-07 15:13                 ` joakim
2022-01-07 15:25                   ` Robert Pluim
2022-01-07 12:36         ` Robert Pluim
2022-01-07 12:55           ` joakim
2022-01-07 13:43             ` Robert Pluim
2022-01-07 14:58               ` joakim
2022-01-07 15:05                 ` Robert Pluim
2022-01-07 15:09 ` Lars Ingebrigtsen [this message]
2022-01-07 15:32   ` joakim
2022-01-12 17:49     ` Glenn Morris

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=87ee5jd1ko.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=53038@debbugs.gnu.org \
    --cc=joakim@verona.se \
    /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).