From: Herbert Xu <herbert@gondor.apana.org.au>
To: Brian Inglis <Brian.Inglis@systematicsw.ab.ca>
Cc: Dash <dash@vger.kernel.org>
Subject: Re: dash 0.5.13 configure config.status truncated running under dash 0.5.13
Date: Sat, 4 Oct 2025 12:00:30 +0800 [thread overview]
Message-ID: <aOCb3piwcPXpm_NI@gondor.apana.org.au> (raw)
In-Reply-To: <e16023a7-bca3-4537-a8f8-f0e952c70e1b@systematicsw.ab.ca>
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.
Thanks,
--
Email: Herbert Xu <herbert@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
next prev parent reply other threads:[~2025-10-04 4:00 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 [this message]
2025-10-04 22:47 ` Brian Inglis
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=aOCb3piwcPXpm_NI@gondor.apana.org.au \
--to=herbert@gondor.apana.org.au \
--cc=Brian.Inglis@systematicsw.ab.ca \
--cc=dash@vger.kernel.org \
/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