X-Authentication-Warning:	delorie.com: mailnull set sender to djgpp-workers-bounces using -f
Date:	Mon, 25 Feb 2002 07:55:28 +0200 (IST)
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender:	eliz AT is
To:	Charles Sandmann <sandmann AT clio DOT rice DOT edu>
cc:	djgpp-workers AT delorie DOT com
Subject:	Re: cp complains about timestamps of directories
In-Reply-To:	<10202242139.AA20004@clio.rice.edu>
Message-ID:	<Pine.SUN.3.91.1020225074841.5689A-100000@is>
MIME-Version:	1.0
Reply-To:	djgpp-workers AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	djgpp-workers AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

On Sun, 24 Feb 2002, Charles Sandmann wrote:

> > I understand why the error message is printed, but the DJGPP port
> > shouldn't print it, since we know DOS/Windows doesn't let us change
> > the time stamps of directories, so this failure is normal behavior,
> > not something the user should be bothered with.
> 
> Is this check in the library or in the application?

If you are asking where does `cp' check if setting the time stamp of a 
directory failed, then it's in the application code.  The errno value 
(the ubiquitous EACESS) comes from a library function, of course, utime 
IIRC).

> > My cp.exe is dated June 4, 2001, and its size is 128000 bytes, in case
> > this is important.
> 
> I don't have this cp.exe - I have an (old) cvs/w2k testing one and the
> one I updated in the refresh.

What does "cp --version" say, and what is the dat of your binary?

It's possible that my binary is not the latest one, so perhaps this 
problem was fixed larter.

> I copied my djgpp tree as the test.
> 
> I get:
> cp: preserving times for test/djgpp: Permission denied (EACCES)
> 
> after the last file in djgpp/bin is copied - with both images.  I don't see
> this message for any other directories in the tree, just this one (which
> is the first one).  So, I also see this message, but only for the first
> directory copied, and after the contents of the directory were copied.

It kinda figures: cp was fixed long time ago to skip the warning in the 
DJGPP port, so it mostly should be silent about these failures.  I'm 
guessing that some new code branch was introduced in the new version of 
Fileutils, and the warning there isn't conditioned on it not being run on 
DOS/Windows.

> I also observed random failures when setting the file dates.  Using both
> the cvs version and 2.03 refresh I got some EACCES errors (1 or 2 for each
> tree also in the bin directory).  File copied fine, but the date was not
> set.  This testing was under Win95 (don't have access to other boxes now).

This should be investigated, IMHO.  Setting file dates should work.  Is 
it truly random, i.e. each time a different file, or are some specific 
files involved?

- Raw text -