From: Brian Inglis <Brian.Inglis@SystematicSW.ab.ca>
To: Dash <dash@vger.kernel.org>
Cc: Herbert Xu <herbert@gondor.apana.org.au>
Subject: Re: dash 0.5.13 configure config.status truncated running under dash 0.5.13
Date: Sat, 4 Oct 2025 16:47:05 -0600 [thread overview]
Message-ID: <e4361489-5c2b-472e-a812-5e07f41c5774@SystematicSW.ab.ca> (raw)
In-Reply-To: <aOCb3piwcPXpm_NI@gondor.apana.org.au>
On 2025-10-03 22:00, Herbert Xu wrote:
> On Fri, Oct 03, 2025 at 09:19:39PM -0600, Brian Inglis wrote:
>>
>> Likely the autoreconfig with recently updated automake 1.18 using existing
>> /usr/share/autoconf/autoconf/status.m4 stanza:
>
> But it's always been like that. The code is correct as it is. The
> quotes are split across two here-documents and there is nothing wrnog
> with that.
>
> For some reason, when you ran the script with dash 0.5.13, the second
> here-document failed silently, thus creating an unterminated quote.
>
> Please help us find the cause by doing a bisection. As I said my
> suspicion lies with the new memfd code which obviously won't be run
> on Cygwin so there may be an issue with the fallback path.
Nothing to bisect as all commit configs from 0.5.12..0.5.13 fail, because your
repo code does not include all your autoupdated config files checked in, and my
autoreconfig always generates config files that fail at that point.
I will retry 0.5.12 using WANT_AUTOMAKE from 1.17 and WANT_AUTOCONF from 2.69
(not so granular without removing/reinstalling packages) back until it once
again works, and then retry 0.5.13, without and with suggested patches if
required, and if necessary bisect whichever axis/package makes a difference! ;^>
What worries me is that something in the autotools config generation depends on
it being done under Linux, and something in the Cygwin autotools autoreconfig is
messing up cross-compatibility, enough that configs are going to start failing
under Cygwin that work under Linux cross-tools, as Cygwin has been increasingly
dropping our previous Windows interoperability interfaces, they are becoming
increasingly less compatible with new POSIX, GNU, and Windows releases, and
packages are becoming harder to build without hacking more tools!
--
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
next prev parent reply other threads:[~2025-10-04 22:47 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-28 23:05 dash 0.5.13 configure config.status truncated running under dash 0.5.13 Brian Inglis
2025-09-29 5:01 ` Herbert Xu
2025-09-29 9:15 ` Brian.Inglis
2025-09-29 9:37 ` Herbert Xu
2025-09-29 10:29 ` Brian.Inglis
2025-09-29 19:18 ` Brian Inglis
2025-09-30 12:26 ` Herbert Xu
2025-09-30 17:11 ` Brian Inglis
2025-10-01 0:40 ` Herbert Xu
2025-10-02 21:56 ` Brian Inglis
2025-10-03 7:29 ` Herbert Xu
2025-10-04 3:19 ` Brian Inglis
2025-10-04 4:00 ` Herbert Xu
2025-10-04 22:47 ` Brian Inglis [this message]
2025-10-06 2:15 ` Herbert Xu
2025-10-06 3:28 ` Herbert Xu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e4361489-5c2b-472e-a812-5e07f41c5774@SystematicSW.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--cc=dash@vger.kernel.org \
--cc=herbert@gondor.apana.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox