From: Amarnath Valluri <amarnath.valluri@intel.com>
To: Jason Wessel <jason.wessel@windriver.com>
Cc: OE-core <Openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 2/2] Revert "kernel: Modify kernel modules installation path."
Date: Thu, 02 Feb 2017 23:10:31 +0200 [thread overview]
Message-ID: <1486069831.2080.17.camel@intel.com> (raw)
In-Reply-To: <869ff8ea-8803-2751-3d2f-187eff4755b5@windriver.com>
Hi,
I am very sorry, i couldn't respond earlier than this, somehow i missed
this thread :(
The motivation of these patches was achieving merged '/usr' in oe-core,
which demands no package installs anything into root(/bin, /sbin, /lib)
folders, and i see no exception for kernel modules/firmware(may be i am
wrong :!). In the real merged usr environment this shouldn't be a
problem as the root symlinks exists.
I guess i can resend these patches as part of 'usrmerge' feature patch
sequence, by keeping these changes behind DISTRO_FEATURES check:
- Amarnath
On Fri, 2017-01-20 at 08:04 -0600, Jason Wessel wrote:
> On 01/20/2017 07:52 AM, Burton, Ross wrote:
>
> >
> > On 20 January 2017 at 13:48, Jason Wessel
> > <jason.wessel@windriver.com> wrote:
> > WARNING: linux-yocto-4.8.12+gitAUTOINC
> > +3edb4de355_9bcb4ea3fa-r0 do_package: QA Issue: linux-yocto:
> > Files/directories were installed but not shipped in any
> > package:
> > /lib64
> > /lib/modules/4.8.17-yocto-standard/modules.builtin
> > /lib64/firmware
> > /lib64/firmware/cpia2
> > /lib64/firmware/cpia2/stv0672_vp4.bin
> > Please set FILES such that these items are packaged.
> > Alternatively if they are unneeded, avoid installing them or
> > delete them within do_install.
> > linux-yocto: 5 installed and not shipped files.
> > [installed-vs-shipped]
> >
> > I suspect this is trivial with fresh eyes. What multilib
> > configuration are you using? My usual "test multilib" stanza is:
> >
> >
> > #require conf/multilib.conf
> > #MULTILIBS_x86-64 = "multilib:lib32"
> > #DEFAULTTUNE_virtclass-multilib-lib32 = "x86"
> >
> >
> > I'm guessing this isn't going to produce the same paths that you're
> > seeing problems with.
> >
> >
> > Ross
>
>
> It looks like it probably should.
>
>
> MULTILIBS = "multilib:lib32"
> DEFAULTTUNE_virtclass-multilib-lib32 = "x86"
>
>
>
> If for some reason you wanted to perform the exact same build I have
> the instructions to do so:
>
> https://github.com/WindRiver-OpenSourceLabs/wr-core/blob/master/docs/README-intel-x86.TXT
>
>
> That basically amounts to:
>
> git clone -b master --recurse-submodules
> https://github.com/WindRiver-OpenSourceLabs/wr-core
>
> cd wr-core
>
> . init-intel-x86-env
>
>
> Jason.
>
>
> --
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
prev parent reply other threads:[~2017-02-02 21:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-19 21:14 [PATCH 1/2] Revert "linux-firmware: Modify firmware installation path" Jason Wessel
2017-01-19 21:14 ` [PATCH 2/2] Revert "kernel: Modify kernel modules installation path." Jason Wessel
2017-01-19 21:24 ` Jason Wessel
2017-01-19 23:43 ` Burton, Ross
2017-01-20 13:29 ` Maxin B. John
2017-01-20 13:30 ` Burton, Ross
2017-01-20 13:48 ` Jason Wessel
2017-01-20 13:52 ` Burton, Ross
2017-01-20 14:04 ` Jason Wessel
2017-02-02 21:10 ` Amarnath Valluri [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=1486069831.2080.17.camel@intel.com \
--to=amarnath.valluri@intel.com \
--cc=Openembedded-core@lists.openembedded.org \
--cc=jason.wessel@windriver.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