From: "Mathieu Dubois-Briand" <mathieu.dubois-briand@bootlin.com>
To: <raj.khem@gmail.com>, <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH] autoconf: Raise line length limit for sed/awk
Date: Wed, 03 Dec 2025 08:23:22 +0100 [thread overview]
Message-ID: <DEOEGKYGPYRE.2VTCS4TEKVW7C@bootlin.com> (raw)
In-Reply-To: <20251127164443.2285753-1-raj.khem@gmail.com>
On Thu Nov 27, 2025 at 5:44 PM CET, Khem Raj via lists.openembedded.org wrote:
> Latest autoconf is splitting long cmd lines in config.status
> it generates using sed/awk to have compatibility with
> platform like HPUX,Solaris,AIX which is understandable given
> autotools try to achieve wider portability, however, this does
> mean that in OE builds we might get these newlines added in
> places dividing commands including buildpaths in them and the
> methods deployed to scrub them from output artifacts will fail
> since the string is now on two lines resulting in build QA to
> pass but the strings do sneak in affecting reproducibility
> one such example is e2tools recipe in meta-filesystems and there
> perhaps are more
>
> Signed-off-by: Khem Raj <raj.khem@gmail.com>
> ---
Hi Khem,
Thanks for your patch.
I've had some issues on the autobuilder for a few days, and it looks
like it was triggered by this patch. While there was no specific error,
the -tc build jobs had been running for several days and never ending.
One example:
https://autobuilder.yoctoproject.org/valkyrie/?#/builders/66/builds/2740
I've had a look on the worker: it looks like the host nfs server, used
to share files with the tests running in qemu, had been failing:
pokybui+ 4115014 1.1 0.0 0 0 ? Z 14:23 4:32 [unfsd] <defunct>
I clearly can't see how this can be linked to this patch, yet, git
bisect points to it, and after its removal I don't have the issue
anymore.
So I'm not sure there is anything you can do, but I will accept any clue
about what might going on here.
Thanks,
Mathieu
--
Mathieu Dubois-Briand, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2025-12-03 7:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-27 16:44 [PATCH] autoconf: Raise line length limit for sed/awk Khem Raj
2025-11-27 17:17 ` [OE-core] " Yoann Congal
2025-12-03 7:23 ` Mathieu Dubois-Briand [this message]
2025-12-08 16:24 ` Yoann Congal
-- strict thread matches above, loose matches on Subject: below --
2026-04-03 2:43 Khem Raj
2026-04-03 8:53 ` [OE-core] " Richard Purdie
2026-04-03 21:31 ` Khem Raj
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=DEOEGKYGPYRE.2VTCS4TEKVW7C@bootlin.com \
--to=mathieu.dubois-briand@bootlin.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.com \
/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