From: Vyacheslav Yurkov <uvv.mail@gmail.com>
To: Marek Vasut <marek.vasut@mailbox.org>,
openembedded-devel@lists.openembedded.org
Cc: Alexander Kanavin <alex@linutronix.de>,
Ankur Tyagi <ankur.tyagi85@gmail.com>,
Khem Raj <khem.raj@oss.qualcomm.com>
Subject: Re: [meta-filesystems][PATCH] overlayfs-tools: Inhibit tests on configure
Date: Fri, 23 Oct 2026 08:24:22 +0200 [thread overview]
Message-ID: <282c4aa2-503e-4d5a-bf52-2434667ccfc6@gmail.com> (raw)
In-Reply-To: <0eba48ad-5c1f-4041-8f8b-c261f18d29d6@mailbox.org>
On 22.10.2026 17:13, Marek Vasut wrote:
> Can you try this:
>
> "
> # conf/local.conf
> MACHINE ??= "qemux86-64"
> USER_CLASSES ?= "buildstats"
> PATCHRESOLVE = "noop"
> BB_DISKMON_DIRS ??= "\
> STOPTASKS,${TMPDIR},1G,100K \
> STOPTASKS,${DL_DIR},1G,100K \
> STOPTASKS,${SSTATE_DIR},1G,100K \
> STOPTASKS,/tmp,100M,100K \
> HALT,${TMPDIR},100M,1K \
> HALT,${DL_DIR},100M,1K \
> HALT,${SSTATE_DIR},100M,1K \
> HALT,/tmp,10M,1K"
>
> CONF_VERSION = "2"
> "
>
> "
> # conf/bblayers.conf
> LCONF_VERSION = "7"
> BBPATH = "${TOPDIR}"
> BBFILES ?= ""
> BBLAYERS ?= " \
> /oe-core___wrynose-6.0/meta \
> /meta-openembedded___wrynose-6.0/meta-oe/ \
> /meta-openembedded___wrynose-6.0/meta-python/ \
> /meta-openembedded___wrynose-6.0/meta-networking/ \
> /meta-openembedded___wrynose-6.0/meta-filesystems/ \
> "
> "
>
> $ . oe-init-build-env /path/to/builddir
> $ MACHINE="qemux86-64" DISTRO="nodistro" bitbake -c configure
> overlayfs-tools
>
> ?
>
> Also, please run 'which sudo' and check whether sudo isn't actually
> installed on your build machine (it is NOT installed on mine, because
> it is a minimal container)
Thanks, I guess the container without a `sudo` is the reason (somehow I
always had it in mines).
If you are OK with this fix
https://github.com/kmxz/overlayfs-tools/pull/34 , we can bump a revision
after that.
Slava
next prev parent reply other threads:[~2026-10-23 6:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-21 13:53 [meta-filesystems][PATCH] overlayfs-tools: Inhibit tests on configure Marek Vasut
2026-10-21 15:09 ` Vyacheslav Yurkov
2026-10-21 16:27 ` Marek Vasut
2026-10-22 12:24 ` Vyacheslav Yurkov
2026-10-22 15:13 ` Marek Vasut
2026-10-23 6:24 ` Vyacheslav Yurkov [this message]
2026-10-23 7:05 ` [oe] " Khem Raj
[not found] ` <47f17a91-d4bf-4259-8995-531483dd8095@gmail.com>
2026-10-23 7:39 ` Marek Vasut
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=282c4aa2-503e-4d5a-bf52-2434667ccfc6@gmail.com \
--to=uvv.mail@gmail.com \
--cc=alex@linutronix.de \
--cc=ankur.tyagi85@gmail.com \
--cc=khem.raj@oss.qualcomm.com \
--cc=marek.vasut@mailbox.org \
--cc=openembedded-devel@lists.openembedded.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.