unofficial mirror of gwl-devel@gnu.org
 help / color / mirror / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: Pjotr Prins <pjotr2019@thebird.nl>
Cc: gwl-devel@gnu.org
Subject: Re: `--run=simple` error ?
Date: Fri, 22 Feb 2019 22:05:45 +0100	[thread overview]
Message-ID: <CAJ3okZ0xFDGAsqYk0uX5xGPsh6vjSqx+EngPq-aNgG2voUxTuQ@mail.gmail.com> (raw)
In-Reply-To: <20190222165758.jidclqfqzphcejsm@thebird.nl>

Hi Pjotr,

> 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

Thank you for the trick.
I will use more containers. ;-)

However, the issue is now how to ./configure Guix and one also needs
to turn on container support (root privileges).
And say it is maybe not the most friendly. :-) I mean it is the hacker
solution (and yes they know how to choose their friend ;-)


Well, even I am still confused.

Which guix modules are going to the container ?
    a) the ones from the package guix in the checkout
or b) the ones of the checkout itself.
And is it the guix modules or only its dependencies? (guile, autotools, etc.)

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.


Cheers,
simon

  reply	other threads:[~2019-02-22 21:06 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 [this message]
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=CAJ3okZ0xFDGAsqYk0uX5xGPsh6vjSqx+EngPq-aNgG2voUxTuQ@mail.gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=gwl-devel@gnu.org \
    --cc=pjotr2019@thebird.nl \
    /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).