[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Bison: testsuite failed
From: |
Ludovic Courtès |
Subject: |
Re: Bison: testsuite failed |
Date: |
Mon, 28 Jan 2013 17:35:37 +0100 |
User-agent: |
Gnus/5.130005 (Ma Gnus v0.5) Emacs/24.2 (gnu/linux) |
Hi,
Nikita Karetnikov <address@hidden> 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’.