All of lore.kernel.org
 help / color / mirror / Atom feed
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, 08 Mar 2018 10:51:54 -0800	[thread overview]
Message-ID: <1520535114.10851.91.camel@linuxfoundation.org> (raw)
In-Reply-To: <CADkTA4P58D1LFLCRZc6PvXa1+R2NTb1LF55EL+U7m+XbwLo4mQ@mail.gmail.com>

On Wed, 2018-03-07 at 08:35 -0500, 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...
> And at this point, I'm basically out of cycles for hacking on devsrc
> :(
> 
> I'll see about it again at the start of next week, and failing that,
> bump it to the next release cycle.

Just as a quick brain dump from a glance at this, I think the issue is
the openssl-dev dependency. It sounds like the image tries to install
two sets of -dev packages and those files conflict. Quite why its doing
that and how/why they conflict I don't know but the -dev dependency is
where I'd start looking at this.

I will also mention that -dev packages are not so well looked at with
multilib, we probably don't test that area much :(.

Cheers,

Richard 


  reply	other threads:[~2018-03-08 18:52 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 [this message]
2018-03-15 13:45     ` Bruce Ashfield
2018-03-29 13:30       ` Richard Purdie
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=1520535114.10851.91.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 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.