Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Alexandre Belloni <alexandre.belloni@bootlin.com>
To: Ross Burton <ross.burton@arm.com>
Cc: "pyih.soft@gmail.com" <pyih.soft@gmail.com>,
	"openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH] classes: make TOOLCHAIN more permissive for kernel
Date: Thu, 1 Dec 2022 16:14:59 +0100	[thread overview]
Message-ID: <Y4jE8wXWKjCvQegF@mail.local> (raw)
In-Reply-To: <7EBEF3C3-A9F1-475E-A90E-DA21E6E5895C@arm.com>

On 01/12/2022 13:27:13+0000, Ross Burton wrote:
> 
> 
> > On 1 Dec 2022, at 12:14, Alexandre Belloni <alexandre.belloni@bootlin.com> wrote:
> > 
> > On 01/12/2022 11:25:29+0000, Ross Burton wrote:
> >> On 30 Nov 2022, at 16:21, Alexey Smirnov via lists.openembedded.org <pyih.soft=gmail.com@lists.openembedded.org> wrote:
> >>> -TOOLCHAIN = "gcc"
> >>> +TOOLCHAIN ?= “gcc"
> >> 
> >> If the kernel is buildable with clang then the TOOLCHAIN statement should just be removed.
> >> 
> > 
> > It is buildable but the generated binary is not necessarily bootable,
> > depending on the architecture
> 
> So maybe the kernel class should just set TOOLCHAIN for those architectures where it is known to not work, leaving it unset (and thus overridable with a global assignment) for everything else?
> 

I'm not sure this is doable because oe-core doesn't have support for all
the architectures that are supported by the kernel and so it would be
better to list the ones that are actually supporting clang. Even then we
will probably end up with people wanting to build with clang just to
ensure there are no new warnings even if the kernel they are going to
use is built with gcc (I've already been asked).

> Ross

> 
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#174059): https://lists.openembedded.org/g/openembedded-core/message/174059
> Mute This Topic: https://lists.openembedded.org/mt/95361461/3617179
> Group Owner: openembedded-core+owner@lists.openembedded.org
> Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [alexandre.belloni@bootlin.com]
> -=-=-=-=-=-=-=-=-=-=-=-
> 


-- 
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com


      reply	other threads:[~2022-12-01 15:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-30 16:21 [PATCH] classes: make TOOLCHAIN more permissive for kernel Alexey Smirnov
2022-12-01 11:25 ` [OE-core] " Ross Burton
2022-12-01 12:14   ` Alexandre Belloni
2022-12-01 13:27     ` Ross Burton
2022-12-01 15:14       ` Alexandre Belloni [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=Y4jE8wXWKjCvQegF@mail.local \
    --to=alexandre.belloni@bootlin.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=pyih.soft@gmail.com \
    --cc=ross.burton@arm.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