somehow, my shell (/bin/ksh) doesn't like the { ... } syntax here: $ cd src && { touch a b; mode3=2755; ./ginstall -Cv -m$mode3 a b } it waits for the command to be continued ... I can't see why Tha
Thanks. That's good, in that it produces the expected output. But it doesn't help me see why that test is failing for you. Long-term, best for you would be to install GNU diffutils. If you can do tha
Thanks. Almost there. Your test output when using GNU diff gave a clue. The *second* time that command is run, it appears to print nothing. Do this in src/: ./touch a b; mode3=2755 ./ginstall -Cv -m$
Bingo! no gdb here, sorry ;-( here u are - hope that helps on this long search (thanx for your patience BTW): execve("ginstall", 0xFFBFFB84, 0xFFBFFB9C) argc = 5 resolvepath("/usr/lib/ld.so.1", "/lib
... I'm beginning to think there's a fundamental problem with your system. Here's the comparable part of truss output on a working Solaris 10 system: getppriv(PRIV_EFFECTIVE, {00040003880000000000000
Have any of you found anything worth addressing for 7.5? Otherwise, I'll make the release tomorrow. Here's a final snapshot: coreutils snapshot: http://meyering.net/cu/coreutils-ss.tar.gz 9.5 MB http
system: ... I got one last input for this case: CC ginstall-install.o "install.c", line 191: warning: initializer does not fit or is out of range: -61952 Code: 187 /* Return true for mode with non-pe
Thanks. Those details have helped me see the light. I suspect this patch works around your compiler's inadequate "bool" support: diff --git a/src/install.c b/src/install.c index 73b3981..19efb1d 1006
necessary. */ perfect (output still incl. my fprintf): $ ./ginstall -Cv -m$mode3 a b extra_mode(1517) -> 1024 ./ginstall: the --compare (-C) option is ignored when you specify a mode with non-permiss
all non-root tests have successfully now, but one of the root-tests failed: == GNU coreutils 7.4.127-d2510: tests/test-suite.log == 1 of 1 test failed. .. contents:: :depth: 2 FAIL: cp/preserve-gid (
Thanks for investigating that! It's good to know it's a weakness in the test script, and not a problem with cp. After coreutils-7.5 someone will adjust the script to skip that part if the just-built
If anyone knows of bug-related fixes that aren't yet applied, please speak up. I'm thinking of making a snapshot today, leading to a bug-fix release, coreutils-7.6, next week. Eric, I'm open to the i
It would be nice to get Ondřej's fix for copy xattrs from readonly files. I might be able to look at that in a couple of hours. There's also this one that popped up in our recent favorite: tail-2/wa
According to Jim Meyering on 9/4/2009 10:17 AM: At least one more adaptation needed - I'm changing link-follow.m4 to define LINK_FOLLOWS_SYMLINKS as a tri-state (1 yes (losing system), 0 no (good, li
Thanks! Right. I suppose it'd be best to add some distcheck-time code to prevent this sort of regression: configure as if inotify were not available, and ensure the tail-related tests still pass. Or
According to Jim Meyering on 9/4/2009 12:11 PM: We've done undocumented three-hyphen options before, and I think it works well. It can't interfere with option abbreviation, which is a plus, and anyth