Something odd happened with generated man/Makefile.in file, it is no longer going to build and install manpages because all corresponding code is absent in the new version: -all-am: Makefile $(MANS)
Hi Dmitry, Thanks for pointing that out. It may be due to the fact that I generated Makefile.in using automake built from the very latest version in the upstream automake.git repository. I've Cc'd bu
In my case, automake version is 1.10.1 (latest stable release) also results to wrong man/Makefile.in file. Thanks, this workaround helps to build manpages. Installing them using "make install" is sti
Ahh, now I see. This coreutils change removed the final literal from the definition of dist_man_MANS in man/Makefile.am, which seems like it should be fine: http://git.sv.gnu.org/gitweb/?p=coreutils.
Hi Jim, * Jim Meyering wrote on Thu, Mar 20, 2008 at 06:49:35PM CET: You can instead also just s/dist_man_MANS/dist_man1_MANS/ because all automake needs to know is the section. Cheers, Ralf
I expect to make a new release of coreutils within a week or two. If you've been sitting on anything resembling a bug report, please send it in sooner rather than later. Here's a new snapshot: coreut
i get 4 test failures on x86_64/linux running as root: FAIL: no-give-up.log FAIL: fail-2eperm.log FAIL: special-bits.log FAIL: now-owned-by-other.log verbose logs attached -mike Attachment: signature
... Hi Mike, Thanks for the quick feedback! You probably know, but just in case, ... realize that running such tests as root is risky, especially on a system with potentially hostile users. I can rep
I'm planning to make a release soon, maybe in the next week, so here's a snapshot of the current state: coreutils snapshot: http://meyering.net/cu/coreutils-ss.tar.gz 8.8 MB http://meyering.net/cu/co
... Thanks for the quick feedback! That's odd. But it's easy to work around. Patch below, but before I apply it for good, I'd like to understand why it is happening. What type of system are you using
Whoops. Missing backslashes. Here's a patch that actually has a chance of working ;-) diff --git a/tests/mkdir/selinux b/tests/mkdir/selinux index c0fc201..f8aeace 100755 -- a/tests/mkdir/selinux +++
I got an error in `make check' in this snapshot: ,-- `/usr/local/src/coreutils-6.10.156-0ec48/tests/mkdir' `/usr/local/src/coreutils-6.10.156-0ec48/tests/mkdir' `/usr/local/src/coreutils-6.10.156-0ec
Debian GNU/Linux sid, i386 architecture. Linux 2.6.24.4, self-compiled. 2.0.59, according to `dpkg -l libselinux1'. Here it comes: execve("./mkdir", ["./mkdir", "-Z", "jdkdjkdj", "foo"], [/* 32 vars
I expect to make a release as soon as autoconf-2.62 is released. As such, this snapshot was bootstrapped with the very latest autoconf and automake (and as usual, up-to-the-minute gnulib). There has
It feels like we're converging. There have been some relevant changes in gnulib, too. Here's hoping the next announcement will be for coreutils-7.0. coreutils snapshot: http://meyering.net/cu/coreuti
I'd forgotten to pull onto master the remove.c fix for BeOS/Haiku, but more importantly, this snapshot is bootstrapped with the just-tagged autoconf-2.62 (soon to appear on ftp.gnu.org): coreutils sn