unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Ricardo Wurmus <rekado@elephly.net>
To: Catonano <catonano@gmail.com>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: test-driver
Date: Mon, 10 Apr 2017 08:20:41 +0200	[thread overview]
Message-ID: <87vaqc237q.fsf@elephly.net> (raw)
In-Reply-To: <CAJ98PDwkYPAKxGWUCfUhghfisbsKGMvEU=d-60UjVdf_w1v1fw@mail.gmail.com>


Catonano <catonano@gmail.com> writes:

> In trying to build libxls tests fail because a test-driver file is missing
>
> Like this
>
> ...
> make check-TESTS
> make[2]: ingresso nella directory
> "/tmp/guix-build-libxsl-1.4.0.drv-0/source/libxls/test"
> make[3]: ingresso nella directory
> "/tmp/guix-build-libxsl-1.4.0.drv-0/source/libxls/test"
> /gnu/store/qkw4zrwfybxww8f56nkb6hggxambk89b-bash-4.4.0/bin/bash:
> ../test-driver: File o directory non esistente
> ...
>
> I asked upstream and I was informed that there's no "test-driver"
> occurrence in libxls source. So they suggest it has to be something
> specific of my build environment
>
> You can see the exchange we had, here
> https://sourceforge.net/p/libxls/discussion/294119/thread/4b5ce0d8/?limit=25#1550
>
> Here is my definition for libxls
> http://paste.lisp.org/display/342783

Here’s my updated definition:

    http://paste.lisp.org/display/342783#1

> Is this a Guix thing ?

Unlikely.  I found that rebootstrapping fixes this, so it appears to be
part of the generated files in the release tarball.

-- 
Ricardo

GPG: BCA6 89B6 3655 3801 C3C6  2150 197A 5888 235F ACAC
https://elephly.net

  reply	other threads:[~2017-04-10  6:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-29 14:07 test-driver Catonano
2017-04-10  6:20 ` Ricardo Wurmus [this message]
2017-04-10  7:09   ` test-driver Catonano

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=87vaqc237q.fsf@elephly.net \
    --to=rekado@elephly.net \
    --cc=catonano@gmail.com \
    --cc=help-guix@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.
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).