AW: AW: AW: AW: AW: AW: AW: new snapshot available: coreutils-7.4.125-eca6

2009-08-20 Thread Voelker, Bernhard
Jim Meyering wrote 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: ... Remember, you did not compile with gcc. Unless someone can suggest an alternative explanation, I'll have to assume this is

Re: AW: AW: AW: AW: AW: AW: AW: new snapshot available: coreutils-7.4.125-eca6

2009-08-20 Thread Jim Meyering
Voelker, Bernhard wrote: Jim Meyering wrote 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: ... Remember, you did not compile with gcc. Unless someone can suggest an alternative explanation,

AW: AW: AW: AW: AW: AW: AW: AW: new snapshot available: coreutils-7.4.125-eca6

2009-08-20 Thread Voelker, Bernhard
Jim Meyering wrote: 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 100644 --- a/src/install.c +++ b/src/install.c @@ -189,7 +189,7 @@ static bool extra_mode (mode_t input) { const mode_t

AW: AW: AW: AW: AW: new snapshot available: coreutils-7.4.125-eca6

2009-08-19 Thread Voelker, Bernhard
Jim Meyering wrote: Please run this command from your build directory cd src { touch a b; mode3=2755; ./ginstall -Cv -m$mode3 a b } and tell us what it prints. somehow, my shell (/bin/ksh) doesn't like the { ... } syntax here: $ cd src { touch a b; mode3=2755; ./ginstall -Cv -m$mode3

AW: AW: AW: AW: AW: new snapshot available: coreutils-7.4.125-eca6

2009-08-19 Thread Voelker, Bernhard
Jim Meyering wrote: sudo env PATH=$PATH NON_ROOT_USERNAME=$USER make -C tests \ TESTS=cp/preserve-gid VERBOSE=yes I think you meant sudo env PATH=$PATH NON_ROOT_USERNAME=$USER make -C tests check \ TESTS=cp/preserve-gid VERBOSE=yes BTW: I'm not sure but shouldn't the tests make

Re: AW: AW: AW: AW: AW: new snapshot available: coreutils-7.4.125-eca6

2009-08-19 Thread Pádraig Brady
Voelker, Bernhard wrote: Jim Meyering wrote: Please run this command from your build directory cd src { touch a b; mode3=2755; ./ginstall -Cv -m$mode3 a b } and tell us what it prints. somehow, my shell (/bin/ksh) doesn't like the { ... } syntax here: $ cd src { touch a b;

Re: AW: AW: AW: AW: AW: new snapshot available: coreutils-7.4.125-eca6

2009-08-19 Thread Philip Rowlands
On Wed, 19 Aug 2009, Voelker, Bernhard wrote: 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 That's not quite valid (POSIX) sh, which requires

Re: AW: AW: AW: AW: AW: new snapshot available: coreutils-7.4.125-eca6

2009-08-19 Thread Jim Meyering
Voelker, Bernhard wrote: Jim Meyering wrote: Please run this command from your build directory cd src { touch a b; mode3=2755; ./ginstall -Cv -m$mode3 a b } and tell us what it prints. somehow, my shell (/bin/ksh) doesn't like the { ... } syntax here: $ cd src { touch a b;

AW: AW: AW: AW: AW: AW: new snapshot available: coreutils-7.4.125-eca6

2009-08-19 Thread Voelker, Bernhard
Jim Meyering wrote: Long-term, best for you would be to install GNU diffutils. done: === GNU coreutils 7.4.127-d2510: tests/test-suite.log === 1 of 1 test failed. .. contents::

Re: AW: AW: AW: AW: AW: new snapshot available: coreutils-7.4.125-eca6

2009-08-19 Thread Jim Meyering
Voelker, Bernhard wrote: Jim Meyering wrote: Please run this command from your build directory cd src { touch a b; mode3=2755; ./ginstall -Cv -m$mode3 a b } and tell us what it prints. somehow, my shell (/bin/ksh) doesn't like the { ... } syntax here: $ cd src { touch a b;

AW: AW: AW: AW: AW: AW: new snapshot available: coreutils-7.4.125-eca6

2009-08-19 Thread Voelker, Bernhard
Jim Meyering wrote: The *second* time that command is run, it appears to print nothing. Do this in src/: ./touch a b; mode3=2755 ./ginstall -Cv -m$mode3 a b ./ginstall -Cv -m$mode3 a b Bingo! If the second invocation of ginstall doesn't print anything, that indicates a

Re: AW: AW: AW: AW: AW: AW: new snapshot available: coreutils-7.4.125-eca6

2009-08-19 Thread Jim Meyering
Voelker, Bernhard wrote: Jim Meyering wrote: The *second* time that command is run, it appears to print nothing. Do this in src/: ./touch a b; mode3=2755 ./ginstall -Cv -m$mode3 a b ./ginstall -Cv -m$mode3 a b Bingo! If the second invocation of ginstall doesn't print