all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Nikita Karetnikov <nikita@karetnikov.org>
Cc: bug-guix@gnu.org
Subject: Re: Bison: testsuite failed
Date: Mon, 28 Jan 2013 17:35:37 +0100	[thread overview]
Message-ID: <87622hb6zq.fsf@gnu.org> (raw)
In-Reply-To: <87ehh5xtn1.fsf_-_@karetnikov.org> (Nikita Karetnikov's message of "Mon, 28 Jan 2013 09:35:23 -0500")

Hi,

Nikita Karetnikov <nikita@karetnikov.org> skribis:

> +/nix/store/6kj7f8kz3h5fizir8l7nrxgras2ns3ww-m4-1.4.16/bin/m4: m4_syscmd subprocess failed
> +/tmp/nix-build-bison-2.6.1.drv-14/bison-2.6.1/data/yacc.c:23: error: b4_cat: cannot write to stdout
> +/tmp/nix-build-bison-2.6.1.drv-14/bison-2.6.1/data/yacc.c:23: the top level

Can you check in the build log of 6kj7f8kz3h5fizir8l7nrxgras2ns3ww-m4-1.4.16
what the line “checking which shell to use for syscmd” says?  (Remember
that build logs are kept in /nix/var/log/nix/drvs or similar, depending
on your localstatedir.  Make sure the value passed to --prefix in that
log matches the one above.)

Here it reads this:

  checking which shell to use for syscmd... /nix/store/ryk1ywzz31kp4biclxq3yq6hpjycalyy-bash-4.2/bin/sh

If it chose /bin/sh, then it means that you built M4 out of the chroot
(or with /bin in the chroot), but now you’re trying to use it within a
chroot.

Ludo’.

  reply	other threads:[~2013-01-28 16:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-26 13:10 'guix-build' returns 'unknown package', Bison's testsuite fails Nikita Karetnikov
2013-01-26 17:21 ` Andreas Enge
2013-01-26 21:03 ` Ludovic Courtès
2013-01-28 14:35   ` Bison: testsuite failed (was: 'guix-build' returns 'unknown package', Bison's testsuite fails) Nikita Karetnikov
2013-01-28 16:35     ` Ludovic Courtès [this message]
2013-01-31  5:18       ` Bison: testsuite failed Nikita Karetnikov

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=87622hb6zq.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=bug-guix@gnu.org \
    --cc=nikita@karetnikov.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 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.