Re: [OE-core] [PATCH v2] siteinfo: nios2-linux - remove wrong mutex info

2017-10-03 Thread Khem Raj
On Tue, Oct 3, 2017 at 7:25 PM, Marek Vasut wrote: > On 10/04/2017 04:01 AM, Andre McCurdy wrote: >> On Tue, Oct 3, 2017 at 2:54 PM, Juro Bystricky >> wrote: >>> With the commit f4e8e9242c5df095b52688b083df3c9d36e7144b >> >> That revision doesn't exist

Re: [OE-core] [PATCH v2] siteinfo: nios2-linux - remove wrong mutex info

2017-10-03 Thread Marek Vasut
On 10/04/2017 04:01 AM, Andre McCurdy wrote: > On Tue, Oct 3, 2017 at 2:54 PM, Juro Bystricky > wrote: >> With the commit f4e8e9242c5df095b52688b083df3c9d36e7144b > > That revision doesn't exist in oe-core... Also, isn't there some sort of standardized format for

Re: [OE-core] [PATCH v2] siteinfo: nios2-linux - remove wrong mutex info

2017-10-03 Thread Andre McCurdy
On Tue, Oct 3, 2017 at 2:54 PM, Juro Bystricky wrote: > With the commit f4e8e9242c5df095b52688b083df3c9d36e7144b That revision doesn't exist in oe-core... > some nios2 builds > (uboot, core-image-minimal, etc) were broken due to db trying to use ARM > instructions >

[OE-core] [PATCH] systemd: drop unreferenced uclibc specific agetty -> getty patch

2017-10-03 Thread Andre McCurdy
The patch is uclibc specific and reference to it was removed from the systemd recipe in: http://git.openembedded.org/openembedded-core/commit/?id=653704e9cf325cb494eb23facca19e9f05132ffd Signed-off-by: Andre McCurdy --- ...r-getty-to-agetty-in-console-setup-system.patch

Re: [OE-core] [PATCH] go-runtime: prevent host leakage into target objects

2017-10-03 Thread Saul Wold
On Fri, 2017-09-29 at 14:15 +, Matt Madison wrote: > When building for a target whose architecture matches > the build host's, the second pass through make.bash > to build the shareable runtime would also overwrite > the target's static cgo library with host-compatibile > binaries. > > Fix

Re: [OE-core] [PATCH] go-runtime: prevent host leakage into target objects

2017-10-03 Thread Wold, Saul
On Fri, 2017-09-29 at 14:15 +, Matt Madison wrote: > When building for a target whose architecture matches > the build host's, the second pass through make.bash > to build the shareable runtime would also overwrite > the target's static cgo library with host-compatibile > binaries. > > Fix

[OE-core] [PATCH v2] siteinfo: nios2-linux - remove wrong mutex info

2017-10-03 Thread Juro Bystricky
With the commit f4e8e9242c5df095b52688b083df3c9d36e7144b some nios2 builds (uboot, core-image-minimal, etc) were broken due to db trying to use ARM instructions in mutexes. The reason was db "configure" used the cached entry from nios2-linux (which was incorrect). So the remedy was to remove the

Re: [OE-core] [PATCH] siteinfo: nios2-linux - remove wrong mutex info

2017-10-03 Thread Marek Vasut
On 10/03/2017 10:44 PM, Bystricky, Juro wrote: > >> While I understand ARM/ is wrong, why is removing the db_cv_mutex a >> correct fix instead of ie. s/ARM/nios2/ ? The patch description does not >> explain that. > > With the relatively recent commit >

Re: [OE-core] [PATCH] siteinfo: nios2-linux - remove wrong mutex info

2017-10-03 Thread Bystricky, Juro
> While I understand ARM/ is wrong, why is removing the db_cv_mutex a > correct fix instead of ie. s/ARM/nios2/ ? The patch description does not > explain that. With the relatively recent commit

Re: [OE-core] [PATCH] siteinfo: nios2-linux - remove wrong mutex info

2017-10-03 Thread Marek Vasut
On 10/03/2017 09:51 PM, Juro Bystricky wrote: > This fixes broken nios2 builds that involve db recipes. While I understand ARM/ is wrong, why is removing the db_cv_mutex a correct fix instead of ie. s/ARM/nios2/ ? The patch description does not explain that. > Signed-off-by: Juro Bystricky

[OE-core] [PATCH] siteinfo: nios2-linux - remove wrong mutex info

2017-10-03 Thread Juro Bystricky
This fixes broken nios2 builds that involve db recipes. Signed-off-by: Juro Bystricky --- meta/site/nios2-linux | 1 - 1 file changed, 1 deletion(-) diff --git a/meta/site/nios2-linux b/meta/site/nios2-linux index 2f4e570..5bae748 100644 --- a/meta/site/nios2-linux

[OE-core] State of bitbake world, Failed tasks 2017-10-03

2017-10-03 Thread Martin Jansa
http://www.openembedded.org/wiki/Bitbake_World_Status == Number of issues - stats == {| class='wikitable' !|Date !!colspan='3'|Failed tasks !!|Signatures !!colspan='15'|QA !!Comment |- || ||qemuarm ||qemux86 ||qemux86_64 ||all ||already-stripped ||libdir ||textrel ||build-deps

[OE-core] Oddness regarding file locks in package.bbclass

