From: ludo@gnu.org (Ludovic Courtès)
To: Fis Trivial <ybbs.daans@hotmail.com>
Cc: "guix-devel@gnu.org" <guix-devel@gnu.org>
Subject: Re: Errors encountered in building guix from source.
Date: Wed, 24 Jan 2018 15:32:29 +0100 [thread overview]
Message-ID: <87shavz5s2.fsf@gnu.org> (raw)
In-Reply-To: <MWHPR16MB0063863252112FF78DAF338B92EE0@MWHPR16MB0063.namprd16.prod.outlook.com> (Fis Trivial's message of "Sat, 20 Jan 2018 20:16:04 +0000")
Fis Trivial <ybbs.daans@hotmail.com> skribis:
> * Do as the menu said
> So I ran the following command in sequence:
> $ guix environment guix --ad-hoc help2man git strace
> $ ./bootstrap
> $ ./configure --localstatedir=/var
>
> The last configure command resulted in error, here is the last part from output:
>
> configure: checking for guile 2.2
> configure: found guile 2.2
> checking for guile-2.2... no
> checking for guile2.2... no
> checking for guile-2... no
> checking for guile2... /usr/bin/guile2
> configure: error: found development files for Guile 2.2, but /usr/bin/guile2 has effective version 2.0
Most likely your .bashrc, .bash_profile, or similar is overriding PATH
and other environment variables defined by ‘guix environment’, which is
why /usr/bin/guile2 takes precedence.
See the footnote at
<https://www.gnu.org/software/guix/manual/html_node/Invoking-guix-environment.html#FOOT15>.
HTH,
Ludo’.
next prev parent reply other threads:[~2018-01-24 14:32 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 [this message]
2018-01-25 15:12 ` Oleg Pykhalov
2018-01-25 20:58 ` Fis Trivial
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
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=87shavz5s2.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=ybbs.daans@hotmail.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.
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).