[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: touch gets stuck for named pipes
From: |
Eric Blake |
Subject: |
Re: touch gets stuck for named pipes |
Date: |
Thu, 9 Apr 2009 17:35:32 +0000 (UTC) |
User-agent: |
Loom/3.14 (http://gmane.org/) |
Paolo Bonzini <bonzini <at> gnu.org> writes:
> > This macro is obsolescent, as all current systems have a `utime'
> > that behaves this way. New programs need not use this macro.
>
> I think that then _this_ is the cross-compilation default to be fixed.
>
> Ok?
Fix these nits before applying:
> - ac_cv_func_utime_null=no)])
> + ac_cv_func_utime_null=yes)])
I'd write this as 'ac_cv_func_utime_null="guessing yes"', to make it obvious.
> if test $ac_cv_func_utime_null = yes; then
And this should be made robust to the shell metacharacters above or to garbage
in the user's pre-seed of the cache:
if test "x$ac_cv_func_utime_null" != xno; then
--
Eric Blake
- Re: touch gets stuck for named pipes, Pádraig Brady, 2009/04/09
- Re: touch gets stuck for named pipes, Andreas Schwab, 2009/04/09
- Re: touch gets stuck for named pipes, Bruno Haible, 2009/04/09
- Re: touch gets stuck for named pipes, Paul Eggert, 2009/04/09
- Re: touch gets stuck for named pipes, Paolo Bonzini, 2009/04/09
- Re: touch gets stuck for named pipes,
Eric Blake <=
- Re: touch gets stuck for named pipes, Jim Meyering, 2009/04/09
- Re: touch gets stuck for named pipes, Paolo Bonzini, 2009/04/09
- Re: touch gets stuck for named pipes, Bruno Haible, 2009/04/09
- Re: touch gets stuck for named pipes, Paolo Bonzini, 2009/04/10
- Re: touch gets stuck for named pipes, Jim Meyering, 2009/04/10
- Re: touch gets stuck for named pipes, Bruno Haible, 2009/04/10