From: Denys Dmytriyenko <denis@denix.org>
To: reatmon@ti.com
Cc: Praneeth Bajjuri <praneeth@ti.com>,
Denys Dmytriyenko <denys@konsulko.com>,
meta-ti@lists.yoctoproject.org
Subject: Re: [meta-ti][master][PATCH] k3r5: Fix mc:k3r5:libgcc build error
Date: Thu, 15 Oct 2026 19:51:14 -0400 [thread overview]
Message-ID: <20261015235114.GW4190@denix.org> (raw)
In-Reply-To: <20261005130234.1532926-1-reatmon@ti.com>
On Mon, Oct 05, 2026 at 08:02:34AM -0500, Ryan Eatmon via lists.yoctoproject.org wrote:
> A recent change in oe-core [1] is causing a build error in the
> mc:k3r5:libgcc do_configure step. We need to track down why this change
> causes this error, but in the meantime we need to get builds working
> again. Add the removed line from [1] to the multiconfig/k3r5.conf file.
>
> [1] https://git.openembedded.org/openembedded-core/commit/?id=020d5f018616bc48eae3a23d5498dec3c78a1386
We need to revert this, as the proper fix has been in upstream for a while:
https://git.openembedded.org/openembedded-core/commit/?id=2f5c2b696bcd8e02eac6b06bb0cdace0fa86eb44
> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
> ---
> meta-ti-bsp/conf/multiconfig/k3r5.conf | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/meta-ti-bsp/conf/multiconfig/k3r5.conf b/meta-ti-bsp/conf/multiconfig/k3r5.conf
> index 936bce2f..fd871dca 100644
> --- a/meta-ti-bsp/conf/multiconfig/k3r5.conf
> +++ b/meta-ti-bsp/conf/multiconfig/k3r5.conf
> @@ -8,3 +8,5 @@ TI_TMPDIR_APPEND ?= "-k3r5"
> TMPDIR:append = "${TI_TMPDIR_APPEND}"
>
> SDKPKGSUFFIX = "k3r5-nativesdk"
> +
> +EXTRA_OECONF:pn-gcc-cross-${TARGET_ARCH}:append = " --without-headers"
> --
> 2.43.0
prev parent reply other threads:[~2026-10-15 23:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-05 13:02 [meta-ti][master][PATCH] k3r5: Fix mc:k3r5:libgcc build error Ryan Eatmon
2026-10-05 13:23 ` PRC Automation
2026-10-15 23:51 ` Denys Dmytriyenko [this message]
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=20261015235114.GW4190@denix.org \
--to=denis@denix.org \
--cc=denys@konsulko.com \
--cc=meta-ti@lists.yoctoproject.org \
--cc=praneeth@ti.com \
--cc=reatmon@ti.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 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.