Elias Pipping wrote: > I've attached the help-version.log Thanks for doing all of this testing. Here is the failure reported in the help-version.log that you sent.
> + prog=ginstall > + eval 'args=$ginstall_args' > ++ args='in-63884 in2-63884' > + /Users/pipping/coreutils-6.9.90/src/ginstall in-63884 in2-63884 > /Users/pipping/coreutils-6.9.90/src/ginstall: setting permissions for > `in2-63884': Invalid argument > + echo FAIL: ginstall > FAIL: ginstall > + fail=1 > + rm -rf in-63884 in2-63884 out-63884 dir-63884 The test is creating a file in-$$ (in-63884 in the above) and then running ginstall (the just built install executable is always named ginstall) and this is failing. Can you try this: echo > foo ./src/ginstall foo bar I expect that to fail for you because the test is failing that same operation. If so then it would be necessary to debug why. I am not familiar with your system type but if it is possible to trace system calls that would be most useful. On my system I would use strace to do this. strace ./src/ginstall foo bar Does your system have something similar? I expect to see that one of the acl system calls is failing. Could you try this and send the output back to the mailing list? (I don't think it should be too large.) > PS: sorry about the double-post -- probably should have killed my smtp > client instead of mutt when i noticed i was sending out a 2.2MB file :/ At 2M plus these files are quite large. Even the last help-version.log at 121K was quite large. In the future would it be possible for you to gzip them before attaching them? That would reduce the size of the mail that gets sent to everyone quite substantially. Thanks. Thanks again for doing this testing. Bob _______________________________________________ Bug-coreutils mailing list [email protected] http://lists.gnu.org/mailman/listinfo/bug-coreutils
