[sr #111321] config.status generation by configure in dash 0.5.13 fails with ERROR

Zack Weinberg <[email protected]> Tue, 27 Jan 2026 12:11:35 -0500 (EST)

Newsgroups	gmane.comp.sysutils.autoconf.bugs
Message-ID	<[email protected]>

Update of sr #111321 (group autoconf):

                Priority:       5 - Unprioritized => 3 - Release N+1
                  Status:                    None => Need Info

    _______________________________________________________

Follow-up Comment #5:

As far as I can tell, this is 100% a dash bug and autoconf's code is correct
as is.  However, it's not clear to me whether the dash bug ever got fixed.  If
it didn't, or if buggy versions of dash are in wide use, possibly autoconf
ought to do something to work around the bug.

The code that generates config.status is old and fragile and I don't want to
mess with it if I don't absolutely have to.  And it would be extremely
difficult to find out if anyone depends on the "neutralize VPATH" logic that
you highlighted as troublesome.

I do not intend to make any changes here for the upcoming release of Autoconf
2.73 (planned for no later than end of February) but please advise whether
this is still a problem with current versions of dash, and how widely used the
buggy versions are.  It sounds like it's a Cygwin-specific bug, so it would be
especially valuable to know how widely used the buggy versions are *with
Cygwin*.


    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/support/?111321>

_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/

signature.asc (application/pgp-signature, 228 B)