From: "brettg@posteo.net" <brettg@posteo.net>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: Newt and Guix pull failing
Date: Sun, 21 Apr 2019 10:20:51 -0500 [thread overview]
Message-ID: <eoo6dm0o32ukooo246fqhuvv.1555859875475@email.lge.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1214 bytes --]
Hey Ludo, thank you for taking a moment to look at this. I have guile_load_path set in both a .guile and .bashrc for a few custom path references. https://git.sr.ht/~brettgilio/guix-system/tree/master/dotfiles/.bashrcI will check and see what guile_load_path is returning when I get a chance. Sent from my Sprint Phone.------ Original message------From: Ludovic CourtèsDate: Sun, Apr 21, 2019 7:39 AMTo: brettg@posteo.net;Cc: help-guix;Subject:Re: Newt and Guix pull failingHello,
brettg@posteo.net skribis:
> I reference the newt module in this file of my channel
> https://git.sr.ht/~brettgilio/guix-system/tree/master/guile-modules/gscale/screen.scm
>
> However, when I `guix pull` it fails to build citing that there is no
> code available for that module. I have guile-newt installed system
> wide, and to my local profile manifest, but neither of those fix the
> issue.
When Guile and Guile-Newt are in the same profile, the GUILE_LOAD_PATH
and GUILE_LOAD_COMPILED_PATH are automatically set appropriately:
guix environment -C --ad-hoc guile guile-newt -- guile -c '(use-modules (newt))'
# success
So it looks like GUILE_LOAD_PATH may be unset or wrong in your case.
Ludo’.
[-- Attachment #2: Type: text/html, Size: 2250 bytes --]
next reply other threads:[~2019-04-21 15:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-21 15:20 brettg [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-04-20 19:37 Newt and Guix pull failing brettg
2019-04-21 12:39 ` Ludovic Courtès
2019-04-21 23:17 ` Brett Gilio
2019-04-22 19:51 ` brettg
2019-04-23 21:53 ` Ludovic Courtès
2019-04-23 22:15 ` Brett Gilio
2019-04-23 5:35 ` Gábor Boskovits
2019-04-23 14:20 ` brettg
2019-04-23 16:45 ` Gábor Boskovits
2019-04-23 16:49 ` brettg
2019-04-23 18:44 ` brettg
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=eoo6dm0o32ukooo246fqhuvv.1555859875475@email.lge.com \
--to=brettg@posteo.net \
--cc=help-guix@gnu.org \
--cc=ludo@gnu.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/guix.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.