[oe] [PATCH] libqmi: fix floating dependencies

libgudev: * Is not configurable -> DEPENDS * fixes | WARNING: libqmi-1.16.0-r0 do_package_qa: QA Issue: libqmi rdepends on libgudev, but it isn't a build dependency, missing libgudev in DEPENDS or PACKAGECONFIG? [build-deps] | WARNING: libqmi-1.16.0-r0 do_package_qa: QA Issue: libqmi rdepends on

[oe] [meta-oe][PATCH] lmsensors: sensors-detect: print a special message when there isn't enough cpu info

When running sensors-detect, if there isn't enough information in /proc/cpuinfo for this arch (e.g. ppc64), "Use of uninitialized value in concatenation (.) or string at /usr/sbin/sensors-detect line 2867" and incomplete "# Processor: (//)" will be printed. Here print out a prompt for such a case.

[oe] [meta-oe][PATCH] xpext-dev: Remove RDEPEND on empty xpext package.

If xpext is included in a build (ie via dependency on mpv) then builds of core-image-sato-sdk will fail with errors such as below. warning: Can't install mpv-dev-0.15.0-r0@i586: Can't install xpext-dev-1.0+5-r0@i586: no package provides xpext = 1.0+5-r0 Signed-off-by: Drew Moseley

[oe] [meta-oe][PATCH] glcompbench: Fix issues causing failures in GCC6

Signed-off-by: Ann Thornton --- .../glcompbench/Fix-configure-for-sqrt-check.patch | 14 + .../glcompbench/Fix_auto_ptr_deprecated.patch | 24 ++ .../glcompbench/glcompbench/Fix_space_issues.patch | 22

[oe] [meta-oe][PATCH] glcompbench: Fix issues causing failures in GCC6

Signed-off-by: Ann Thornton --- .../glcompbench/Fix-configure-for-sqrt-check.patch | 14 + .../glcompbench/Fix_auto_ptr_deprecated.patch | 24 ++ .../glcompbench/glcompbench/Fix_space_issues.patch | 22

[oe] [PATCH] glade: fix typo introduced in last patch

Signed-off-by: Andreas Müller --- meta-oe/recipes-devtools/glade/files/0002-fix-gcc-6-build.patch | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/meta-oe/recipes-devtools/glade/files/0002-fix-gcc-6-build.patch

Re: [oe] [meta-oe][PATCH] xpext: Allow the main package to be empty.

> On Sep 6, 2016, at 5:06 PM, Martin Jansa wrote: > > On Tue, Sep 06, 2016 at 02:41:55PM -0400, Drew Moseley wrote: >> If xpext is included in a build (ie via dependency on mpv) then >> builds of core-image-sato-sdk will fail with errors such as below. >> >> Allowing

Re: [oe] [PATCH 5/5] samba: fix build by linking with bfd instead of gold

On Tue, Sep 6, 2016 at 8:28 PM, Khem Raj wrote: > >> On Sep 4, 2016, at 1:15 PM, Andreas Müller >> wrote: >> >> Use this workaround as long as there is no better (upstream) fix >> >> Signed-off-by: Andreas Müller

Re: [oe] [meta-oe][PATCH] xpext: Allow the main package to be empty.

On Tue, Sep 06, 2016 at 02:41:55PM -0400, Drew Moseley wrote: > If xpext is included in a build (ie via dependency on mpv) then > builds of core-image-sato-sdk will fail with errors such as below. > > Allowing the package to be empty fixes this. > > warning: Can't install

[oe] [meta-oe][PATCH] xpext: Allow the main package to be empty.

If xpext is included in a build (ie via dependency on mpv) then builds of core-image-sato-sdk will fail with errors such as below. Allowing the package to be empty fixes this. warning: Can't install mpv-dev-0.15.0-r0@i586: Can't install xpext-dev-1.0+5-r0@i586: no package provides xpext =

Re: [oe] [PATCH 5/5] samba: fix build by linking with bfd instead of gold

> On Sep 4, 2016, at 1:15 PM, Andreas Müller > wrote: > > Use this workaround as long as there is no better (upstream) fix > > Signed-off-by: Andreas Müller > --- > meta-networking/recipes-connectivity/samba/samba_4.4.5.bb | 2 +- >

Re: [oe] persistent storage & RO rootfs

