From: ludo@gnu.org (Ludovic Courtès)
To: Leo Famulari <leo@famulari.name>
Cc: 22420@debbugs.gnu.org
Subject: bug#22420: Zsh test failure
Date: Fri, 22 Jan 2016 16:04:35 +0100 [thread overview]
Message-ID: <878u3h7j0c.fsf@gnu.org> (raw)
In-Reply-To: <20160121230523.GA17695@jasmine> (Leo Famulari's message of "Thu, 21 Jan 2016 18:05:23 -0500")
Leo Famulari <leo@famulari.name> skribis:
> On Thu, Jan 21, 2016 at 10:02:53PM +0100, Ludovic Courtès wrote:
>> Leo Famulari <leo@famulari.name> skribis:
>>
>> > Zsh fails to build due to a test failure on my system (x86_64).
>> >
>> > The test suite does not report where the failure occurs but I believe it
>> > is in section 'Test/B02typeset.ztst' as a result of patch-shebang
>> > failing to find a binary interpreter for 'Test/ztst.zsh':
>> >
>> > patch-shebang: ./Test/ztst.zsh: warning: no binary for interpreter `zsh' found in $PATH
>> >
>> > I wonder if this means that the file is being interpreted by Bash, or
>> > maybe the 'sh' mode of Bash.
>>
>> It means that the ztst.zsh contains #!/usr/bin/zsh or similar, and when
>> the ‘patch-shebangs’ phase runs, there’s no ‘zsh’ binary in $PATH, so
>> the file is left unpatched with its bogus shebang.
>>
>> That means that attempts to exec ztst.zsh systematically fail.
>>
>> However, I see that Zsh appears to build fine on x86_64-linux as of
>> v0.9.0-1121-gaca738f. What Guix commit are you using?
>
> Currently, feb767b23c7c. I noticed it was failing on core-updates and
> decided to investigate; this commit is on master, not core-updates.
On my x86_64 machine, commit, I’ve just run:
--8<---------------cut here---------------start------------->8---
$ ./pre-inst-env guix build zsh --rounds=3 -K --no-substitutes
[...]
@ build-succeeded /gnu/store/0g7d2ccznwrw010mlfjzzgvycc28vfyx-zsh-5.1.1.drv -
/gnu/store/1wv2flclz8nnkiq1j1s2aphqp9lk68i6-zsh-5.1.1
$ guix hash -r /gnu/store/1wv2flclz8nnkiq1j1s2aphqp9lk68i6-zsh-5.1.1
0s634s0z2b53fj3yd16bydh0qqh1xqjsjnwr59lbkqpd7yprpqma
$ git describe
v0.9.0-1135-gedfa91a
--8<---------------cut here---------------end--------------->8---
What system are you using?
> I have confirmed the failure is in 'Test/B02typeset.ztst'.
Could you post the relevant part of the build log?
TIA,
Ludo’.
next prev parent reply other threads:[~2016-01-22 15:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-21 2:21 bug#22420: Zsh test failure Leo Famulari
2016-01-21 21:02 ` Ludovic Courtès
2016-01-21 23:05 ` Leo Famulari
2016-01-22 15:04 ` Ludovic Courtès [this message]
2016-01-22 16:30 ` Leo Famulari
2016-01-22 17:47 ` Ludovic Courtès
2016-01-22 19:33 ` Leo Famulari
2016-01-22 20:34 ` Ludovic Courtès
2016-01-22 20:38 ` Leo Famulari
2016-01-22 20:43 ` Leo Famulari
2016-01-23 10:51 ` Ludovic Courtès
2016-01-21 22:20 ` Leo Famulari
2016-01-21 23:14 ` Leo Famulari
2018-09-10 0:10 ` Leo Famulari
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=878u3h7j0c.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=22420@debbugs.gnu.org \
--cc=leo@famulari.name \
/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).