From: joakim@verona.se
To: Robert Pluim <rpluim@gmail.com>
Cc: 53038@debbugs.gnu.org
Subject: bug#53038: 28.0.50; problem building
Date: Fri, 07 Jan 2022 13:55:12 +0100 [thread overview]
Message-ID: <87pmp3so27.fsf@tanaka.verona.se> (raw)
In-Reply-To: <875yqv7me0.fsf@gmail.com> (Robert Pluim's message of "Fri, 07 Jan 2022 13:36:55 +0100")
Robert Pluim <rpluim@gmail.com> writes:
>>>>>> On Fri, 07 Jan 2022 13:44:08 +0200, Eli Zaretskii <eliz@gnu.org> said:
>
> >> From: joakim@verona.se
> >> Cc: 53038@debbugs.gnu.org
> >> Date: Fri, 07 Jan 2022 09:44:14 +0100
> >>
> >> > When the build fails, does the file lisp/international/emoji.el exist?
> >>
> >> It does exist, yes.
>
> Eli> So the problem seems to be with finding files via load-path.
>
> Eli> My suggestion is to run the failing command manually, and if it also
> Eli> fails, run it under a debugger to see why Emacs cannot find an
> Eli> existing Lisp file.
>
> Looking through the build log, $PWD and the paths reported by the
> build look different. Is there some symlinking or NFS-mounting going
> on?
There is:
ls -la ~|grep build
lrwxrwxrwx. 1 joakim joakim 9 Oct 8 2019 build -> /mnt/fast
To rule out this being a problem I went to the target of the symlink,
and did maintainer-clean, and make again. The problem persists.
For fun I can try on a completely different disk.
>
> Robert
--
Joakim Verona
joakim@verona.se
next prev parent reply other threads:[~2022-01-07 12:55 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 [this message]
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
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=87pmp3so27.fsf@tanaka.verona.se \
--to=joakim@verona.se \
--cc=53038@debbugs.gnu.org \
--cc=rpluim@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).