2017-10-03 Thread Peter Kjellerstedt
I just stumbled upon something odd in package.bbclass. In commit ede381d5 from January 2011 (the code hasn't changed since), the use of the ${PACKAGELOCK} lock file was changed to shared to improve parallelism. However, when looking at the actual change it becomes confusing. I have included it

Re: [OE-core] [PATCH 0/2] busybox updating

2017-10-03 Thread Andre McCurdy
On Tue, Oct 3, 2017 at 8:38 AM, Andrej Valek wrote: > Update busybox to version 1.27.2 > Fix CVE-20177-5325 > > Changes: > - busybox: 1.24.1 -> 1.27.2: > - fixed link creation to shell > - reported bug with suid shells >

Re: [OE-core] [PATCH] Small improvement for the initscripts package

2017-10-03 Thread Alexander Kanavin
On 10/03/2017 06:03 PM, jef.drie...@niko.eu wrote: Burton, Ross [ross.bur...@intel.com] On 3 October 2017 at 11:03, wrote: Note: base-files-emperor is the package with the custom init scripts. I added: PROVIDES = "initscripts" And in conf/machine/emperor.conf, I added:

[OE-core] [PATCH 1/2] busybox: 1.24.1 -> 1.27.2

2017-10-03 Thread Andrej Valek
- fixed link creation to shell - reported bug with suid shells [https://bugs.busybox.net/show_bug.cgi?id=10346] - removed and modified already merged patches - updated defconfig regarding to new version Signed-off-by: Andrej Valek Signed-off-by: Radovan Scasny

[OE-core] [PATCH 0/2] busybox updating

2017-10-03 Thread Andrej Valek
Update busybox to version 1.27.2 Fix CVE-20177-5325 Changes: - busybox: 1.24.1 -> 1.27.2: - fixed link creation to shell - reported bug with suid shells [https://bugs.busybox.net/show_bug.cgi?id=10346] - removed and modified already merged patches - updated defconfig regarding to new

[OE-core] [PATCH 2/2] busybox: Fix CVE-2011-5325

2017-10-03 Thread Andrej Valek
Signed-off-by: Radovan Scasny Signed-off-by: Andrej Valek --- .../busybox/busybox/CVE-2011-5325.patch| 481 + meta/recipes-core/busybox/busybox_1.27.2.bb| 1 + 2 files changed, 482 insertions(+)

Re: [OE-core] [PATCH] Small improvement for the initscripts package

2017-10-03 Thread Jef.Driesen
Burton, Ross [ross.bur...@intel.com] > On 3 October 2017 at 11:03, wrote: >> Note: base-files-emperor is the package with the custom init scripts. I >> added: >> >> PROVIDES = "initscripts" >> >> And in conf/machine/emperor.conf, I added: >> >> PREFERRED_PROVIDER_initscripts

Re: [OE-core] [PATCH] Small improvement for the initscripts package

2017-10-03 Thread Burton, Ross
On 3 October 2017 at 11:03, wrote: > > Note: base-files-emperor is the package with the custom init scripts. I > added: > > PROVIDES = "initscripts" > > And in conf/machine/emperor.conf, I added: > > PREFERRED_PROVIDER_initscripts = "base-files-emperor" > If your

Re: [OE-core] [PATCH] Small improvement for the initscripts package

2017-10-03 Thread Jef.Driesen
> I'd definitely be curious as to where initscripts is coming from in the SDK. > You can use bitbake -g to generate dependency charts. There are quite some packages which depend on initscripts: $ bitbake -g image-sdk-niko -c populate_sdk NOTE: Started PRServer with DBfile:

Re: [OE-core] [PATCH] Small improvement for the initscripts package

2017-10-03 Thread Jef.Driesen
Alexander Kanavin: > You can use bbappend to instead replace the standard files with the ones > that you want installed. Or you can add PROVIDES = "initscripts" to your > recipe with the 'custom' initscripts, and set > PREFERRED_PROVIDER_initscripts = "my-custom-initscripts" to have that >

Re: [OE-core] [PATCH] dbus: 1.10.20 -> 1.10.22

2017-10-03 Thread Burton, Ross
Remember to upgrade dbus-test at the same time as otherwise you break dbus-test. Ross On 21 September 2017 at 08:46, Fan Xin wrote: > Upgrade dbus from 1.10.20 to 1.10.22 > > Signed-off-by: fan@jp.fujitsu.com > --- > meta/recipes-core/dbus/dbus_1.10.20.bb | 180 >

Re: [OE-core] [oe] [meta-java][PATCH] openjdk-8-common: Fix the issue of building failed adlc on host with gcc < 6

2017-10-03 Thread Andrew Goodbody
> -Original Message- > From: Fupan Li > > The patch recipes-core/openjdk/patches-openjdk-8/openjdk8-fix-adlc- > flags.patch > had tried to fix this issue, and it tried to filter out the > TARGET_FLAGS/TARGET_ > CXXFLGAS, but for the flags such as

[OE-core] [PATCH] staging.bbclass: handle postinst-useradd-* fixmes

2017-10-03 Thread Mikko Ylinen
After 02457ef7f600ce954874e2d11e74b1c6daaa3bfc, PSEUDO for postinst-useradd-* scripts get to use only one PSEUDO_LOCALSTATEDIR which is set under recipes ${WORKDIR}. When the those scripts are run in a clean build environment that is built from the sstate (populate_sysroot_setscene run for

Re: [OE-core] [PATCH 00/10] gstreamer1.0: upgrade to 1.12.3

2017-10-03 Thread Nicolas Dechesne
On Mon, Oct 2, 2017 at 3:05 PM, Burton, Ross wrote: > On 2 October 2017 at 21:49, Nicolas Dechesne > wrote: >> >> I have seen these patches on master-next at some point, and they got >> dropped. Was there any specific issue? > > > They were