[OE-core] [PATCH] binutils: enable warn system direcotories in cross-canadian ld

Warn system directories requires a configuration option to be enabled. This patch enables the warning for cross-canadian ld, to align with the cross version. Signed-off-by: Yuanjie Huang --- meta/recipes-devtools/binutils/binutils-cross-canadian.inc | 1 + 1 file

Re: [OE-core] [PATCH 0/1] $COREBASE/LICENSE in LIC_FILES_CHKSUM

Hi Olaf, On Wed, 19 Oct 2016 10:05:12 Olaf Mandel wrote: > I ran into QA issues when inadvertently replacing OEs LICENSE with > Yoctos LICENSE file. Why should recipes depend on the license for > the complete collection of layers? At least for "normal" recipes > that generate target device

Re: [OE-core] [PATCH 06/19] btrfs-tools: update to 4.8.1

On 19 October 2016 at 16:06, Alexander Kanavin < alexander.kana...@linux.intel.com> wrote: > Remove fix-parallel.patch as version.h is now generated by autoconf in > configure() > Doing a rebuild from clean (actually to test the man page patch) resulted in this:

Re: [OE-core] [PATCH 1/4] u-boot: Update to 2016.09.01 release

On 10/20/2016 05:16 PM, Burton, Ross wrote: > > On 20 October 2016 at 14:35, Marek Vasut > wrote: > > Upgrade U-Boot to the latest version. > > > I hope nobody objects but I squashed these for clarity. All right ;-) -- Best regards, Marek Vasut --

[OE-core] [PATCH][krogoth] dropbear: Fix multiple CVEs

CVE-2016-7406 CVE-2016-7407 CVE-2016-7408 CVE-2016-7409 Reference: https://matt.ucc.asn.au/dropbear/CHANGES [YOCTO #10443] Signed-off-by: Sona Sarmadi --- meta/recipes-core/dropbear/dropbear.inc|4 + .../dropbear/dropbear/CVE-2016-7406.patch |

[OE-core] [PATCH] build-appliance-image: add /sbin to PATH

runqemu script fails with an error when executed in Build Appliance. Typical use case: $ bitbake core-image-minimal $ runqemu qemux86 Observed error: runqemu - ERROR - In order for this script to dynamically infer paths ...snip... runqemu-ifup, runqemu-ifdown or ip not

Re: [OE-core] [PATCH 00/19] Recipe updates and version check fixes

On 10/20/2016 02:16 AM, Alexander Kanavin wrote: On 10/19/2016 10:42 PM, akuster808 wrote: Are these updates just bug fixes or do they also contain new features / enhancements. Having a little more description in the commit will help the morty maintainer determine if any of the updates are

Re: [OE-core] how do i get "nativesdk-rpm-build-5.4.16-r0.x86_64_nativesdk.rpm" into the SDK?

On Thu, 20 Oct 2016, Robert P. J. Day wrote: > > ok, this one should be simple ... i ran: > > $ bitbake -c populate_sdk core-image-minimal > > then popped into tmp/deploy/rpm/x86_64_nativesdk to see the rpms > of interest to me: > > nativesdk-rpm-5.4.16-r0.x86_64_nativesdk.rpm >

Re: [OE-core] [PATCH 1/4] u-boot: Update to 2016.09.01 release

On 20 October 2016 at 14:35, Marek Vasut wrote: > Upgrade U-Boot to the latest version. > I hope nobody objects but I squashed these for clarity. Ross -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org

[OE-core] how do i get "nativesdk-rpm-build-5.4.16-r0.x86_64_nativesdk.rpm" into the SDK?

ok, this one should be simple ... i ran: $ bitbake -c populate_sdk core-image-minimal then popped into tmp/deploy/rpm/x86_64_nativesdk to see the rpms of interest to me: nativesdk-rpm-5.4.16-r0.x86_64_nativesdk.rpm nativesdk-rpm-build-5.4.16-r0.x86_64_nativesdk.rpm

Re: [OE-core] [PATCH V3 3/4] u-boot: Drop PV altogether

On Thu, Oct 20, 2016 at 03:48:27PM +0200, Marek Vasut wrote: > Drop the explicit setting of PV altogether. This changes the U-Boot > version string from "v20yy.mm" to "20yy.mm" , so layer setting the > PREFERRED_VERSION_u-boot must be updated by removing the leading 'v'. > > Signed-off-by: Marek

