[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Problem with texinfo 5.0 package
From: |
Mark H Weaver |
Subject: |
Re: Problem with texinfo 5.0 package |
Date: |
Wed, 20 Feb 2013 13:42:00 -0500 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/24.2 (gnu/linux) |
address@hidden (Ludovic Courtès) writes:
> Mark H Weaver <address@hidden> skribis:
>
>> The built texinfo 5.0 packages contain a few uses of 'perl' that are not
>> pointing to a specific version in /nix/store:
>
> Yes, I know, but since in ‘core-updates’ we’ll change ‘patch-shebang’ to
> handle /usr/bin/env specially, that’ll work well there.
Okay. In the meantime, 'mailutils' fails to build because of this
problem:
--8<---------------cut here---------------start------------->8---
CCLD libmu_scm.la
GEN mailutils.scm
GEN guile-procedures.txt
/nix/store/777jas1fcgc38hmvq6lq1sa9k67f10kl-coreutils-8.20/bin/env: perl: No
such file or directory
WARNING: `makeinfo' is missing on your system. You should only need it if
you modified a `.texi' or `.texinfo' file, or any other file
indirectly affecting the aspect of the manual. The spurious
call might also be the consequence of using a buggy `make' (AIX,
DU, IRIX). You might want to install the `Texinfo' package or
the `GNU make' package. Grab either from any GNU archive site.
make[3]: *** [guile-procedures.txt] Error 1
make[3]: Leaving directory
`/tmp/nix-build-mailutils-2.2.drv-0/mailutils-2.2/libmu_scm'
make[2]: *** [all] Error 2
make[2]: Leaving directory
`/tmp/nix-build-mailutils-2.2.drv-0/mailutils-2.2/libmu_scm'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/tmp/nix-build-mailutils-2.2.drv-0/mailutils-2.2'
make: *** [all] Error 2
phase `build' failed after 88 seconds
builder for `/nix/store/39031b9d3w6j9iwhsnxjfd0lhga1z61g-mailutils-2.2.drv'
failed with exit code 1
error: build failed: build of
`/nix/store/39031b9d3w6j9iwhsnxjfd0lhga1z61g-mailutils-2.2.drv' failed
--8<---------------cut here---------------end--------------->8---
I don't care that much, but that's how the problem came to my attention.
Regards,
Mark