From: Fis Trivial <ybbs.daans@hotmail.com>
To: Oleg Pykhalov <go.wigust@gmail.com>
Cc: "guix-devel@gnu.org" <guix-devel@gnu.org>
Subject: Re: Errors encountered in building guix from source.
Date: Thu, 25 Jan 2018 20:58:38 +0000 [thread overview]
Message-ID: <MWHPR16MB0063341575D1C01F3AE3FDF292E10@MWHPR16MB0063.namprd16.prod.outlook.com> (raw)
In-Reply-To: <87fu6uezvo.fsf@gmail.com>
Sorry for the really late reply.
>
> Installing a missing package by guessing from non-existing command is a
> Fedora's “feauture” of Bash. I believe this is a reason of following
> failures. You probably could avoid this by starting a Bash process with
>
> bash --noprofile
>
> [...]
>
It would be nice to be included in document.
>
> Please, run 'sudo' not from 'guix environment'. (Press Ctrl+D to exit
> from an 'guix environment').
>
Can we put it in the document too? :)
>
> What are the exact commands you are giving?
>
> Pj.
>
I succeeded at the second time according to your guide, don't know why,
maybe missing something. All in all, I sent the remaining patches for
some packages to guix and those are accepted. :)
I think I will have to disable guix for a while since it's really messing
up with my environment and I currently don't have the time to deal with
it. :(
I will come back latter and try joining the development for guix itself,
really sorry.
Fis.
next prev parent reply other threads:[~2018-01-25 20:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-20 20:16 Errors encountered in building guix from source Fis Trivial
2018-01-20 20:45 ` Pjotr Prins
2018-01-21 9:13 ` Fis Trivial
2018-01-21 10:50 ` Pjotr Prins
2018-01-24 14:32 ` Ludovic Courtès
2018-01-25 15:12 ` Oleg Pykhalov
2018-01-25 20:58 ` Fis Trivial [this message]
2018-01-26 15:25 ` Oleg Pykhalov
2018-01-27 15:12 ` Fis Trivial
2018-01-29 19:20 ` Oleg Pykhalov
2018-01-29 22:35 ` Fis Trivial
2018-01-28 3:16 ` Chris Marusich
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=MWHPR16MB0063341575D1C01F3AE3FDF292E10@MWHPR16MB0063.namprd16.prod.outlook.com \
--to=ybbs.daans@hotmail.com \
--cc=go.wigust@gmail.com \
--cc=guix-devel@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.