From: Pjotr Prins <pjotr2019@thebird.nl>
To: zimoun <zimon.toutoune@gmail.com>
Cc: gwl-devel@gnu.org
Subject: Re: `--run=simple` error ?
Date: Sun, 24 Feb 2019 13:02:27 +0100 [thread overview]
Message-ID: <20190224120227.ebv54vt6hhzvkozd@thebird.nl> (raw)
In-Reply-To: <CAJ3okZ1cfvvdx5qsHpOWgEVUwt2-46pL0us5cHoj0aCpyjuwZA@mail.gmail.com>
On Sun, Feb 24, 2019 at 12:40:13PM +0100, zimoun wrote:
> Hi Pjotr,
>
> On Fri, 22 Feb 2019 at 22:18, Pjotr Prins <pjotr2019@thebird.nl> wrote:
> >
> > guix environment -C guix
> >
> > pulls in everything you need to build guix itself.
>
> If I understand well, this sequence:
>
> cd ~/guix-master
> git checkout <hash>
> cd /path/to/project
> ~/guix-master/pre-inst-env guix environment -C tool --ad-hoc other tools
>
> is nouw somehow equivalent to:
>
> guix pull --commit=<hash>
> guix environment -C tool --ad-hoc othertools
Guix pull also pulls in its build environment.
> Right?
>
> > > And is it the guix modules or only its dependencies? (guile, autotools, etc.)
> >
> > try it, you can check. Also read
> >
> > https://github.com/pjotrp/guix-notes/blob/master/INSTALL.org#building-gnu-guix-from-source-using-guix---the-bullet-proof-way
> >
> > > And idem if you run instead:
> > > ~/guix-master/pre-inst-env guix environment -C gwl --ad-hoc some other tools
> > > or any other package that depends on Guix.
>
>
> In fact, the question is how to do when a package (gwl) depends on
> Guix the library.
> Kind of build time vs run time. If I understand well.
> It was my initial issue: gwl was built with a version of Guix. Then it
> fails at run time because the very Guix version was incompatible.
Yeah. You have to get the PATHs right for the different purposes.
Pj.
next prev parent reply other threads:[~2019-02-24 12:09 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-21 15:22 `--run=simple` error ? zimoun
2019-02-21 15:40 ` Ricardo Wurmus
2019-02-22 16:22 ` zimoun
2019-02-22 16:33 ` Pjotr Prins
2019-02-22 16:48 ` zimoun
2019-02-22 16:57 ` Pjotr Prins
2019-02-22 21:05 ` zimoun
2019-02-22 21:18 ` Pjotr Prins
2019-02-24 11:40 ` zimoun
2019-02-24 12:02 ` Pjotr Prins [this message]
2019-02-22 16:35 ` Ricardo Wurmus
2019-02-22 16:55 ` zimoun
2019-02-22 17:04 ` Ricardo Wurmus
2019-02-22 21:10 ` zimoun
2019-02-22 22:54 ` Ricardo Wurmus
2019-02-24 11:56 ` zimoun
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.guixwl.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190224120227.ebv54vt6hhzvkozd@thebird.nl \
--to=pjotr2019@thebird.nl \
--cc=gwl-devel@gnu.org \
--cc=zimon.toutoune@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.
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).