From: Michael Olbrich <m.olbrich@pengutronix.de>
To: Guillermo Rodriguez Garcia <guille.rodriguez@gmail.com>
Cc: "ptxdist@pengutronix.de" <ptxdist@pengutronix.de>
Subject: Re: [ptxdist] Kernel GCC plugins
Date: Tue, 20 Jul 2021 14:02:46 +0200 [thread overview]
Message-ID: <20210720120246.GK15288@pengutronix.de> (raw)
In-Reply-To: <CABDcavZbjMQdMoQnScC-kmtciA2vKrton+-ztexWSCnYVBXqGQ@mail.gmail.com>
Hi,
On Mon, Jul 19, 2021 at 01:45:44PM +0200, Guillermo Rodriguez Garcia wrote:
> El vie, 16 jul 2021 a las 15:04, Michael Olbrich (<m.olbrich@pengutronix.de>)
> escribió:
> > On Fri, Jul 16, 2021 at 02:45:40PM +0200, Guillermo Rodriguez Garcia wrote:
> > > El viernes, 16 de julio de 2021, Alexander Dahl <post@lespocky.de>
> > escribió:
> > > > 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?
> > >
> > >
> > > Do I need to do something special for this to work?
> > >
> > > I’m on ptxdist 2021.07.0 so the above fixes should be merged, yet I am
> > > still having the problem ..
> >
> > Is PTXCONF_KERNEL_GCC_PLUGINS disabled?
>
> Yes.
Ok.
> > And which kernel version?
>
>
> 5.4.56
>
> I am rechecking, perhaps I did something wrong in the process.
Or maybe that version has a different check. Looking hat the history, I
definitely checked v4.19 and v5.6. I'm not sure about the versions in
between. Take a look at what scripts/gcc-plugins/Kconfig is doing.
Michael
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
To unsubscribe, send a mail with subject "unsubscribe" to ptxdist-request@pengutronix.de
prev parent reply other threads:[~2021-07-20 12:02 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
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 [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=20210720120246.GK15288@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=guille.rodriguez@gmail.com \
--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