From: Alexander Dahl <post@lespocky.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] Kernel GCC plugins
Date: Fri, 16 Jul 2021 14:11:52 +0200 [thread overview]
Message-ID: <20210716121151.yz7ksnenssgzosci@falbala.internal.home.lespocky.de> (raw)
In-Reply-To: <CABDcavbMrCE=yXDZ=MSbVCe1AVHX0U1-9XmmgZd0X5HN1J1QXg@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1251 bytes --]
Hei hei,
On Fri, Jul 16, 2021 at 01:32:29PM +0200, Guillermo Rodriguez Garcia wrote:
> I notice that the kernelconfig files changes depending on the host gcc
> version; in particular depending on supported gcc plugins.
>
> However this does not seem to make much sense -- the kernel will not be
> built using the host gcc; it will be built using the cross compiler from
> the toolchain.
>
> Is it possible to avoid this?
IIRC this was addressed several times in recent ptxdist versions:
- ptxdist-2021.04.0-14-g533f7709f ("kernel/kernel-template: set PTXDIST_NO_GCC_PLUGINS=1 in _MAKE_ENV as well")
- ptxdist-2021.03.0-69-g7a90f622f ("template: kernel: fix disabling gcc plugins for >= v5.11")
- ptxdist-2021.03.0-33-g114fecbd4 ("kernel: really fix disabling gcc plugins for >= v5.11)
- ptxdist-2021.02.0-41-gd57abb428 ("kernel: fix disabling gcc plugins for >= v5.11")
… and maybe more?
Or is yours another problem?
Greets
Alex
--
/"\ ASCII RIBBON | »With the first link, the chain is forged. The first
\ / CAMPAIGN | speech censured, the first thought forbidden, the
X AGAINST | first freedom denied, chains us all irrevocably.«
/ \ HTML MAIL | (Jean-Luc Picard, quoting Judge Aaron Satie)
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
[-- Attachment #2: Type: text/plain, Size: 181 bytes --]
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
To unsubscribe, send a mail with subject "unsubscribe" to ptxdist-request@pengutronix.de
next parent reply other threads:[~2021-07-16 12:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CABDcavbMrCE=yXDZ=MSbVCe1AVHX0U1-9XmmgZd0X5HN1J1QXg@mail.gmail.com>
2021-07-16 12:11 ` Alexander Dahl [this message]
2021-07-16 12:58 ` Michael Olbrich
[not found] ` <CABDcavYOeVWR+nVkMo4HXxFme=EmK050C383jGbAatD+N8GU3g@mail.gmail.com>
2021-07-16 13:04 ` Michael Olbrich
[not found] ` <CABDcavZbjMQdMoQnScC-kmtciA2vKrton+-ztexWSCnYVBXqGQ@mail.gmail.com>
2021-07-20 12:02 ` Michael Olbrich
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=20210716121151.yz7ksnenssgzosci@falbala.internal.home.lespocky.de \
--to=post@lespocky.de \
--cc=ptxdist@pengutronix.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox