Ralf Wildenhues <[EMAIL PROTECTED]> writes:

> Hello Paul, Alexandre,
>
> * Paul Eggert wrote on Tue, Jun 20, 2006 at 10:43:04PM CEST:
>> OK, but the new test he added (marked '+' below):
>> 
>>    { ac_out=`sed -n '/\${datarootdir}/p' "$tmp/out"`; test -n "$ac_out"; } &&
>> +  { ac_out=`sed -n '/^[[    ]]*datarootdir[[        ]]*:*=/p' "$tmp/out"`; 
>> test -z "$ac_out"; } &&
>> 
>> looks pretty portable to me.  If it breaks, then I'd expect the
>> existing sed-based test to break too.
>
> Well.  This change causes us to issue a warning for an empty .in file.
> So, apologies for rejecting it for the wrong reason.  ;-)

The change only adds an extra condition that must be fulfilled, so all
it can do is silence the existing warning, I don't see how it can
possibly cause an extra warning (and I certainly don't see one here
with an empty .in file). Or do you mean you get a warning from sed or
something like this?

-- 
Alexandre Julliard
[EMAIL PROTECTED]


Reply via email to