> On Sep 5, 2016, at 2:05 AM, André Draszik wrote: > > Hi, > > I want to use a read-only rootfs, but some packages will need persistent > storage, which typically involves /var/lib/ > > Two solutions come to mind: > - bbappend each involved recipe and set the --localstatedir

Re: [oe] question about yocto+qt5+qemu

> On Sep 5, 2016, at 10:11 PM, milad hasanvand > wrote: > > Dear all, > > please correct me if it not the right place to ask this question. > has anyone built qt5 using meta-qt5 and yocto(krogoth) for qemux8? > > I have tested every possible hint I found on the

Re: [oe] [meta-java]: java and javac in path provided by cocao and ecj

> On Sep 6, 2016, at 2:35 AM, Pascal Bach wrote: > > Hi > > > While diving into meta-java I noticed the following. > > The java version that is found by default in an SDK is provided by > cacao-native and the javac version by ecj-native. > Both of these are very old

[oe] [PATCH] lvm2: add PACKAGECONFIG for lvm thin provisioning

The thin provisioning tools is runtime dependency, so disable build time detection. Signed-off-by: Hongxu Jia --- meta-oe/recipes-support/lvm2/lvm2.inc | 12 ++-- 1 file changed, 10 insertions(+), 2 deletions(-) diff --git

Re: [oe] Please merge krogoth-next > krogoth

On Tue, Sep 06, 2016 at 07:04:55AM -0700, akuster808 wrote: > Please merge Kogoth-next to krogoth. > > TIA, done > > Armin > -- Martin 'JaMa' Jansa jabber: martin.ja...@gmail.com signature.asc Description: Digital signature -- ___

Re: [oe] [PATCH 1/1] add PACKAGECONFIG for lvm thin provisioning

On Tue, Sep 06, 2016 at 05:15:15AM -0400, Hongxu Jia wrote: > The thin provisioning tools is runtime dependency, > so disable build time detection. > > Signed-off-by: Hongxu Jia Next time start the summary with component name. > --- >

[oe] Please merge krogoth-next > krogoth

Please merge Kogoth-next to krogoth. TIA, Armin -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel

Re: [oe] fftw recipes

On 06/09/16 08:02, Andreas Müller wrote: Hi, is there a technical reason why we have multiple fftw recipes (fftw / fftwl / fftwf)? or before I start: Any complaints/comments if I * merge all fftw's into one recipe named fftw splitting in multiple packages (fftw / fftwl / fftwf / fftwq?) *

[oe] [meta-oe][PATCH 0/1] add PACKAGECONFIG for lvm thin provisioning

The following changes since commit 291946d2501be1dc2549304460e3e288408dfbfe: directfb: add PACKAGECONFIG for inputdrivers (2016-09-05 13:30:55 +0200) are available in the git repository at: git://git.openembedded.org/openembedded-core-contrib hongxu/lvm2

[oe] [PATCH 1/1] add PACKAGECONFIG for lvm thin provisioning

The thin provisioning tools is runtime dependency, so disable build time detection. Signed-off-by: Hongxu Jia --- meta-oe/recipes-support/lvm2/lvm2.inc | 12 ++-- 1 file changed, 10 insertions(+), 2 deletions(-) diff --git

[oe] [meta-networking][PATCH] stunnel: 5.28 -> 5.35

Upgrade stunnel from 5.28 to 5.35. Signed-off-by: Wang Xin --- .../recipes-support/stunnel/{stunnel_5.28.bb => stunnel_5.35.bb} | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) rename meta-networking/recipes-support/stunnel/{stunnel_5.28.bb =>

Re: [oe] fftw recipes

Op 06-09-16 om 09:02 schreef Andreas Müller: > Hi, > > is there a technical reason why we have multiple fftw recipes (fftw / > fftwl / fftwf)? Yes, at the time of writing there was no easy way to generate the different libraries using one recipe. Worse, the headers conflict, even in the current

[oe] fftw recipes

Hi, is there a technical reason why we have multiple fftw recipes (fftw / fftwl / fftwf)? or before I start: Any complaints/comments if I * merge all fftw's into one recipe named fftw splitting in multiple packages (fftw / fftwl / fftwf / fftwq?) * replace virtual/fftw by fftw * make oe-core's