%% Darren Hiebert <[EMAIL PROTECTED]> writes:
dh> I did this and confirmed that cp -p does not preserve the nanosecond
dh> field in the copy.
Bummer! :(
Thanks for working this, though. I'll make a note of it somewhere. I
may have to make a configure option to disable nanosecond timestamp
Paul D. Smith wrote:
> Another thing you can do is write a little test program (you'll have to
> use C as I don't think perl, etc. support this field either) that shows
> the values of st_mtime and st_mtim.tv_nsec...returned by stat(2), then
> run it on a file, and then on a copy created with "cp
%% Darren Hiebert <[EMAIL PROTECTED]> writes:
dh> Paul D. Smith wrote:
>> Hmm. Are you using Irix "cp" to do this? If so, this may be a bug in
>> the Irix "cp" command. Maybe.
>> If you're using another cp, then that's probably your problem...
dh> Good idea. I checked and found, by
Paul D. Smith wrote:
> Hmm. Are you using Irix "cp" to do this? If so, this may be a bug in
> the Irix "cp" command. Maybe.
>
> If you're using another cp, then that's probably your problem...
Good idea. I checked and found, by putting explicit paths to cp in
the makefile that /usr/bin/cp, /
%% Darren Hiebert <[EMAIL PROTECTED]> writes:
dh> I encountered a strange bug when make-3.79 is used on IRIX 6.5,
dh> # Begin Makefile
dh> #DATE=-d "19 Dec 1994"
dh> b: a
dh> cp -p $< $@
dh> a:
dh> touch $(DATE) a
dh> # End Makefile
dh> Note that every time you run make
