From: Robert Pluim <rpluim@gmail.com>
To: joakim@verona.se
Cc: 53038@debbugs.gnu.org
Subject: bug#53038: 28.0.50; problem building
Date: Fri, 07 Jan 2022 16:25:27 +0100 [thread overview]
Message-ID: <87sftz600o.fsf@gmail.com> (raw)
In-Reply-To: <87o84nr342.fsf@tanaka.verona.se> (joakim@verona.se's message of "Fri, 07 Jan 2022 16:13:01 +0100")
>>>>> On Fri, 07 Jan 2022 16:13:01 +0100, joakim@verona.se said:
joakim> It turns out I have been using a guix emacs build, and for some reason
joakim> guix sets
joakim> EMACSLOADPATH=/home/joakim/.guix-profile/share/emacs/site-lisp:/home/joakim/.guix-profile/share/emacs/site-lisp:/home/joakim/.guix-profile/share/emacs/site-lisp:/gnu/store/divi72vf7cw42kcr8w4h6j3pn4npicl8-emacs-native-comp-28.0.50-183.6885c62/share/emacs/28.0.50/lisp
joakim> if I unset EMACSLOADPATH, the build finishes.
That sounds like we should put
EMACSLOADPATH=
in front of the emacs invocation from admin/unidata/Makfile, by
analogy to lisp/Makefile, ie:
emacs = EMACSLOADPATH= "${EMACS}" -batch --no-site-file --no-site-lisp
Does that help?
joakim> Anyway, thanks for your patience, and in the best of worlds this mail
joakim> transcript might help someone else. Thanks!
No worries, itʼs what they pay us for ;-)
Robert
--
next prev parent reply other threads:[~2022-01-07 15:25 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87sftz600o.fsf@gmail.com \
--to=rpluim@gmail.com \
--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 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.