[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: touch gets stuck for named pipes
From: |
Jim Meyering |
Subject: |
Re: touch gets stuck for named pipes |
Date: |
Thu, 09 Apr 2009 20:25:41 +0200 |
Eric Blake wrote:
> 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.
It would be a tad more backwards-compatible to stick with "yes".
Consider a configure.ac that does this,
AC_FUNC_UTIME_NULL
if test $ac_cv_func_utime_null = yes; then
...
fi
That would malfunction with the "guessing yes" value.
- 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, 2009/04/09
- Re: touch gets stuck for named pipes,
Jim Meyering <=
- 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