From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Trevor Woerner <twoerner@gmail.com>,
"Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH][jethro][RFC 1/2] libsdl: expand PACKAGECONFIG and enable native builds
Date: Fri, 11 Mar 2016 23:16:49 +0000 [thread overview]
Message-ID: <1457738209.2804.259.camel@linuxfoundation.org> (raw)
In-Reply-To: <56E33A51.2020807@gmail.com>
On Fri, 2016-03-11 at 16:36 -0500, Trevor Woerner wrote:
> Hi Ross,
>
> On 03/11/16 15:49, Burton, Ross wrote:
> >
> > On 11 March 2016 at 20:20, Trevor Woerner <twoerner@gmail.com
> > <mailto:twoerner@gmail.com>> wrote:
> >
> > ERROR: Nothing PROVIDES 'virtual/nativesdk-nativesdk-libx11'
> > (but
> > virtual:nativesdk:/z/dragon410c-repo/dragon410c-tw
> > -jethro/layers/openembedded-core/meta/recipes
> > -graphics/libsdl/libsdl_1.2.15.bb
> > <http://libsdl_1.2.15.bb> DEPENDS on or otherwise requires it).
> > Close matches:
> >
> >
> > That's an awesome comment. Clearly my testing wasn't optimal,
> > there's
> > another patch required.
> >
> > Can you verify that
> > cherry-picking 55ca1fb8f0e81ff739b3c46897e43356d1f760c3 solves
> > this?
>
> Yes, verified. Cherry-picking 55ca1fb8 solves the problem.
>
> Thanks! :-)
I just merged the fix to the branch, thanks for testing.
Cheers,
Richard
next prev parent reply other threads:[~2016-03-11 23:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-29 16:02 [PATCH][jethro][RFC 1/2] libsdl: expand PACKAGECONFIG and enable native builds Ross Burton
2016-02-29 16:02 ` [PATCH][jethro][RFC 2/2] conf/local.conf.sample: comment out ASSUME_PROVIDED=libsdl-native Ross Burton
2016-03-11 20:20 ` [PATCH][jethro][RFC 1/2] libsdl: expand PACKAGECONFIG and enable native builds Trevor Woerner
2016-03-11 20:49 ` Burton, Ross
2016-03-11 21:36 ` Trevor Woerner
2016-03-11 23:16 ` Richard Purdie [this message]
2016-03-12 2:58 ` Trevor Woerner
2016-03-14 18:40 ` Otavio Salvador
2016-03-14 20:36 ` Burton, Ross
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=1457738209.2804.259.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@intel.com \
--cc=twoerner@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox