unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: "Taylan Ulrich \"Bayırlı/Kammer\"" <taylanbayirli@gmail.com>
Cc: 22354-done@debbugs.gnu.org
Subject: bug#22354: Test failure when running distcheck from out-of-tree build
Date: Tue, 12 Jan 2016 17:51:42 +0100	[thread overview]
Message-ID: <87ziwan3kx.fsf@gnu.org> (raw)
In-Reply-To: <87r3hnuple.fsf@T420.taylan> ("Taylan Ulrich \=\?utf-8\?Q\?\=5C\=22Bay\=C4\=B1rl\=C4\=B1\=2FKammer\=5C\=22\=22's\?\= message of "Tue, 12 Jan 2016 10:14:21 +0100")

taylanbayirli@gmail.com (Taylan Ulrich "Bayırlı/Kammer") skribis:

> If one runs distcheck from within the build directory of an out-of-tree
> build (perhaps a strange combination), the guix-environment.sh test
> fails with the following log snippet.

[...]

> ./configure: ./config.status: /home/taylan/src/guix/build/guix-0.9.1/_build/sub/test-tmp/store/d41iyl2gyk0r: bad interpreter: No such file or directory

I think you’re hitting the shebang limit (127 chars) that prevents you
from running test from that build tree.  ./configure emits a warning in
this case, which you should see in ‘config.log’.

So, not a bug, but it would have been nicer if ‘make check’ had failed
directly.  Commit bb25130 does that.

Though now that I look again at the error above, I see that we’re below
the 127 char limit.  Weird.

Thanks,
Ludo’.

  reply	other threads:[~2016-01-12 16:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-12  9:14 bug#22354: Test failure when running distcheck from out-of-tree build Taylan Ulrich Bayırlı/Kammer
2016-01-12 16:51 ` Ludovic Courtès [this message]
2016-01-12 19:40   ` Taylan Ulrich Bayırlı/Kammer
2016-01-12 20:54     ` Ludovic Courtès
2016-01-13  9:00       ` Taylan Ulrich Bayırlı/Kammer
2016-01-13 10:13         ` Ludovic Courtès
2016-01-13 10:42           ` Taylan Ulrich Bayırlı/Kammer
2016-01-13 10:25 ` bug#22354: Hash-bang line length 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=87ziwan3kx.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=22354-done@debbugs.gnu.org \
    --cc=taylanbayirli@gmail.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.
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).