From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Bruce Ashfield <bruce.ashfield@gmail.com>,
"Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/9 v3] kernel-devsrc: restructure for out of tree (and on target) module builds
Date: Thu, 29 Mar 2018 14:30:47 +0100 [thread overview]
Message-ID: <1522330247.11431.92.camel@linuxfoundation.org> (raw)
In-Reply-To: <CADkTA4MGW3B_R-Y1oAi7BNa8CqxKbRx6ben3F3hXDz-F9vj0CA@mail.gmail.com>
On Thu, 2018-03-15 at 09:45 -0400, Bruce Ashfield wrote:
> On Wed, Mar 7, 2018 at 3:40 AM, Burton, Ross <ross.burton@intel.com>
> wrote:
> >
> > On 6 March 2018 at 18:11, Bruce Ashfield <bruce.ashfield@windriver.
> > com>
> > wrote:
> > >
> > >
> > > +RDEPENDS_${PN} = "bc python ${TCLIBC}-utils"
> > > +# 4.15+ needs these next two RDEPENDS
> > > +RDEPENDS_${PN} += "openssl-dev util-linux"
> > > +# and x86 needs a bit more for 4.15+
> > > +RDEPENDS_${PN} += "${@bb.utils.contains('ARCH', 'x86',
> > > 'elfutils', '',
> > > d)}"
> >
> > Annoyingly this is breaking our multilib test case:
> >
> > https://autobuilder.yocto.io/builders/nightly-multilib/builds/852/s
> > teps/BuildImages_4/logs/stdio
> >
> > It's entirely possible that the test is broken in some way but it's
> > far too
> > early for me right now to comprehend the multilib matrix...
> I was trying to reproduce this here, and couldn't make any sense out
> of the configuration.
>
> Is there somewhere that I can read to figure out what to put in my
> local.conf to reproduce
> that configuration ?
Sorry, I was travelling. I think this should do it:
MACHINE = "qemux86"
require conf/multilib.conf
MULTILIBS = "multilib:lib64"
DEFAULTTUNE_virtclass-multilib-lib64 = "x86-64"
$ bitbake lib64-core-image-sato-sdk
Cheers,
Richard
next prev parent reply other threads:[~2018-03-29 13:30 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-06 18:11 [PATCH 0/9] kernel-yocto: consolidated pull request Bruce Ashfield
2018-03-06 18:11 ` [PATCH 1/9 v3] kernel-devsrc: restructure for out of tree (and on target) module builds Bruce Ashfield
2018-03-07 8:40 ` Burton, Ross
2018-03-07 13:35 ` Bruce Ashfield
2018-03-08 18:51 ` Richard Purdie
2018-03-15 13:45 ` Bruce Ashfield
2018-03-29 13:30 ` Richard Purdie [this message]
2018-03-06 18:11 ` [PATCH 2/9] linux-libc-headers: update to 4.15.7 Bruce Ashfield
2018-03-06 18:11 ` [PATCH 3/9] linux-yocto/4.15: update to v4.15.7 Bruce Ashfield
2018-03-06 18:11 ` [PATCH 4/9] linux-yocto/4.14: update to v4.14.24 Bruce Ashfield
2018-03-06 18:11 ` [PATCH 5/9] linux-yocto/4.12: fix aufs compile warning Bruce Ashfield
2018-03-06 18:11 ` [PATCH 6/9] linux-yocto/4.12: memleak and build warning fixes Bruce Ashfield
2018-03-06 18:11 ` [PATCH 7/9] linux-yocto: aufs and systemtap Bruce Ashfield
2018-03-07 8:38 ` Burton, Ross
2018-03-07 13:39 ` Bruce Ashfield
2018-03-07 15:06 ` Bruce Ashfield
2018-03-07 15:35 ` Burton, Ross
2018-03-14 12:41 ` Burton, Ross
2018-03-14 12:46 ` Bruce Ashfield
2018-03-14 12:50 ` Burton, Ross
2018-03-14 15:11 ` Bruce Ashfield
2018-03-06 18:11 ` [PATCH 8/9] linux-yocto/4.12: warning: drm/i915/cfl: Coffee Lake works on Kaby Lake PCH Bruce Ashfield
2018-03-06 18:11 ` [PATCH 9/9] kernel: make copying of crtsavres.o conditional Bruce Ashfield
2018-03-06 18:33 ` ✗ patchtest: failure for kernel-yocto: consolidated pull request Patchwork
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=1522330247.11431.92.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=bruce.ashfield@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@intel.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