Eric Blake [EMAIL PROTECTED] writes:
POSIX requires that a group name that is completely numeric (yes,
that is a portable group name) takes preference over a group number.
That's awkward. The obvious workaround is to keep prepending 0s until
you come up with a name that's not used. But I'd
Eric Blake [EMAIL PROTECTED] wrote:
...
Also, I noticed some other tests in the suite that were sensitive to group
names. At the moment, I'm not on the machine where I noticed all the
problems, but off the top of my head, I remember that at least
chown/separator was calling `id' directly
Eric Blake [EMAIL PROTECTED] writes:
http://lists.gnu.org/archive/html/bug-coreutils/2005-01/msg00063.html
Conceivably this problem could occur on Unix too. I installed this
patch to work around it (on Unix, anyway) by using group numbers
rather than names.
2005-01-17 Paul Eggert [EMAIL
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[cross-posted to cygwin and automake lists]
I'm not sure if the bug below is with cygwin's mods to make, in automake
for using non-portable Makefile constructs, or in both.
According to Jim Meyering on 1/12/2005 9:45 AM:
If you run `make -k check',
Eric Blake wrote:
Actually, the tarball includes AM_GNU_GETTEXT_VERSION(0.13.1), the latest
version of autopoint is 0.14.1, but some of the gettext .m4 files are
newer than the 0.14.1 version. To get a good reconf, I had to use
`AUTOPOINT=true autoreconf -fiv', skipping autopoint, because
According to Jim Meyering on 1/11/2005 10:09 AM:
Once I manually patched the corresponding Makefile.ins, I don't get very
far into the testsuite (1 of 5 failed under tests/chgrp), see
coreutils.check3. I haven't yet had time to figure out how to get any
further.
As for tests/chgrp/basic,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Jim Meyering on 1/12/2005 6:43 AM:
autoreconf should work fine.
Why are you using -f (--force)? Or -i (--install) for that matter?
Using autoreconf (without -f) should work fine.
Habit, I guess. You were correct that it worked
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The 5.3.0 testsuite does not even get a chance to run on cygwin, because
the check-README target of src/Makefile does not take into account
${EXEEXT}. See the attached coreutils.check, and my proposed patch below.
However, I didn't have automake
