From: Pjotr Prins <pjotr2019@thebird.nl>
To: zimoun <zimon.toutoune@gmail.com>
Cc: gwl-devel@gnu.org
Subject: Re: `--run=simple` error ?
Date: Fri, 22 Feb 2019 17:57:58 +0100 [thread overview]
Message-ID: <20190222165758.jidclqfqzphcejsm@thebird.nl> (raw)
In-Reply-To: <CAJ3okZ2Z-6_QHJeO7XXve1a57RJv6bYbiBOvFWCQNt9onprNJg@mail.gmail.com>
On Fri, Feb 22, 2019 at 05:48:23PM +0100, zimoun wrote:
> Hi Pjotr,
>
> On Fri, 22 Feb 2019 at 17:33, Pjotr Prins <pjotr2019@thebird.nl> wrote:
> >
> > Yes, it can be hard. Best is to systematically rule out problems.
> > Containers are preferred by me because there is no chance of a mixup.
>
> Yes but when speaking about Guix modules, one wants the most
> up-to-date (i.e. from guix pull) which is not necessary the case with
> container (i.e. from guix package -i guix).
>
> From my understanding, there is a real "issue" for all the packages
> that depends on the package guix. For example emacs-guix, gwl that I
> am aware of.
You can run a container in a freshly compiled source tree. I do that
all the time. I don't normally use guix pull. Example using a D compiler
~/guix-master/pre-inst-env guix environment -C guix --ad-hoc ldc clang llvm unzip gdb ncurses vim git make cmake which less tzdata binutils
rm -rf CMakeFiles CMakeCache.txt
cmake .
make clean
make -j 24
next prev parent reply other threads:[~2019-02-22 17:04 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 [this message]
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
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=20190222165758.jidclqfqzphcejsm@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).