From: Mark H Weaver <mhw@netris.org>
To: Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de>
Cc: 31841@debbugs.gnu.org
Subject: bug#31841: ./pre-inst-env guix system no longer works without ~/.config/guix
Date: Fri, 15 Jun 2018 09:08:00 -0400 [thread overview]
Message-ID: <87tvq4nqof.fsf@netris.org> (raw)
In-Reply-To: <8736xouuh7.fsf@mdc-berlin.de> (Ricardo Wurmus's message of "Fri, 15 Jun 2018 14:04:04 +0200")
Hi,
Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de> writes:
> Ludovic Courtès <ludo@gnu.org> writes:
>
>> Hello,
>>
>> Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de> skribis:
>>
>>> When outside of an environment containing guile-sqlite3 strace shows
>>> that Guix tries to load it right before failing. The cause here is the
>>> autoloading of (guix store database), which depends on the sqlite
>>> bindings.
>>
>> Indeed. Commit c5a2e1ffcb029f50c4c18352cf378b61c41c625e made
>> guile-sqlite3 a requirement, but ‘configure’ is supposed to error out if
>> it’s not found.
>>
>> Mark, any idea why ‘configure’ didn’t fail for you? What does
>> ‘config.log’ say?
>
> I have the same problem when using “pre-inst-env” outside of a
> development environment. So “configure” succeeds (when run inside “guix
> enviromnent guix”), but “./pre-inst-env guix system --help” fails when
> run outside of that environment.
Indeed. I make sure to run 'make' within a development environment, but
until now I've been able to *run* Guix using ./pre-inst-env outside of
the development environment.
My preferred mode of operation has always been to run 'guix' from my
private git checkout. For years I was able to arrange this by manually
installing a symlink from ~/.config/guix/latest to my git checkout, but
at some point that stopped working, so now I have a small 'guix' script
in ~mhw/bin and ~root/bin:
#!/bin/sh
exec /home/mhw/guix/pre-inst-env guix "$@"
I suppose I could extend this script to run 'pre-inst-env' within the
development environment, but I wonder if there's a reason not to have
'pre-inst-env' install the necessary environment. That would seem to be
its job, no?
Mark
next prev parent reply other threads:[~2018-06-15 13:10 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-15 2:24 bug#31841: ./pre-inst-env guix system no longer works without ~/.config/guix Mark H Weaver
2018-06-15 6:56 ` Rutger Helling
2018-06-15 10:56 ` myglc2
2018-06-15 11:24 ` Ricardo Wurmus
2018-06-15 11:45 ` Ludovic Courtès
2018-06-15 12:04 ` Ricardo Wurmus
2018-06-15 13:08 ` Mark H Weaver [this message]
2018-06-15 13:40 ` Mark H Weaver
2018-06-15 16:51 ` Ludovic Courtès
2018-06-15 22:56 ` myglc2
2018-06-16 8:06 ` Mark H Weaver
2018-06-16 8:25 ` Ludovic Courtès
2018-06-16 9:50 ` Mark H Weaver
2018-06-16 14:31 ` George Clemmer
2018-06-17 20:53 ` Ludovic Courtès
2018-06-19 17:08 ` myglc2
2018-06-20 14:06 ` Ludovic Courtès
2018-06-16 7:51 ` Mark H Weaver
2018-06-17 12:54 ` bug#31841: Status: Guix requires guile-sqlite3 Maxim Cournoyer
2018-06-17 21:19 ` Ludovic Courtès
2018-06-18 1:34 ` Maxim Cournoyer
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87tvq4nqof.fsf@netris.org \
--to=mhw@netris.org \
--cc=31841@debbugs.gnu.org \
--cc=ricardo.wurmus@mdc-berlin.de \
/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/guix.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).