From: Francesco Dolcini <francesco@dolcini.it>
To: Ilias Apalodimas <ilias.apalodimas@linaro.org>
Cc: Tom Rini <trini@konsulko.com>, Fabio Estevam <festevam@gmail.com>,
Michal Simek <michal.simek@amd.com>,
sughosh.ganu@linaro.org,
Christophe Leroy <christophe.leroy@csgroup.eu>,
Stefano Babic <sbabic@nabladev.com>,
"NXP i.MX U-Boot Team" <uboot-imx@nxp.com>,
Marek Vasut <marex@denx.de>,
Olaf Mandel <o.mandel@menlosystems.com>,
Minkyu Kang <mk7.kang@samsung.com>,
Jaehoon Chung <jh80.chung@samsung.com>,
Francesco Dolcini <francesco.dolcini@toradex.com>,
Simon Glass <sjg@chromium.org>, Peng Fan <peng.fan@nxp.com>,
Yannic Moog <y.moog@phytec.de>, Wadim Egorov <w.egorov@phytec.de>,
Christoph Stoidner <c.stoidner@phytec.de>,
Prasad Kummari <prasad.kummari@amd.com>,
Jiaxun Yang <jiaxun.yang@flygoat.com>,
Paul Barker <paul.barker.ct@bp.renesas.com>,
Rasmus Villemoes <rasmus.villemoes@prevas.dk>,
Jonathan Humphreys <j-humphreys@ti.com>,
Sam Edwards <cfsworks@gmail.com>,
Andrejs Cainikovs <andrejs.cainikovs@toradex.com>,
u-boot@lists.denx.de
Subject: Re: [PATCH v2 2/2] kbuild: Bump the build system to 5.1
Date: Fri, 11 Jul 2025 07:27:05 +0200 [thread overview]
Message-ID: <20250711052705.GA5353@francesco-nb> (raw)
In-Reply-To: <CAC_iWj+B2p-xfcdJS14LZAAjxGsxXeuBbm0CxJf_DL4E-0ytFA@mail.gmail.com>
Hi
On Fri, Jul 11, 2025 at 08:15:25AM +0300, Ilias Apalodimas wrote:
> I can't reproduce this on my Ubuntu and Debian boxes.
> Can you paste your Ubuntu, make & gcc versions?
Our CI is also failing builds.
We build within OE master, no other changes on our side.
TI platforms are affected in a similar way
| make[1]: *** arch/arm/mach-k3/: Is a directory. Stop.
From a quick check, with arm64, everything is fine.
Francesco
next prev parent reply other threads:[~2025-07-11 5:27 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-27 18:57 [PATCH v2 1/2] kbuild: Update Makefile.extrawarn to 5.1 Ilias Apalodimas
2025-06-27 18:57 ` [PATCH v2 2/2] kbuild: Bump the build system " Ilias Apalodimas
2025-07-10 14:16 ` Fabio Estevam
2025-07-10 14:27 ` Ilias Apalodimas
2025-07-10 14:34 ` Fabio Estevam
2025-07-10 14:58 ` Michal Simek
2025-07-10 15:01 ` Tom Rini
2025-07-11 5:15 ` Ilias Apalodimas
2025-07-11 5:27 ` Francesco Dolcini [this message]
2025-07-11 6:17 ` Ilias Apalodimas
2025-07-11 7:02 ` Francesco Dolcini
2025-07-11 6:50 ` Michal Simek
2025-07-11 6:52 ` Yao Zi
2025-07-11 7:09 ` Ilias Apalodimas
2025-07-11 12:11 ` Fabio Estevam
2025-07-17 17:03 ` Sudeep Holla
2025-07-17 17:41 ` Tom Rini
2025-07-18 8:30 ` Sudeep Holla
2025-07-21 7:26 ` Ilias Apalodimas
2025-07-08 21:35 ` [PATCH v2 1/2] kbuild: Update Makefile.extrawarn " Tom Rini
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=20250711052705.GA5353@francesco-nb \
--to=francesco@dolcini.it \
--cc=andrejs.cainikovs@toradex.com \
--cc=c.stoidner@phytec.de \
--cc=cfsworks@gmail.com \
--cc=christophe.leroy@csgroup.eu \
--cc=festevam@gmail.com \
--cc=francesco.dolcini@toradex.com \
--cc=ilias.apalodimas@linaro.org \
--cc=j-humphreys@ti.com \
--cc=jh80.chung@samsung.com \
--cc=jiaxun.yang@flygoat.com \
--cc=marex@denx.de \
--cc=michal.simek@amd.com \
--cc=mk7.kang@samsung.com \
--cc=o.mandel@menlosystems.com \
--cc=paul.barker.ct@bp.renesas.com \
--cc=peng.fan@nxp.com \
--cc=prasad.kummari@amd.com \
--cc=rasmus.villemoes@prevas.dk \
--cc=sbabic@nabladev.com \
--cc=sjg@chromium.org \
--cc=sughosh.ganu@linaro.org \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--cc=uboot-imx@nxp.com \
--cc=w.egorov@phytec.de \
--cc=y.moog@phytec.de \
/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.