Package: coreutils
Version: 5.93-5
Severity: important
Hi,
coreutils fails to build on hurd-i386 due to the following error:
Making all in man
make[3]: Entering directory
`/build/buildd/coreutils-5.93/build-tree/coreutils-5.93/man'
Updating man page basename.1
Updating man page cat.1
Updating man page chgrp.1
[...]
Updating man page chcon.1
help2man: can't get `--help' info from chcon.td/chcon
make[3]: *** [chcon.1] Error 127
The full build log is at
http://experimental.ftbfs.de/fetch.php?&pkg=coreutils&ver=5.93-5&arch=hurd-i386&stamp=1135013024&file=log&as=raw
(chcon is added by the selinux patch)
The superficial reason for the failure is that make thinks chcon.1 (and
runcon.1 as well) need updating, possibly to time stamp skews during
patching as 55_coreutils-selinux.patch first includes chcon.1 and then
chcon.x, on which the manpage depends.
I tested that the following patch makes the build go fine:
--- debian/rules.orig 2005-12-20 16:03:43.000000000 +0100
+++ debian/rules 2005-12-20 14:19:06.000000000 +0100
@@ -53,6 +53,7 @@
configure-stamp: $(patched)
dh_testdir
+ touch $(BUILD_TREE)/man/{ch,run}con.1
cd $(BUILD_TREE) && autoreconf
cd $(BUILD_TREE) && CFLAGS=$(CFLAGS) \
However, I am not quite sure why it succeeds to build on kfreebsd (their
build log is on experimental.ftbfs.de as well), maybe it is due to
different timestamp handling.
I also do not know why the manpage is being updated at all, when the
binary is not built, and poking at the Makefile.ams for quite a bit did
not help much, either. Interestingly, when I comment out the mentions
of uptime in configure.ac (which is sort of in the same boat as chcon,
as it only gets built depending on what ./configure decides), I get the
same error:
[...]
Updating man page uptime.1
help2man: can't get `--help' info from uptime.td/uptime
make[3]: *** [uptime.1] Error 127
so maybe this is even an upstream problem (though I'd be surprised
nobody else ran into it, unless they changed behaviour recently)
cheers,
Michael
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