Re: [OE-core] [PATCH 1/4] u-boot: Update to 2016.09.01 release

On Thu, Oct 20, 2016 at 03:35:11PM +0200, Marek Vasut wrote: > Upgrade U-Boot to the latest version. > > Signed-off-by: Marek Vasut > Cc: Richard Purdie > Cc: Denys Dmytriyenko Acked-by: Denys Dmytriyenko >

Re: [OE-core] [PATCH 2/4] u-boot: Drop the +git part from PV

On Thu, Oct 20, 2016 at 03:35:12PM +0200, Marek Vasut wrote: > The U-Boot package is using release versions of U-Boot, > so drop the extra +git part from PV. > > Signed-off-by: Marek Vasut > Cc: Richard Purdie > Cc: Denys Dmytriyenko

[OE-core] [PATCH V3 3/4] u-boot: Drop PV altogether

Drop the explicit setting of PV altogether. This changes the U-Boot version string from "v20yy.mm" to "20yy.mm" , so layer setting the PREFERRED_VERSION_u-boot must be updated by removing the leading 'v'. Signed-off-by: Marek Vasut Cc: Richard Purdie

Re: [OE-core] [PATCH V2 3/4] u-boot: Drop PV altogether

On Thu, Oct 20, 2016 at 03:35:13PM +0200, Marek Vasut wrote: > Drop the explicit setting of PV altogether. This changes the U-Boot > version string from "v20yy.mm" to "20yy.mm" , so layer setting the > PREFERRED_VERSION_u-boot must be updated by removing the leading 'v'. > > Signed-off-by: Marek

Re: [OE-core] [PATCH 4/4] u-boot: Drop redundant comment

On Thu, Oct 20, 2016 at 03:35:14PM +0200, Marek Vasut wrote: > Drop comment stating that the SRCREV corresponds to particular U-Boot > version. This comment is redundant, since the U-Boot version is part > of the recipe filename. > > Signed-off-by: Marek Vasut > Cc: Richard Purdie

[OE-core] [PATCH 2/4] u-boot: Drop the +git part from PV

The U-Boot package is using release versions of U-Boot, so drop the extra +git part from PV. Signed-off-by: Marek Vasut Cc: Richard Purdie Cc: Denys Dmytriyenko --- meta/recipes-bsp/u-boot/u-boot-common_2016.09.01.inc | 2 +-

Re: [OE-core] meta-toolchain and meta-toolchain-qt for specific image

On Wed, Oct 19, 2016 at 08:00:12PM -0700, Khem Raj wrote: > > > On Oct 19, 2016, at 1:19 AM, thilo.ceston...@ts.fujitsu.com wrote: > > > > Hey! > > > > I want to create such a nice toolchain installation package for my image > > recipe. > > The problem I currently hit is, that I need to do

Re: [OE-core] [PATCH 4/5] u-boot: Drop PV altogether

On 10/20/2016 12:13 PM, Burton, Ross wrote: > On 19 October 2016 at 23:53, Marek Vasut > wrote: > > OK, snap. Can you pick 1,2,3,5 so I don't have to resubmit them ? They > should apply cleanly and they are pretty orthogonal from the 4/5. > > > 1

[OE-core] [PATCH 4/4] u-boot: Drop redundant comment

Drop comment stating that the SRCREV corresponds to particular U-Boot version. This comment is redundant, since the U-Boot version is part of the recipe filename. Signed-off-by: Marek Vasut Cc: Richard Purdie Cc: Denys Dmytriyenko

[OE-core] [PATCH V2 3/4] u-boot: Drop PV altogether

Drop the explicit setting of PV altogether. This changes the U-Boot version string from "v20yy.mm" to "20yy.mm" , so layer setting the PREFERRED_VERSION_u-boot must be updated by removing the leading 'v'. Signed-off-by: Marek Vasut Cc: Richard Purdie

[OE-core] [PATCH 1/4] u-boot: Update to 2016.09.01 release

