From: Julien Lepiller <julien@lepiller.eu>
To: HiPhish <hiphish@posteo.de>,49145@debbugs.gnu.org
Subject: bug#49145: Cannot build Guix (Texinfo failure)
Date: Tue, 22 Jun 2021 08:06:59 -0400 [thread overview]
Message-ID: <D3303D39-EAEA-4B5A-B080-ECAD10B5504E@lepiller.eu> (raw)
In-Reply-To: <4629869.GXAFRqVoOG@titan>
[-- Attachment #1: Type: text/plain, Size: 1152 bytes --]
Something seems to have gone wrong with the i18n code. Maybe we use something that's not recognized by your shell? Can you try again, but this time configure and make in a pure environment? (Add --pure to the guix environment invocation).
Le 20 juin 2021 17:37:34 GMT-04:00, HiPhish <hiphish@posteo.de> a écrit :
>Hello,
>
>I have been trying to build Guix from source (in order to contribute a
>new
>package), but the `make` step fails every time. I am on Void Linux
>(glibc) and
>I have checked out commit d027858e70c4a37aca90b1d4ecb2f0421a95d987.
>
>Here are the steps I took after checking out the repo:
>
> guix environment guix
> ./bootstrap
> ./configure --localstatedir=/var
> make
>
>The error messages are all complaining to that cross-references in
>Texinfo
>cannot be resolved. I have attached the full log. I already tried with
>a
>freshly checked out repository, and with both a pure Guix environment
>and a
>regular one.
>
>I had the same issue a couple of weeks ago, and I don't know if the
>issue is
>related to my distribution. Please let me know if you need any more
>information.
[-- Attachment #2: Type: text/html, Size: 1405 bytes --]
next prev parent reply other threads:[~2021-06-22 12:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-20 21:37 bug#49145: Cannot build Guix (Texinfo failure) HiPhish
2021-06-22 12:06 ` Julien Lepiller [this message]
2021-06-22 17:18 ` HiPhish
2021-06-25 22:26 ` HiPhish
2021-06-26 10:58 ` Julien Lepiller
2021-06-28 21:27 ` HiPhish
2021-07-09 16:21 ` HiPhish
2021-11-10 21:33 ` bug#49145: Solved, I guess HiPhish
2021-11-11 15:59 ` Maxim Cournoyer
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=D3303D39-EAEA-4B5A-B080-ECAD10B5504E@lepiller.eu \
--to=julien@lepiller.eu \
--cc=49145@debbugs.gnu.org \
--cc=hiphish@posteo.de \
/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.