public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Khem Raj <raj.khem@gmail.com>
To: openembedded-core@lists.openembedded.org
Cc: Khem Raj <raj.khem@gmail.com>
Subject: [PATCH 2/5] gcc: Pin native toolchain to GCC as well
Date: Tue, 21 Oct 2025 22:08:07 -0700	[thread overview]
Message-ID: <20251022050810.1572184-2-raj.khem@gmail.com> (raw)
In-Reply-To: <20251022050810.1572184-1-raj.khem@gmail.com>

GCC is not buildable with clang and when using clang
for native compiler this fails to build native parts

Signed-off-by: Khem Raj <raj.khem@gmail.com>
---
 meta/recipes-devtools/gcc/gcc-15.2.inc | 1 +
 1 file changed, 1 insertion(+)

diff --git a/meta/recipes-devtools/gcc/gcc-15.2.inc b/meta/recipes-devtools/gcc/gcc-15.2.inc
index 575987b6433..d178b254878 100644
--- a/meta/recipes-devtools/gcc/gcc-15.2.inc
+++ b/meta/recipes-devtools/gcc/gcc-15.2.inc
@@ -11,6 +11,7 @@ BINV = "15.2.0"
 FILESEXTRAPATHS =. "${FILE_DIRNAME}/gcc:${FILE_DIRNAME}/gcc/backport:"
 
 TOOLCHAIN = "gcc"
+TOOLCHAIN_NATIVE = "gcc"
 
 DEPENDS =+ "mpfr gmp libmpc zlib zstd flex-native"
 NATIVEDEPS = "mpfr-native gmp-native libmpc-native zlib-native flex-native zstd-native"


  reply	other threads:[~2025-10-22  5:08 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-22  5:08 [PATCH 1/5] libcap: Pass OE defined BUILD_CC and BUILD_LDFLAGS Khem Raj
2025-10-22  5:08 ` Khem Raj [this message]
2025-10-22  5:08 ` [PATCH 3/5] pseudo: Pin native compiler to gcc as well Khem Raj
2025-10-22  5:08 ` [PATCH 4/5] pkgconfig: Always use gcc for native compiler Khem Raj
2025-10-23 12:16   ` [OE-core] " Ross Burton
2025-10-24  2:24     ` Khem Raj
2025-10-22  5:08 ` [PATCH 5/5] elfutils: " Khem Raj
2025-10-23 12:16   ` [OE-core] " Ross Burton
2025-10-24  2:25     ` 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=20251022050810.1572184-2-raj.khem@gmail.com \
    --to=raj.khem@gmail.com \
    --cc=openembedded-core@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox