Re: dash 0.5.13 configure config.status truncated running under dash 0.5.13

On 2025-09-29 03:37, Herbert Xu wrote:
> [email protected] wrote:
>>
>> Applied and rebuilt, getting the same failure with identical ERROR messages and
>> symptoms, after building okay with previous dash == sh, then rerunning with
>> latest dash == sh.
>>
>> Do the previously highlighted configure script last two config.status generation
>> stanzas seem to have issues, or is that as intended?
>>
>> It appears that the following _ACEOF\ncat >>$CONFIG_STATUS ... might be
>> misplaced, as it is immediately followed by a list of sed commands.
> 
> It looks identical to the configure script that I get from running
> autoconf, and my copy works just fine, even with the buggy dash 0.5.13.
> 
>> These stanzas come from /usr/share/autoconf{,2.7}/autoconf/status.m4
>> included by /usr/share/autoconf{,2.7}/autoconf/autoconf.m4 frozen in
>> /usr/share/autoconf{,2.7}/autoconf/autoconf.m4f.
>>
>> Or is this an issue that should be raised with the autoconf/autotools team?
> 
> Based on the fact we just found two bugs in 0.5.13 that both broke
> autoconf, it's probably a dash bug :)
> 
> I just checked your original email and your configure script is
> identical to mine.
> 
> Can you please run configure with set -x and send me the result?
Complete Cygwin build run with set -vx attached.

-- 
Take care. Thanks, Brian Inglis              Calgary, Alberta, Canada

La perfection est atteinte                   Perfection is achieved
non pas lorsqu'il n'y a plus rien à ajouter  not when there is no more to add
mais lorsqu'il n'y a plus rien à retrancher  but when there is no more to cut
                                 -- Antoine de Saint-Exupéry