Upgrade U-Boot to the latest version. Signed-off-by: Marek Vasut Cc: Richard Purdie Cc: Denys Dmytriyenko --- .../{u-boot-common_2016.03.inc => u-boot-common_2016.09.01.inc} | 8 .../{u-boot-fw-utils_2016.03.bb =>

[OE-core] Performance tweaks in 2.2

I've been distracted with ELC-E and other travel but I wanted to recognise some good work people have done on the performance front. We identified a few issues recently: a) pseudo slowed down after upgrading sqlite b) we were using more space on disk (without rm_work) c) eSDK installation times

Re: [OE-core] [PATCH 1/1] Remove $COREBASE/LICENSE from LIC_FILES_CHKSUM

Hello, Am 20.10.2016 um 12:44 schrieb Peter Kjellerstedt: >> -Original Message- -Snipp- >> Subject: [OE-core] [PATCH 1/1] Remove $COREBASE/LICENSE from -Snipp- > > Even after this is applied, there are still nine recipes in OE-Core > that reference ${COREBASE}/LICENSE. There is also an

Re: [OE-core] how can i ask to keep all the generated "nativesdk" rpms?

On Thu, 20 Oct 2016, Richard Purdie wrote: > On Thu, 2016-10-20 at 06:31 -0400, Robert P. J. Day wrote: > >   just for fun, i'm going to do a fresh build right now, involving: > > > > * fresh "git pull" of poky > > * MACHINE=mpc8315e-rdb > > * bitbake core-image-minimal > > > [...] > > $ ls -l >

Re: [OE-core] [PATCH] libbsd 0.8.3: BBCLASSEXTEND to native and nativesdk

On 20 October 2016 at 09:30, Koen Kooi wrote: > +BBCLASSEXTEND = "native nativesdk" > The native form fails on Debian stable hosts: | make[2]: Entering directory '/data/poky-master/tmp-glibc/work/x86_64-linux/libbsd-native/0.8.3-r0/build/src' | ../x86_64-linux-libtool

Re: [OE-core] how can i ask to keep all the generated "nativesdk" rpms?

On 20 October 2016 at 11:31, Robert P. J. Day wrote: > should i have expected a nativesdk directory? > Not if you didn't build a SDK, no. Ross -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org

Re: [OE-core] how can i ask to keep all the generated "nativesdk" rpms?

On Thu, 2016-10-20 at 06:31 -0400, Robert P. J. Day wrote: >   just for fun, i'm going to do a fresh build right now, involving: > > * fresh "git pull" of poky > * MACHINE=mpc8315e-rdb > * bitbake core-image-minimal > [...] > $ ls -l > total 328 > drwxr-xr-x. 2 rpjday rpjday   4096 Oct 20 05:54

Re: [OE-core] [PATCH 1/1] Remove $COREBASE/LICENSE from LIC_FILES_CHKSUM

> -Original Message- > From: openembedded-core-boun...@lists.openembedded.org > [mailto:openembedded-core-boun...@lists.openembedded.org] On Behalf Of > Olaf Mandel > Sent: den 19 oktober 2016 12:05 > To: openembedded-core@lists.openembedded.org > Cc: Olaf Mandel > Subject: [OE-core]

Re: [OE-core] [PATCH] gnutls_3.5.3.bb: Fix native build on distro with kernel < 3.4.17

On 18 October 2016 at 02:16, Khem Raj wrote: > When using distros which use old kernels gnutls fails to build > due to missing SYS_getrandom, therefore we need to check for this > before using it. > Fixes errorr e.g. > > | ../../../gnutls-3.5.3/lib/nettle/rnd-linux.c: In

Re: [OE-core] how can i ask to keep all the generated "nativesdk" rpms?

On Wed, 19 Oct 2016, Richard Purdie wrote: > On Wed, 2016-10-19 at 17:34 -0400, Robert P. J. Day wrote: > >   so, i'm home and on a different system about to do a build ... > > refresh my memory, where are all those nativesdk rpms supposed to > > show up? if memory serves, they were under > >

Re: [OE-core] [PATCH 4/5] u-boot: Drop PV altogether

On 19 October 2016 at 23:53, Marek Vasut wrote: > OK, snap. Can you pick 1,2,3,5 so I don't have to resubmit them ? They > should apply cleanly and they are pretty orthogonal from the 4/5. > 1 is standalone and I've merged this into ross/mut already, but 3/4/5 are all basically

Re: [OE-core] any plans to upgrade to rpm-5.4.17?

On 20 October 2016 at 10:46, Robert P. J. Day wrote: > so is there an ETA for just moving to 5.4.17? > As the weekly schedule mails say we're currently hard frozen for the Morty/2.2 release. No doubt Mark is aware of the 5.4.17 release but upgrading rpm5 is "not trivial"

[OE-core] [PATCH] mesa: update to 12.0.3

* removed patch was applied mainline * tested on RaspberryPi2 weston / lxqt / kde Signed-off-by: Andreas Müller --- .../mesa/files/clang-compile-PR89599.patch | 116 - .../mesa/{mesa-gl_12.0.1.bb => mesa-gl_12.0.3.bb} | 0

[OE-core] any plans to upgrade to rpm-5.4.17?

just noticed in recipe rpm_5.4.16.bb: # There is no official 5.4.16 release yet, so start w/ 5.4.15 and patch it # based on CVS S = "${WORKDIR}/rpm-5.4.15" SRC_URI = "http://www.rpm5.org/files/rpm/rpm-5.4/rpm-5.4.15-0.20140824.src.rpm;name=srpm;extract=rpm-5.4.15.tar.gz \ ... snip ... but

Re: [OE-core] [PATCH 10/19] gnome-desktop3: update to 3.22.1

On 19 October 2016 at 16:06, Alexander Kanavin < alexander.kana...@linux.intel.com> wrote: > .../{gnome-desktop3_3.20.2.bb => gnome-desktop3_3.22.1.bb}| > 4 ++-- > * FILELIST: removed "/usr/lib/libgnome-desktop-3.so.12.1.0 /usr/share/libgnome-desktop-3.0/pnp.ids" added

Re: [OE-core] [PATCH 18/19] webkitgtk: update to 2.14.1

On 20 October 2016 at 10:23, Burton, Ross wrote: > buildhistory-diff reports that the binaries are being removed: > > packages/corei7-64-poky-linux/webkitgtk/webkitgtk-bin: PKGSIZE changed > from 213688 to 0 (-100%) > * FILELIST: removed all items "/usr/bin/MiniBrowser

[OE-core] how to add "uninative binary shim" to local source mirror?

i use a local source mirror to avoid massive fetching; my site.conf: SOURCE_MIRROR_URL ?= "file:///home/rpjday/oe/dist/tarballs/" INHERIT += "own-mirrors" BB_GENERATE_MIRROR_TARBALLS = "1" # BB_NO_NETWORK = "1" and if anything did need to get downloaded, i have a script i run from

Re: [OE-core] [PATCH 19/19] epiphany: update to 3.22.1

On 10/20/2016 06:31 AM, Khem Raj wrote: -EXTRA_OECONF += " --disable-nss --with-distributor-name=${DISTRO}" +EXTRA_OECONF += " --with-distributor-name=${DISTRO}" why is nss not disabled explicitly anymore ? Sorry, forgot to add this to the commit log - they dropped nss support altogether

Re: [OE-core] [PATCH 18/19] webkitgtk: update to 2.14.1

On 19 October 2016 at 16:06, Alexander Kanavin < alexander.kana...@linux.intel.com> wrote: > Rebase 0001-WebKitMacros-Append-to-I-and-not-to-isystem.patch > > Signed-off-by: Alexander Kanavin > buildhistory-diff reports that the binaries are being removed:

Re: [OE-core] [PATCH 00/19] Recipe updates and version check fixes

On 10/19/2016 10:42 PM, akuster808 wrote: Are these updates just bug fixes or do they also contain new features / enhancements. Having a little more description in the commit will help the morty maintainer determine if any of the updates are suitable to backporting. They're both. The updates

[OE-core] [PATCH] libbsd 0.8.3: BBCLASSEXTEND to native and nativesdk

Android-tools depends on it and to build the native versions of fastboot, adb, mkbootimg and others libbsd needs to support native builds. Signed-off-by: Koen Kooi --- meta/recipes-support/libbsd/libbsd_0.8.3.bb | 2 ++ 1 file changed, 2 insertions(+) diff --git

Re: [OE-core] Question for OE variable "LABELS"

Hi Jianxun, On 10/20/2016 04:51 AM, Jianxun Zhang wrote: The current OE document has this LABELS variable and OE has some code to support its usage. But if I just set LABELS in a BSP conf or local.conf file, the build will show the warning message: WARNING: core-image-minimal-1.0-r0

Re: [OE-core] meta-toolchain and meta-toolchain-qt for specific image

> > what is the advantage of such a recipe? The only "advantage" what made me using such a recipe was, that I want to have the normal toolchain AND the qt5 toolchain in one installation package together. When you know another way to get both together, I would be thankful if you tell me how to