Re: [yocto] [yocto-docs][PATCH] dev-manual: document CPU features and QB_CPU_KVM

2018-04-30 Thread Martin Kelly
27, 2018 at 10:46 AM, Martin Kelly <mke...@xevo.com <mailto:mke...@xevo.com>> wrote: As suggested in a recent mail thread by Martin Jansa, there are cases in which QEMU under KVM will crash because of CPU feature incompatibilities between compiled binaries and the ho

[yocto] [yocto-docs][PATCH] dev-manual: document CPU features and QB_CPU_KVM

2018-04-27 Thread Martin Kelly
work around it. Signed-off-by: Martin Kelly <mke...@xevo.com> --- documentation/dev-manual/dev-manual-qemu.xml | 22 ++ 1 file changed, 22 insertions(+) diff --git a/documentation/dev-manual/dev-manual-qemu.xml b/documentation/dev-manual/dev-manual-qemu.xml index f47

Re: [yocto] CROPS status?

2017-12-14 Thread Martin Kelly
actively being worked on? Are there any related repositories I should be looking at? On 12/13/17, 10:26 AM, "Martin Kelly" <mke...@xevo.com> wrote: Hi, I recently discovered the CROPS project at https://github.com/crops/crops. It looks like a great

[yocto] CROPS status?

2017-12-13 Thread Martin Kelly
Hi, I recently discovered the CROPS project at https://github.com/crops/crops. It looks like a great idea, but I see it hasn't had a commit since June 23, 2016. Is the project still active? Thanks, Martin -- ___ yocto mailing list

Re: [yocto] How should we handle GCC 6 and -isystem /usr/include?

2017-04-26 Thread Martin Kelly
On 04/25/2017 05:44 PM, Khem Raj wrote: On 4/20/17 5:04 PM, Martin Kelly wrote: Hi, After compiling a package with GCC 6, I noticed the following error, which is a known issue: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70129 The problem is caused by adding -isystem /usr/include, which

Re: [yocto] Qt 5.8: do_rootfs: File 'qtdeclarative-plugins' not found

2017-04-25 Thread Martin Kelly
On 04/25/2017 07:41 AM, Malte Thiel wrote: Hello, I am trying to compile a Qt 5.8 application using the master branch of meta-qt5/recipes-qt/qt5/ (For 5.8 support). Within my recipe I have: RDEPENDS_${PN} = "libgcc glibc qtbase [...] qtdeclarative" My recipe (and therefore the application)

[yocto] How should we handle GCC 6 and -isystem /usr/include?

2017-04-20 Thread Martin Kelly
Hi, After compiling a package with GCC 6, I noticed the following error, which is a known issue: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70129 The problem is caused by adding -isystem /usr/include, which breaks the GCC 6's #include_next. I see that Khem Raj already removed this for the

Re: [yocto] Relicensing an Apache-licensed recipe as MIT

2017-04-12 Thread Martin Kelly
On 04/12/2017 09:43 AM, Martin Kelly wrote: On 04/12/2017 03:50 AM, Jussi Kukkonen wrote: On 12 April 2017 at 12:54, Paul Eggleton <paul.eggle...@linux.intel.com <mailto:paul.eggle...@linux.intel.com>> wrote: On Wednesday, 12 April 2017 7:14:00 PM NZST Jussi Kukkonen wrote:

Re: [yocto] Relicensing an Apache-licensed recipe as MIT

2017-04-12 Thread Martin Kelly
On 04/12/2017 03:50 AM, Jussi Kukkonen wrote: On 12 April 2017 at 12:54, Paul Eggleton <paul.eggle...@linux.intel.com <mailto:paul.eggle...@linux.intel.com>> wrote: On Wednesday, 12 April 2017 7:14:00 PM NZST Jussi Kukkonen wrote: > On 11 April 2017 at 23:52, Ma

[yocto] Relicensing an Apache-licensed recipe as MIT

2017-04-11 Thread Martin Kelly
Hi, I'm thinking about integrating the open-vm-tools recipe from openswitch[1] into openembedded (it massively improves the performance of VMWare guests) but first I have a question about licensing. The openswitch repository is Apache-licensed while the openembedded layers are all MIT

Re: [yocto] runqemu - "Could not initialize SDL(No available video device) - exiting"

2017-04-06 Thread Martin Kelly
I found the source of the issue (SDL must be compiled with X11 support) and sent a patch to OE-core to fix it: https://patchwork.openembedded.org/series/6211 On 04/04/2017 03:41 PM, Martin Kelly wrote: [This sender failed our fraud detection checks and may not be who they appear to be. Learn

[yocto] runqemu - "Could not initialize SDL(No available video device) - exiting"

2017-04-04 Thread Martin Kelly
Hi, I'm hitting an error on runqemu when I try to build an SDK and image on one machine and run it on another, even when the build machine and qemu-running machine match very closely (both running Debian Jessie on Intel 64-bit hardware). Specifically, I get this error: Could not initialize