From: Ricardo Wurmus <rekado@elephly.net>
To: mikadoZero <mikadozero@yandex.com>
Cc: Help Guix <help-guix@gnu.org>
Subject: Re: 14.1 Building from Git
Date: Mon, 18 Mar 2019 13:37:03 +0100 [thread overview]
Message-ID: <87wokwxssw.fsf@elephly.net> (raw)
In-Reply-To: <multrzs5.fsf@yandex.com>
mikadoZero <mikadozero@yandex.com> writes:
> I am trying to follow the instruction in the Contributing section of the
> manual, as I want to submit some patches. Following "14.1 Building from
> Git" I am getting an error when running `./bootstrap`.
>
> `guix describe`
> guix 19c0cdb
> repository URL: https://git.savannah.gnu.org/git/guix.git
> branch: master
> commit: 19c0cdb9e6271956015232421ef7f63a1ad001ae
>
> Here is what I am doing that leads to the error.
>
> `git clone https://git.savannah.gnu.org/git/guix.git`
>
> `cd guix`
>
> `guix environment guix`
Could you try if you get different behaviour with “guix environment
--pure guix”?
> configure.ac:88: error: possibly undefined macro: PKG_CHECK_MODULES
> If this token and others are legitimate, please use m4_pattern_allow.
> See the Autoconf documentation.
> configure.ac:89: error: possibly undefined macro: GUILE_MODULE_AVAILABLE
> configure.ac:96: error: possibly undefined macro: GUILE_PKG
> configure.ac:97: error: possibly undefined macro: GUILE_PROGS
This looks like some environment variables are not set properly. If you
set variables in ~/.bashrc, for example, (instead of ~/.bash_profile)
that could interfere with “guix environment”.
Could you please show the output of “env” after you ran “guix
environment guix”?
--
Ricardo
next prev parent reply other threads:[~2019-03-18 12:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-17 20:50 14.1 Building from Git mikadoZero
2019-03-18 10:08 ` Giovanni Biscuolo
2019-03-18 19:16 ` mikadoZero
2019-03-18 12:37 ` Ricardo Wurmus [this message]
2019-03-18 19:05 ` mikadoZero
2019-03-18 19:28 ` Leo Famulari
2019-03-19 15:39 ` mikadoZero
2019-03-18 19:54 ` Ricardo Wurmus
2019-03-19 15:34 ` mikadoZero
2019-03-19 16:08 ` Ricardo Wurmus
2019-03-20 21:20 ` mikadoZero
2019-03-19 19:17 ` Tobias Geerinckx-Rice
2019-03-20 21:25 ` mikadoZero
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=87wokwxssw.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=help-guix@gnu.org \
--cc=mikadozero@yandex.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).