From: ludo@gnu.org (Ludovic Courtès)
To: "Cook, Malcolm" <MEC@stowers.org>
Cc: Guix-devel <guix-devel@gnu.org>, "'bug-guix@gnu.org'" <bug-guix@gnu.org>
Subject: Re: Test suite failures building 0.10.0 on CentOS7
Date: Thu, 31 Mar 2016 10:00:13 +0200 [thread overview]
Message-ID: <87lh4zcc1e.fsf@gnu.org> (raw)
In-Reply-To: <b663a59849944874a8d36fe4ee59d621@exchsrv2.sgc.loc> (Malcolm Cook's message of "Wed, 30 Mar 2016 22:37:55 +0000")
"Cook, Malcolm" <MEC@stowers.org> skribis:
> Thanks for the reminder about https://www.gnu.org/software/guix/manual/html_node/Running-the-Test-Suite.html I note there too that I should be emailing bug-guix@gnu.org instead of guix-devel. I've cc:ed it this time. What is the best going forward?
Yeah, using bug-guix@gnu.org for bug reports is the best way.
> I am building the release from git since I want to ./configure with a
> non-standard --localstatedir of /gnu/var
This can also be done when building from the tarball: just run
tar xf guix-0.10.0.tar.gz
cd guix-0.10.0
./configure --localstatedir=/gnu/var
…
> In any case I have reduced the issues by adding to my install mantra:
>
> export ACLOCAL_PATH=/usr/share/aclocal # as per https://www.gnu.org/software/guix/manual/guix.html#Building-from-Git
Another reason for using the release tarball: there’d be no such issues!
:-)
> In guix/cve.scm:
> 76: 2 [call-with-cve-port # 518400 ...]
> In guix/http-client.scm:
> 300: 1 [http-fetch/cached # # 518400 ...]
> In unknown file:
> ?: 0 [string-append #f "/http/" "Fjb931UJRoTPOjHq6hc1oawK9bCopdhOoX9grKLx71Q="]
>
> ERROR: In procedure string-append:
> ERROR: In procedure string-append: Wrong type (expecting string): #f'
This is a harmless failure: it indicates that neither the HOME nor the
XDG_CACHE_HOME environment variables are defined in the build
environment. Could you define one of these (they can point any writable
directory) and run ‘make recheck’?
Surely we should handle this situation better. I guess
‘cache-directory’ in (guix utils) should just error out in such a case,
with a clear error message. Thoughts?
Thanks,
Ludo’.
next prev parent reply other threads:[~2016-03-31 8:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <0296d40916d54cf5ac592c9620b6be17@exchsrv2.sgc.loc>
[not found] ` <8760w3bre5.fsf@gnu.org>
2016-03-30 22:37 ` Test suite failures building 0.10.0 on CentOS7 Cook, Malcolm
2016-03-31 8:00 ` Ludovic Courtès [this message]
2016-04-18 17:44 ` bug#23165: " 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=87lh4zcc1e.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=MEC@stowers.org \
--cc=bug-guix@gnu.org \
--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 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).