All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Bruce Ashfield" <bruce.ashfield@gmail.com>
To: Bruce Ashfield <bruce.ashfield@gmail.com>
Cc: Vyacheslav Yurkov <uvv.mail@gmail.com>,
	 Patches and discussions about the oe-core layer
	<Openembedded-core@lists.openembedded.org>,
	 Vyacheslav Yurkov <Vyacheslav.Yurkov@bruker.com>
Subject: Re: [OE-core] [PATCH] module.bbclass: add HOSTCC for out-of-tree modules
Date: Thu, 1 Oct 2020 11:05:41 -0400	[thread overview]
Message-ID: <CADkTA4PL-Bs+NG9rYOgZ6_oETHG4q3+33x6TEoCmdxVp-AeVHw@mail.gmail.com> (raw)
In-Reply-To: <1639E5FC19B7A570.14692@lists.openembedded.org>

On Thu, Oct 1, 2020 at 10:53 AM Bruce Ashfield via
lists.openembedded.org
<bruce.ashfield=gmail.com@lists.openembedded.org> wrote:
>
> On Thu, Oct 1, 2020 at 10:47 AM Vyacheslav Yurkov <uvv.mail@gmail.com> wrote:
> >
> > On 01.10.2020 16:36, Bruce Ashfield wrote:
> > > We already ran into this with the main kernel flags, and we don't want
> > > to duplicate them here.
> > >
> > > Why aren't what we have in kernel.bbclass working in your scenario ?
> > >
> > > Bruce
> > >
> > Because kernel.bbclass is not pulled in into the environment of
> > out-of-tree module recipe. Should it be?
> > This can easily be checked when you do 'bitbake hello-mod -c devshell'
> > and examine $EXTRA_OEMAKE variable.
>
> Yes, it should be.
>
> We build out of tree modules in each autobuilder test run, so it is
> functional for the most part. I'd be interested to see the reproducing
> kernel module and build steps, so they can be built into the tests to
> catch this.

And by that, I mean more than the warnings about ORC, etc. Since those
have been popping up for some time.

I'm not saying we shouldn't be fixing those, I'm just wondering if
this is an actual build failure, versus the ones we know about.

(and either way, it doesn't change the way we fix it, just that we can
test it better).

Bruce

>
> But we absolutely do not want to duplicate those flags into this class.
>
> So with a reproducer, we can perhaps shuffle things around and make
> sure that both this new case and the old ones continue to work.
>
> Bruce
>
> >
> > Vyacheslav
>
>
>
> --
> - Thou shalt not follow the NULL pointer, for chaos and madness await
> thee at its end
> - "Use the force Harry" - Gandalf, Star Trek II
>
> 
>


-- 
- Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end
- "Use the force Harry" - Gandalf, Star Trek II

      parent reply	other threads:[~2020-10-01 15:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-01 13:59 [PATCH] module.bbclass: add HOSTCC for out-of-tree modules Vyacheslav Yurkov
2020-10-01 14:36 ` [OE-core] " Bruce Ashfield
2020-10-01 14:47   ` Vyacheslav Yurkov
2020-10-01 14:53     ` Bruce Ashfield
2020-10-01 15:05       ` Vyacheslav Yurkov
2020-10-01 15:16         ` Bruce Ashfield
     [not found]     ` <1639E5FC19B7A570.14692@lists.openembedded.org>
2020-10-01 15:05       ` Bruce Ashfield [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=CADkTA4PL-Bs+NG9rYOgZ6_oETHG4q3+33x6TEoCmdxVp-AeVHw@mail.gmail.com \
    --to=bruce.ashfield@gmail.com \
    --cc=Openembedded-core@lists.openembedded.org \
    --cc=Vyacheslav.Yurkov@bruker.com \
    --cc=uvv.mail@gmail.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.