Re: [Bug-gnulib] utime.c patch for the !HAVE_UTIMES_NULL case

[James Youngman]

On Tue, Sep 09, 2003 at 10:41:04PM +0200, Jim Meyering wrote:

> Would you please see what you get in config.cache
> if you run ./configure --cache=config.cache for e.g., any
> coreutils or fileutils release?


Configuring coreutils-5.0 on Dynix 4.4.2...


> 
> If it contains this line,
> 
>   ac_cv_func_utime_null=${ac_cv_func_utime_null=yes}
> 
> then it might be safe finally to remove the old work-around code.


$ grep -i utime config.cache
ac_cv_func_utime_null=${ac_cv_func_utime_null=yes}
ac_cv_header_utime_h=${ac_cv_header_utime_h=yes}
$ uname -a
DYNIX/ptx spock 4.0 V4.4.2 i386


... config.log says :-


configure:27289: checking whether utime accepts a null argument
configure:27320: cc -o conftest -g   conftest.c  >&5
configure:27323: $? = 0
configure:27325: ./conftest
configure:27328: $? = 0
configure:27343: result: yes
configure:27360: checking for utime.h
configure:27365: result: yes


The utime(2) manpage on Dynix 4.4.2 says :-

|          If times is NULL, the access and modification times of the
|          file are set to the current time.  A process must be the
|          owner of the file or have write permission to use utime in
|          this manner.

-- 
James Youngman.
CSSC Bug reporting page:       http://sf.net/tracker/?group_id=8064&atid=108064
GNU Findutils bug reporting page: http://savannah.gnu.org/bugs/?group=findutils