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 21:54:37 +0100 [thread overview]
Message-ID: <87k2nea582.fsf@gnu.org> (raw)
In-Reply-To: <87mvsavb61.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 20:40:38 +0100")
taylanbayirli@gmail.com (Taylan Ulrich "Bayırlı/Kammer") skribis:
> ludo@gnu.org (Ludovic Courtès) writes:
>
>> 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.
>
> Hmm, that commit didn't fix the issue.
You mean it doesn’t error out directly upon ‘make check’? Could you
run “grep length …/_build/config.log”?
> I'm also puzzled by the cut-off of the shebang string at 77 characters
> in the error message, so I looked into it a bit, but nothing strange
> here from what I can tell: the ./configure of make-4.1 is called with
> SHELL and CONFIG_SHELL set to
>
> /home/taylan/src/guix/build/guix-0.9.1/_build/sub/test-tmp/store/d41iyl2gyk0rwd9z2ddgph9nyg48f3p0-bootstrap-binaries-0/bin/bash
>
> which is exactly 127 characters, but add #! and you have 129. This ends
> up being the shebang of config.status, which is why it fails while
> trying to call that.
So the diagnostic was correct.
> Only the error message is broken.
Would be interesting to see which is the piece of software that has an
even lower limit here.
Ludo’.
next prev parent reply other threads:[~2016-01-12 20:55 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
2016-01-12 19:40 ` Taylan Ulrich Bayırlı/Kammer
2016-01-12 20:54 ` Ludovic Courtès [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87k2nea582.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 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.