Openembedded Core Discussions
 help / color / mirror / Atom feed
From: richard.purdie@linuxfoundation.org
To: Kang Kai <Kai.Kang@windriver.com>,
	 openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/1] image_types_wic: set consistent staging dirs
Date: Mon, 15 Oct 2018 08:10:54 +0100	[thread overview]
Message-ID: <aa73bd86641971a244b900e3736900d538732499.camel@linuxfoundation.org> (raw)
In-Reply-To: <9da9fad9-38c1-a465-8154-ab1581b15e73@windriver.com>

On Mon, 2018-10-15 at 08:54 +0800, Kang Kai wrote:
> On 2018年10月12日 18:43, Richard Purdie wrote:
> > On Fri, 2018-10-12 at 16:57 +0800, kai.kang@windriver.com wrote:
> > > From: Kai Kang <kai.kang@windriver.com>
> > > 
> > > When build wic image with multilib enabled by following config:
> > > 
> > >    MACHINE = "qemux86-64"
> > >    require conf/multilib.conf
> > >    MULTILIBS = "multilib:lib32"
> > >    DEFAULTTUNE_virtclass-multilib-lib32 = "x86"
> > > 
> > >    IMAGE_FSTYPES = "wic"
> > > 
> > > it fails to build lib32 image such as lib32-core-image-minimal:
> > > 
> > > > DEBUG: Executing shell function do_image_wic
> > > > INFO: Creating image(s)...
> > > > 
> > > > ERROR: Couldn't find correct bootimg_dir, exiting
> > > 
> > > Dependency syslinux is not expand to lib32-syslinux when multilib
> > > is
> > > enabled. It is populated to ${WORKDIR}/recipe-sysroot, but script
> > > wic
> > > searches syslinux in ${WORKDIR}/lib32-recipe-sysroot and causes
> > > error.
> > > 
> > > Set consistent staging dirs for wic to fix the issue.
> > > 
> > > Signed-off-by: Kai Kang <kai.kang@windriver.com>
> > > ---
> > >   meta/classes/image_types_wic.bbclass | 5 +++++
> > >   1 file changed, 5 insertions(+)
> > > 
> > > diff --git a/meta/classes/image_types_wic.bbclass
> > > b/meta/classes/image_types_wic.bbclass
> > > index 5b40a9e919..402920805d 100644
> > > --- a/meta/classes/image_types_wic.bbclass
> > > +++ b/meta/classes/image_types_wic.bbclass
> > > @@ -54,6 +54,11 @@ WKS_FILE_DEPENDS ??=
> > > "${WKS_FILE_DEPENDS_DEFAULT}
> > > ${WKS_FILE_DEPENDS_BOOTLOADERS
> > >   
> > >   DEPENDS += "${@ '${WKS_FILE_DEPENDS}' if d.getVar('USING_WIC')
> > > else
> > > '' }"
> > >   
> > > +# Dependency syslinux is not expanded when multilib is enabled,
> > > consistent staging dirs are needed
> > > +RECIPE_SYSROOT = "${WORKDIR}/recipe-sysroot"
> > > +STAGING_DIR_HOST = "${WORKDIR}/recipe-sysroot"
> > > +STAGING_DIR_TARGET = "${WORKDIR}/recipe-sysroot"
> > > +
> > 
> > Doesn't that change this for *all* image types? Not sure that is a
> > good
> > idea...
> 
> OK. I'll build and test all image types.

That isn't my point, the autobuilder could test that.

I don't like changes which are so wide reaching where we can't easily
evaluate the impact or potential problems in other code.

I think we need to look for a better way to fix this.

Cheers,

Richard



      reply	other threads:[~2018-10-15  7:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-12  8:57 [PATCH 0/1] image_types_wic: set consistent staging dirs kai.kang
2018-10-12  8:57 ` [PATCH 1/1] " kai.kang
2018-10-12 10:43   ` Richard Purdie
2018-10-15  0:54     ` Kang Kai
2018-10-15  7:10       ` richard.purdie [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=aa73bd86641971a244b900e3736900d538732499.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=Kai.Kang@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    /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