unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: iyzsong@member.fsf.org (宋文武)
To: "Cook, Malcolm" <MEC@stowers.org>
Cc: 23524@debbugs.gnu.org
Subject: bug#23524: Test suite failures building 0.10.0 on CentOS7 - building from git
Date: Sun, 15 May 2016 16:46:38 +0800	[thread overview]
Message-ID: <87r3d3d7yp.fsf@member.fsf.org> (raw)
In-Reply-To: <1463091775110.48039@stowers.org> (Malcolm Cook's message of "Thu, 12 May 2016 22:22:55 +0000")

"Cook, Malcolm" <MEC@stowers.org> writes:

> Ludo!
>
> It has been far too long that I followed up on this.  I have just now return to this project.
>
> Setting HOME, as you last suggested, got me past the `make check` problems from before.  Thank you.
>
> However,  `make check` still apparently halts after:
>
> ....
> PASS: tests/guix-package-net.sh
> PASS: tests/guix-package.sh
> PASS: tests/guix-build.sh
> PASS: tests/guix-environment.sh
> PASS: tests/builders.scm
>
> The tests apparently stop running.  Top agrees with me.
>
> At this point, all checks have PASSed  except guix-lint.sh, which is the single file tarred up in checkFAIL.tar.gz
>
> LOG.tar.gz contains logs of stdout/stderr from each step so far:
> bookstrap, configure, make, make check. and also a file detailing the
> version of RPM installed on my CentOS 7 box.
>
> Note - All this is still trying to build based on git, viz:
>
>     git clone git://git.savannah.gnu.org/guix.git  --branch v0.10.0  guix
>
> .... and still of course performing the ./bootstrap.
>
> I will in a separate message detail what happens when I try and build from the release tarball.
>
> However, I would like to understand what the issues are with building
> using git.  Is there a good explanation on the possible issues that
> are avoided by using the release tarball?
With the release tarball, the ‘configure’ script and documents (man
pages and info) are already built, so autotools, help2man etc. are
not required to build guix.

The failing one in the guix-lint.log:
--8<---------------cut here---------------start------------->8---
<...>
;;; Failed to autoload make-session in (gnutls):
;;; ERROR: missing interface for module (gnutls)
Backtrace:
<...>
In guix/build/download.scm:
 256: 0 [tls-wrap #<input-output: socket 10> "static.nvd.nist.gov"]

guix/build/download.scm:256:17: In procedure tls-wrap:
guix/build/download.scm:256:17: In procedure module-lookup: Unbound variable: make-session'
<...>
--8<---------------cut here---------------end--------------->8---

It’s due to missing ‘guile-gnutls’ in your host system,
and the ‘cve’ checker of ‘guix lint’ need it to access the URL
through HTTPS.  Seems like we should skip those tests if the gnutls
module is not available.

Once build guix on your host (it uses glibc, guile,
guile-gnutls, etc on your host system), you can install (or without
substitutes, build) guix from guix, which will use glibc,
guile-gnutls, etc in guix (all in /gnu/store).

Thanks your report!

  reply	other threads:[~2016-05-16 17:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-12 22:22 bug#23524: Test suite failures building 0.10.0 on CentOS7 - building from git Cook, Malcolm
2016-05-15  8:46 ` 宋文武 [this message]
2016-05-24 12:46 ` Ludovic Courtès

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=87r3d3d7yp.fsf@member.fsf.org \
    --to=iyzsong@member.fsf.org \
    --cc=23524@debbugs.gnu.org \
    --cc=MEC@stowers.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 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).