[OE-core] [PATCH 1/1] openssl: fix do_configure error when cwd is not in @INC

[Robert Yang]

Fixed when building on Debian-testing:
| Can't locate find.pl in @INC (@INC contains: /etc/perl 
/usr/local/lib/x86_64-linux-gnu/perl/5.22.2 /usr/local/share/perl/5.22.2 
/usr/lib/x86_64-linux-gnu/perl5/5.22 /usr/share/perl5 
/usr/lib/x86_64-linux-gnu/perl/5.22 /usr/share/perl/5.22 
/usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base) at perlpath.pl 
line 7.

Signed-off-by: Robert Yang 
---
 .../openssl/openssl-util-perlpath.pl-cwd.patch | 34 ++
 .../recipes-connectivity/openssl/openssl_1.0.2h.bb |  1 +
 2 files changed, 35 insertions(+)
 create mode 100644 
meta/recipes-connectivity/openssl/openssl/openssl-util-perlpath.pl-cwd.patch

diff --git 
a/meta/recipes-connectivity/openssl/openssl/openssl-util-perlpath.pl-cwd.patch 
b/meta/recipes-connectivity/openssl/openssl/openssl-util-perlpath.pl-cwd.patch
new file mode 100644
index 000..065b9b1
--- /dev/null
+++ 
b/meta/recipes-connectivity/openssl/openssl/openssl-util-perlpath.pl-cwd.patch
@@ -0,0 +1,34 @@
+From e427748f3bb5d37e78dc8d70a558c373aa8ababb Mon Sep 17 00:00:00 2001
+From: Robert Yang 
+Date: Mon, 19 Sep 2016 22:06:28 -0700
+Subject: [PATCH] util/perlpath.pl: make it work when cwd is not in @INC
+
+Fixed when building on Debian-testing:
+| Can't locate find.pl in @INC (@INC contains: /etc/perl 
/usr/local/lib/x86_64-linux-gnu/perl/5.22.2 /usr/local/share/perl/5.22.2 
/usr/lib/x86_64-linux-gnu/perl5/5.22 /usr/share/perl5 
/usr/lib/x86_64-linux-gnu/perl/5.22 /usr/share/perl/5.22 
/usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base) at perlpath.pl 
line 7.
+
+The find.pl is added by oe-core, so once openssl/find.pl is removed,
+then this patch can be dropped.
+
+Upstream-Status: Inappropriate [OE-Specific]
+
+Signed-off-by: Robert Yang 
+---
+ util/perlpath.pl | 2 ++
+ 1 file changed, 2 insertions(+)
+
+diff --git a/util/perlpath.pl b/util/perlpath.pl
+index a1f236b..5599892 100755
+--- a/util/perlpath.pl
 b/util/perlpath.pl
+@@ -4,6 +4,8 @@
+ # line in all scripts that rely on perl.
+ #
+ 
++BEGIN { unshift @INC, "."; }
++
+ require "find.pl";
+ 
+ $#ARGV == 0 || print STDERR "usage: perlpath newpath  (eg /usr/bin)\n";
+-- 
+2.9.0
+
diff --git a/meta/recipes-connectivity/openssl/openssl_1.0.2h.bb 
b/meta/recipes-connectivity/openssl/openssl_1.0.2h.bb
index 4f91e55..c8444d3 100644
--- a/meta/recipes-connectivity/openssl/openssl_1.0.2h.bb
+++ b/meta/recipes-connectivity/openssl/openssl_1.0.2h.bb
@@ -41,6 +41,7 @@ SRC_URI += "file://find.pl;subdir=${BP}/util/ \
 file://parallel.patch \
 file://CVE-2016-2177.patch \
 file://CVE-2016-2178.patch \
+file://openssl-util-perlpath.pl-cwd.patch \
"
 SRC_URI[md5sum] = "9392e65072ce4b614c1392eefc1f23d0"
 SRC_URI[sha256sum] = 
"1d4007e53aad94a5b2002fe045ee7bb0b3d98f1a47f8b2bc851dcd1c74332919"
-- 
2.9.0

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

[OE-core] [PATCH 0/1] openssl: fix do_configure error when cwd is not in @INC

[Robert Yang]

The following changes since commit 5ac0604fdc7d5b783011c43d476210b427b5dae0:

  build-appliance-image: Create image in correct location (2016-09-19 08:58:04 
+0100)

are available in the git repository at:

  git://git.openembedded.org/openembedded-core-contrib rbt/openssl
  
http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=rbt/openssl

Robert Yang (1):
  openssl: fix do_configure error when cwd is not in @INC

 .../openssl/openssl-util-perlpath.pl-cwd.patch | 34 ++
 .../recipes-connectivity/openssl/openssl_1.0.2h.bb |  1 +
 2 files changed, 35 insertions(+)
 create mode 100644 
meta/recipes-connectivity/openssl/openssl/openssl-util-perlpath.pl-cwd.patch

-- 
2.9.0

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [PATCH V2 1/1] kernel.bbclass: Add kernel_version_sanity_check function

[Bruce Ashfield]

On Mon, Sep 19, 2016 at 8:03 PM, Bruce Ashfield 
wrote:

>
>
> On Mon, Sep 19, 2016 at 7:02 PM, Cal Sullivan <
> california.l.sulli...@intel.com> wrote:
>
>>
>>
>> On 09/19/2016 03:55 PM, Bruce Ashfield wrote:
>>
>>
>>
>> On Mon, Sep 19, 2016 at 6:02 PM, Cal Sullivan <
>> california.l.sulli...@intel.com> wrote:
>>
>>> I don't have time to smoke test a SRCREV update for so many machines
>>> right now, so I think for now I will just set the correct PV in the various
>>> linux-yocto recipes so we don't block master-next builds.
>>>
>>> Is this acceptable?
>>>
>>
>> In the linux-yocto bbappends of the various layers ? I keep track of the
>> PV's in the
>> core recipes themselves, so they shouldn't need to be modified.
>>
>> You're right. Only the linux-yocto bbappends in meta-yocto-bsp need
>> MACHINE-specific PVs right now.
>> The issue with 4.1 (used by lsb right now) in oe-core is that
>> LINUX_VERSION was bumped to 4.1.32 rather than 4.1.31 in error.
>>
>
> I'll take care of that part in a few hours. Since I've been testing the
> SRCREVs, I'll double
> check and tweak it as need be.
>

Strangely I had merged 4.1.32 (the tag was present), but I didn't update
the machine
SRCREVs to match.

I was integrating 4.8-rc7 (and preempt-rt) today, so I've merged the 4.1.32
tag, and will
send it along with my series on Tuesday morning.

Bruce


>
> Bruce
>
>
>>
>> ---
>> Cal
>>
>>
>>
>> Bruce
>>
>>
>>>
>>> Thanks,
>>> Cal
>>>
>>>
>>> On 09/19/2016 01:49 PM, Saul Wold wrote:
>>>
 On Mon, 2016-09-19 at 15:55 -0400, Bruce Ashfield wrote:

> On 2016-09-19 03:53 PM, Cal Sullivan wrote:
>
>> Yep, these all have incorrect PVs.
>> 628bf62756 Merge tag 'v4.4.11' into standard/base
>> The problem seems fairly wide spread.
>>
>> Bruce, do you suggest updating PVs or updating the SRCREVs (is
>> there a
>> good reason to keep using old SRCREVs?)?
>>
> Updating the SRCREVs is the right thing to do to sync them up now.
>
> but ..
>
> at the same time, they should probably have their own PVs, since
> next time up update 4.4.x, they'll fall out of sync and fail again.
>
> +1, I think that these need their own PV since they also don't update
 as fast as the base qemu recipes do.

 Sau!

 We want them to be aligned with the latest -stable, but we also
> don't need failures every time I push a new SRCREV and update the
> PV of the base recipe.
>
> Bruce
>
>
>> ---
>> Cal
>>
>>
>> On 09/19/2016 11:54 AM, Burton, Ross wrote:
>>
>>>
>>> On 19 September 2016 at 18:05, Cal Sullivan
>>> >> > wrote:
>>>
>>>  It looks like the function is doing as its supposed to, and
>>> we
>>>  need to update some PVs or SRCREVs to match PVs.
>>>
>>>  E.g., on the error below, SRCREV d6237b3b24 is indeed 4.1.31.
>>>
>>>
>>> And some more builders failed with 4.4:
>>>
>>> ERROR: linux-yocto-4.4.20+gitAUTOINC+e66032e2d9_628bf62756-r0
>>> do_kernel_version_sanity_check: Package Version
>>> (4.4.20+gitAUTOINC+e66032e2d9_628bf62756) does not match of
>>> kernel
>>> being built (4.4.11). Please update the PV variable to match the
>>> kernel source.
>>> ERROR: linux-yocto-4.4.20+gitAUTOINC+e66032e2d9_628bf62756-r0
>>> do_kernel_version_sanity_check: Function failed:
>>> do_kernel_version_sanity_check (log file is located at
>>> /home/pokybuild/yocto-autobuilder/yocto-worker/nightly-
>>> arm/build/build/tmp/work/beaglebone-poky-linux-gnueabi/linux-
>>> yocto/4.4.20+gitAUTOINC+e66032e2d9_628bf62756-
>>> r0/temp/log.do_kernel_version_sanity_check.30210)
>>> NOTE: recipe usbutils-008-r0: task do_fetch: Started
>>> ERROR: Logfile of failure stored in:
>>> /home/pokybuild/yocto-autobuilder/yocto-worker/nightly-
>>> arm/build/build/tmp/work/beaglebone-poky-linux-gnueabi/linux-
>>> yocto/4.4.20+gitAUTOINC+e66032e2d9_628bf62756-
>>> r0/temp/log.do_kernel_version_sanity_check.30210
>>> ERROR: Task
>>> (/home/pokybuild/yocto-autobuilder/yocto-worker/nightly-
>>> arm/build/meta/recipes-kernel/linux/linux-
>>> yocto_4.4.bb:do_kernel_version_sanity_check)
>>> failed with exit code '1'
>>>
>>> (ditto for ppc and x86)
>>>
>>> Ross
>>>
>>
>>> --
>>> ___
>>> Openembedded-core mailing list
>>> Openembedded-core@lists.openembedded.org
>>> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>>>
>>
>>
>>
>> --
>> "Thou shalt not follow the NULL pointer, for chaos and madness await thee
>> at its end"
>>
>>
>>
>
>
> --
> "Thou shalt not follow the NULL pointer, for chaos and madness await thee
> at its end"
>



-- 
"Thou shalt not follow the NULL pointer, for chaos and madness await thee
at its end"
-- 

Re: [OE-core] [OE-Core][Patch] arch-mips: Restructure mips64 and add mips64r2

[Robert Yang]

Hi,

It seems that this one causes build failures on qemumips64 + multilib:

config:
http://autobuilder.yocto.io:8010/builders/nightly-multilib/builds/64/steps/CreateAutoConf_5/logs/stdio

error:
http://autobuilder.yocto.io:8010/builders/nightly-multilib/builds/64/steps/BuildImages_5/logs/stdio

ERROR:  OE-core's config sanity checker detected a potential misconfiguration.
Either fix the cause of this error or at your own risk disable the checker 
(see sanity.conf).

Following is the list of potential problems / advisories:

Toolchain tunings invalid:
Tuning 'mips32r2' has no defined features, and cannot be used.

// Robert

On 09/19/2016 07:14 PM, Zubair Lutfullah Kakakhel wrote:

The current file structure felt slightly unsuitable for adding
MIPS64r2. So I restructured it slightly and added MIPS64r2
support

Signed-off-by: Zubair Lutfullah Kakakhel 
---
 meta/conf/machine/include/mips/arch-mips.inc | 60 
 meta/conf/machine/include/tune-mips32.inc| 22 +++-
 meta/conf/machine/include/tune-mips64.inc| 80 +-
 meta/conf/machine/include/tune-mips64r2.inc  | 84 
 4 files changed, 184 insertions(+), 62 deletions(-)
 create mode 100644 meta/conf/machine/include/tune-mips64r2.inc

diff --git a/meta/conf/machine/include/mips/arch-mips.inc 
b/meta/conf/machine/include/mips/arch-mips.inc
index d3e83d1..6be84be 100644
--- a/meta/conf/machine/include/mips/arch-mips.inc
+++ b/meta/conf/machine/include/mips/arch-mips.inc
@@ -42,64 +42,4 @@ MIPSPKGSFX_ABI = "${@bb.utils.contains('TUNE_FEATURES', 'n32', 
'-n32', '', d)}"
 TUNE_ARCH = "mips${MIPSPKGSFX_BYTE}${MIPSPKGSFX_ENDIAN}"
 TUNE_PKGARCH = 
"${MIPSPKGSFX_VARIANT_tune-${DEFAULTTUNE}}${MIPSPKGSFX_FPU}${MIPSPKGSFX_ABI}"

-# Base tunes
-AVAILTUNES += "mips mips64-n32 mips64 mipsel mips64el-n32 mips64el mips-nf 
mips64-nf-n32 mips64-nf mipsel-nf mips64el-nf-n32 mips64el-nf"
-TUNE_FEATURES_tune-mips = "o32 bigendian fpu-hard"
-BASE_LIB_tune-mips = "lib"
-MIPSPKGSFX_VARIANT_tune-mips = "${TUNE_ARCH}"
-PACKAGE_EXTRA_ARCHS_tune-mips = "mips"

-TUNE_FEATURES_tune-mips64-n32 = "n32 bigendian fpu-hard"
-BASE_LIB_tune-mips64-n32 = "lib32"
-MIPSPKGSFX_VARIANT_tune-mips64-n32 = "${TUNE_ARCH}"
-PACKAGE_EXTRA_ARCHS_tune-mips64-n32 = "mips64-n32"
-
-TUNE_FEATURES_tune-mips64 = "n64 bigendian fpu-hard"
-BASE_LIB_tune-mips64 = "lib64"
-MIPSPKGSFX_VARIANT_tune-mips64 = "${TUNE_ARCH}"
-PACKAGE_EXTRA_ARCHS_tune-mips64 = "mips64"
-
-TUNE_FEATURES_tune-mipsel = "o32 fpu-hard"
-BASE_LIB_tune-mipsel = "lib"
-MIPSPKGSFX_VARIANT_tune-mipsel = "${TUNE_ARCH}"
-PACKAGE_EXTRA_ARCHS_tune-mipsel = "mipsel"
-
-TUNE_FEATURES_tune-mips64el-n32 = "n32 fpu-hard"
-BASE_LIB_tune-mips64el-n32 = "lib32"
-MIPSPKGSFX_VARIANT_tune-mips64el-n32 = "${TUNE_ARCH}"
-PACKAGE_EXTRA_ARCHS_tune-mips64el-n32 = "mips64el-n32"
-
-TUNE_FEATURES_tune-mips64el = "n64 fpu-hard"
-BASE_LIB_tune-mips64el = "lib64"
-MIPSPKGSFX_VARIANT_tune-mips64el = "${TUNE_ARCH}"
-PACKAGE_EXTRA_ARCHS_tune-mips64el = "mips64el"
-
-TUNE_FEATURES_tune-mips-nf = "o32 bigendian"
-BASE_LIB_tune-mips-nf = "lib"
-MIPSPKGSFX_VARIANT_tune-mips-nf = "${TUNE_ARCH}"
-PACKAGE_EXTRA_ARCHS_tune-mips-nf = "mips-nf"
-
-TUNE_FEATURES_tune-mips64-nf-n32 = "n32 bigendian"
-BASE_LIB_tune-mips64-nf-n32 = "lib32"
-MIPSPKGSFX_VARIANT_tune-mips64-nf-n32 = "${TUNE_ARCH}"
-PACKAGE_EXTRA_ARCHS_tune-mips64-nf-n32 = "mips64-nf-n32"
-
-TUNE_FEATURES_tune-mips64-nf = "n64 bigendian"
-BASE_LIB_tune-mips64-nf = "lib64"
-MIPSPKGSFX_VARIANT_tune-mips64-nf = "${TUNE_ARCH}"
-PACKAGE_EXTRA_ARCHS_tune-mips64-nf = "mips64-nf"
-
-TUNE_FEATURES_tune-mipsel-nf = "o32"
-BASE_LIB_tune-mipsel-nf = "lib"
-MIPSPKGSFX_VARIANT_tune-mipsel-nf = "${TUNE_ARCH}"
-PACKAGE_EXTRA_ARCHS_tune-mipsel-nf = "mipsel-nf"
-
-TUNE_FEATURES_tune-mips64el-nf-n32 = "n32"
-BASE_LIB_tune-mips64el-nf-n32 = "lib32"
-MIPSPKGSFX_VARIANT_tune-mips64el-nf-n32 = "${TUNE_ARCH}"
-PACKAGE_EXTRA_ARCHS_tune-mips64el-nf-n32 = "mips64el-nf-n32"
-
-TUNE_FEATURES_tune-mips64el-nf = "n64"
-BASE_LIB_tune-mips64el-nf = "lib64"
-MIPSPKGSFX_VARIANT_tune-mips64el-nf = "${TUNE_ARCH}"
-PACKAGE_EXTRA_ARCHS_tune-mips64el-nf = "mips64el-nf"
diff --git a/meta/conf/machine/include/tune-mips32.inc 
b/meta/conf/machine/include/tune-mips32.inc
index ce0445f..4c3d93f 100644
--- a/meta/conf/machine/include/tune-mips32.inc
+++ b/meta/conf/machine/include/tune-mips32.inc
@@ -6,7 +6,27 @@ TUNEVALID[mips32] = "Enable mips32 specific processor 
optimizations"
 TUNECONFLICTS[mips32] = "n64 n32"
 TUNE_CCARGS .= "${@bb.utils.contains('TUNE_FEATURES', 'mips32', ' -march=mips32', 
'', d)}"

-AVAILTUNES += "mips32 mips32el mips32-nf mips32el-nf"
+AVAILTUNES += "mips mipsel mips-nf mipsel-nf mips32 mips32el mips32-nf 
mips32el-nf"
+
+TUNE_FEATURES_tune-mips = "o32 bigendian fpu-hard"
+BASE_LIB_tune-mips = "lib"
+MIPSPKGSFX_VARIANT_tune-mips = "${TUNE_ARCH}"
+PACKAGE_EXTRA_ARCHS_tune-mips = "mips"
+
+TUNE_FEATURES_tune-mipsel = "o32 fpu-hard"

Re: [OE-core] [PATCH v2] libunwind: add aarch64 support

[ChenQi]

On 09/26/2014 05:59 PM, Fathi Boudra wrote:

* pass --enable-debug-frame on aarch64 architecture


Hi Fathi,

I'm now dealing with a problem related to libunwind support on aarch64.
Could you please tell me why '--enable-debug-frame' is needed for aarch64?

Best Regards,
Chen Qi


* include patches:
   - aarch64 port (backported from upstream)
   - Support-building-with-older-compilers (fix undefined reference to
 `unreachable' on older compilers)

Signed-off-by: Fathi Boudra 
---
  .../libunwind/libunwind-1.1/AArch64-port.patch | 2529 
  .../Support-building-with-older-compilers.patch|   72 +
  meta/recipes-support/libunwind/libunwind.inc   |1 +
  meta/recipes-support/libunwind/libunwind_1.1.bb|5 +
  4 files changed, 2607 insertions(+)
  create mode 100644 
meta/recipes-support/libunwind/libunwind-1.1/AArch64-port.patch
  create mode 100644 
meta/recipes-support/libunwind/libunwind-1.1/Support-building-with-older-compilers.patch

diff --git a/meta/recipes-support/libunwind/libunwind-1.1/AArch64-port.patch 
b/meta/recipes-support/libunwind/libunwind-1.1/AArch64-port.patch
new file mode 100644
index 000..228ec32
--- /dev/null
+++ b/meta/recipes-support/libunwind/libunwind-1.1/AArch64-port.patch
@@ -0,0 +1,2529 @@
+From ac6c0a6535975f1dc2da6e4e2766614baac2a14a Mon Sep 17 00:00:00 2001
+From: Yvan Roux 
+Date: Sat, 11 May 2013 09:18:23 -0600
+Subject: [PATCH] AArch64 port.
+
+Upstream-Status: Backport
+
+---
+ Makefile.am  |6
+ README   |1
+ configure.ac |6
+ include/libunwind-aarch64.h  |  187 ++
+ include/libunwind.h.in   |4
+ include/tdep-aarch64/dwarf-config.h  |   52 ++
+ include/tdep-aarch64/jmpbuf.h|   33 +++
+ include/tdep-aarch64/libunwind_i.h   |  294 
+++
+ include/tdep/dwarf-config.h  |4
+ include/tdep/jmpbuf.h|2
+ include/tdep/libunwind_i.h.in|4
+ src/Makefile.am  |   39 
+ src/aarch64/Gcreate_addr_space.c |   60 +++
+ src/aarch64/Gget_proc_info.c |   39 
+ src/aarch64/Gget_save_loc.c  |  100 +++
+ src/aarch64/Gglobal.c|   57 ++
+ src/aarch64/Ginit.c  |  187 ++
+ src/aarch64/Ginit_local.c|   55 ++
+ src/aarch64/Ginit_remote.c   |   45 +
+ src/aarch64/Gis_signal_frame.c   |   64 +++
+ src/aarch64/Gregs.c  |  113 +
+ src/aarch64/Gresume.c|  177 +
+ src/aarch64/Gstep.c  |  129 +++
+ src/aarch64/Lcreate_addr_space.c |5
+ src/aarch64/Lget_proc_info.c |5
+ src/aarch64/Lget_save_loc.c  |5
+ src/aarch64/Lglobal.c|5
+ src/aarch64/Linit.c  |5
+ src/aarch64/Linit_local.c|5
+ src/aarch64/Linit_remote.c   |5
+ src/aarch64/Lis_signal_frame.c   |5
+ src/aarch64/Lregs.c  |5
+ src/aarch64/Lresume.c|5
+ src/aarch64/Lstep.c  |5
+ src/aarch64/gen-offsets.c|   68 
+ src/aarch64/init.h   |  127 +++
+ src/aarch64/is_fpreg.c   |   32 +++
+ src/aarch64/offsets.h|   49 +
+ src/aarch64/regname.c|  106 
+ src/aarch64/siglongjmp.S |   12 +
+ src/aarch64/unwind_i.h   |   43 +
+ src/coredump/_UCD_access_reg_linux.c |5
+ src/ptrace/_UPT_reg_offset.c |   36 
+ 43 files changed, 2184 insertions(+), 7 deletions(-)
+ create mode 100644 include/libunwind-aarch64.h
+ create mode 100644 include/tdep-aarch64/dwarf-config.h
+ create mode 100644 include/tdep-aarch64/jmpbuf.h
+ create mode 100644 include/tdep-aarch64/libunwind_i.h
+ create mode 100644 src/aarch64/Gcreate_addr_space.c
+ create mode 100644 src/aarch64/Gget_proc_info.c
+ create mode 100644 src/aarch64/Gget_save_loc.c
+ create mode 100644 src/aarch64/Gglobal.c
+ create mode 100644 src/aarch64/Ginit.c
+ create mode 100644 src/aarch64/Ginit_local.c
+ create mode 100644 src/aarch64/Ginit_remote.c
+ create mode 100644 src/aarch64/Gis_signal_frame.c
+ create mode 100644 src/aarch64/Gregs.c
+ create mode 100644 src/aarch64/Gresume.c
+ create mode 100644 src/aarch64/Gstep.c
+ create mode 100644 src/aarch64/Lcreate_addr_space.c
+ create mode 100644 src/aarch64/Lget_proc_info.c
+ create mode 100644 src/aarch64/Lget_save_loc.c
+ create mode 100644 src/aarch64/Lglobal.c
+ create mode 100644 src/aarch64/Linit.c
+ create mode 100644 src/aarch64/Linit_local.c
+ create mode 100644 src/aarch64/Linit_remote.c
+ create mode 100644 src/aarch64/Lis_signal_frame.c
+ create mode 100644 src/aarch64/Lregs.c
+ create mode 100644 

Re: [OE-core] [PATCH][v5] watchdog: enable systemd support

[Huang, Jie (Jackie)]

Ping.

> -Original Message-
> From: openembedded-core-boun...@lists.openembedded.org 
> [mailto:openembedded-core-
> boun...@lists.openembedded.org] On Behalf Of jackie.hu...@windriver.com
> Sent: Monday, September 12, 2016 1:01 PM
> To: openembedded-core@lists.openembedded.org
> Subject: [OE-core] [PATCH][v5] watchdog: enable systemd support
> 
> From: Roy Li 
> 
> 1. inherit systemd, and add two unit files which are from Fedora 23
> 2. auto load soft dog kernel module
> 
> Signed-off-by: Roy Li 
> Signed-off-by: Robert Yang 
> Signed-off-by: Jackie Huang 
> ---
>  .../watchdog/watchdog/watchdog-ping.service   | 11 +++
>  .../watchdog/watchdog/watchdog.service| 11 +++
>  meta/recipes-extended/watchdog/watchdog_5.15.bb   | 19 
> +--
>  3 files changed, 39 insertions(+), 2 deletions(-)
>  create mode 100644 
> meta/recipes-extended/watchdog/watchdog/watchdog-ping.service
>  create mode 100644 meta/recipes-extended/watchdog/watchdog/watchdog.service
> 
> diff --git a/meta/recipes-extended/watchdog/watchdog/watchdog-ping.service 
> b/meta/recipes-
> extended/watchdog/watchdog/watchdog-ping.service
> new file mode 100644
> index 000..44bac9d
> --- /dev/null
> +++ b/meta/recipes-extended/watchdog/watchdog/watchdog-ping.service
> @@ -0,0 +1,11 @@
> +[Unit]
> +Description=watchdog daemon for use with ping test / network dependency
> +After=network.target
> +Conflicts=watchdog.service
> +
> +[Service]
> +Type=forking
> +ExecStart=@SBINDIR@/watchdog
> +
> +[Install]
> +WantedBy=multi-user.target
> diff --git a/meta/recipes-extended/watchdog/watchdog/watchdog.service 
> b/meta/recipes-
> extended/watchdog/watchdog/watchdog.service
> new file mode 100644
> index 000..c5faa4e
> --- /dev/null
> +++ b/meta/recipes-extended/watchdog/watchdog/watchdog.service
> @@ -0,0 +1,11 @@
> +[Unit]
> +Description=watchdog daemon
> +# man systemd.special
> +# auto added After=basic.target
> +
> +[Service]
> +Type=forking
> +ExecStart=@SBINDIR@/watchdog
> +
> +[Install]
> +WantedBy=multi-user.target
> diff --git a/meta/recipes-extended/watchdog/watchdog_5.15.bb b/meta/recipes-
> extended/watchdog/watchdog_5.15.bb
> index cedfc04..826e31f 100644
> --- a/meta/recipes-extended/watchdog/watchdog_5.15.bb
> +++ b/meta/recipes-extended/watchdog/watchdog_5.15.bb
> @@ -13,6 +13,8 @@ SRC_URI = 
> "${SOURCEFORGE_MIRROR}/watchdog/watchdog-${PV}.tar.gz \
> file://watchdog-init.patch \
> file://watchdog-conf.patch \
> file://wd_keepalive.init \
> +   file://watchdog-ping.service \
> +   file://watchdog.service \
>  "
> 
>  SRC_URI[md5sum] = "678c32f6f35a0492c9c1b76b4aa88828"
> @@ -22,7 +24,7 @@ UPSTREAM_CHECK_URI =
> "http://sourceforge.net/projects/watchdog/files/watchdog/;
>  UPSTREAM_CHECK_REGEX = "/watchdog/(?P(\d+[\.\-_]*)+)/"
> 
>  inherit autotools
> -inherit update-rc.d
> +inherit update-rc.d systemd
> 
>  DEPENDS_append_libc-musl = " libtirpc "
>  CFLAGS_append_libc-musl = " -I${STAGING_INCDIR}/tirpc "
> @@ -37,16 +39,29 @@ INITSCRIPT_PARAMS_${PN} = "start 15 1 2 3 4 5 . stop 85 0 
> 6 ."
>  INITSCRIPT_NAME_${PN}-keepalive = "wd_keepalive"
>  INITSCRIPT_PARAMS_${PN}-keepalive = "start 15 1 2 3 4 5 . stop 85 0 6 ."
> 
> +SYSTEMD_SERVICE_${PN} = "watchdog.service"
> +
>  do_install_append() {
> - install -D ${S}/redhat/watchdog.init 
> ${D}/${sysconfdir}/init.d/watchdog.sh
> +install -D ${S}/redhat/watchdog.init 
> ${D}/${sysconfdir}/init.d/watchdog.sh
>  install -Dm 0755 ${WORKDIR}/wd_keepalive.init 
> ${D}${sysconfdir}/init.d/wd_keepalive
> 
>  # watchdog.conf is provided by the watchdog-config recipe
>  rm ${D}${sysconfdir}/watchdog.conf
> +
> +install -d ${D}${systemd_system_unitdir}
> +install -m 0644 ${WORKDIR}/watchdog*.service 
> ${D}${systemd_system_unitdir}
> +
> +if ${@bb.utils.contains('DISTRO_FEATURES','systemd','true','false',d)}; 
> then
> +install -d ${D}${sysconfdir}/modules-load.d
> +echo "softdog" > ${D}${sysconfdir}/modules-load.d/softdog.conf
> +sed -i -e 's,@SBINDIR@,${sbindir},g' 
> ${D}${systemd_system_unitdir}/*.service
> +fi
>  }
> 
>  PACKAGES =+ "${PN}-keepalive"
> 
> +FILES_${PN} += "${systemd_system_unitdir}/*"
> +
>  FILES_${PN}-keepalive = " \
>  ${sysconfdir}/init.d/wd_keepalive \
>  ${sbindir}/wd_keepalive \
> --
> 2.8.1
> 
> --
> ___
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [PATCH] default-distrovars.inc: remove libidn from LGPLv2_WHITELIST_GPL-3.0

[Huang, Jie (Jackie)]

Ping.

> -Original Message-
> From: openembedded-core-boun...@lists.openembedded.org 
> [mailto:openembedded-core-
> boun...@lists.openembedded.org] On Behalf Of jackie.hu...@windriver.com
> Sent: Thursday, September 01, 2016 10:48 AM
> To: openembedded-core@lists.openembedded.org
> Subject: [OE-core] [PATCH] default-distrovars.inc: remove libidn from 
> LGPLv2_WHITELIST_GPL-3.0
> 
> From: Jackie Huang 
> 
> The libidn recipe is now buildable in distros which blacklist
> GPL-3.0 without needing to be explicitly whitelisted (since it
> provides at least one non GPLv3 package).
> 
> Signed-off-by: Jackie Huang 
> ---
>  meta/conf/distro/include/default-distrovars.inc | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/meta/conf/distro/include/default-distrovars.inc 
> b/meta/conf/distro/include/default-
> distrovars.inc
> index fac4deb..f7ed943 100644
> --- a/meta/conf/distro/include/default-distrovars.inc
> +++ b/meta/conf/distro/include/default-distrovars.inc
> @@ -23,7 +23,7 @@ DISTRO_FEATURES ?= "${DISTRO_FEATURES_DEFAULT}
> ${DISTRO_FEATURES_LIBC}"
>  IMAGE_FEATURES ?= ""
> 
>  WHITELIST_GPL-3.0 ?= ""
> -LGPLv2_WHITELIST_GPL-3.0 ?= "libidn"
> +LGPLv2_WHITELIST_GPL-3.0 ?= ""
> 
>  COMMERCIAL_AUDIO_PLUGINS ?= ""
>  # COMMERCIAL_AUDIO_PLUGINS ?= "gst-plugins-ugly-mad 
> gst-plugins-ugly-mpegaudioparse"
> --
> 2.8.1
> 
> --
> ___
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [PATCH V2 1/1] kernel.bbclass: Add kernel_version_sanity_check function

[Bruce Ashfield]

On Mon, Sep 19, 2016 at 7:02 PM, Cal Sullivan <
california.l.sulli...@intel.com> wrote:

>
>
> On 09/19/2016 03:55 PM, Bruce Ashfield wrote:
>
>
>
> On Mon, Sep 19, 2016 at 6:02 PM, Cal Sullivan <
> california.l.sulli...@intel.com> wrote:
>
>> I don't have time to smoke test a SRCREV update for so many machines
>> right now, so I think for now I will just set the correct PV in the various
>> linux-yocto recipes so we don't block master-next builds.
>>
>> Is this acceptable?
>>
>
> In the linux-yocto bbappends of the various layers ? I keep track of the
> PV's in the
> core recipes themselves, so they shouldn't need to be modified.
>
> You're right. Only the linux-yocto bbappends in meta-yocto-bsp need
> MACHINE-specific PVs right now.
> The issue with 4.1 (used by lsb right now) in oe-core is that
> LINUX_VERSION was bumped to 4.1.32 rather than 4.1.31 in error.
>

I'll take care of that part in a few hours. Since I've been testing the
SRCREVs, I'll double
check and tweak it as need be.

Bruce


>
> ---
> Cal
>
>
>
> Bruce
>
>
>>
>> Thanks,
>> Cal
>>
>>
>> On 09/19/2016 01:49 PM, Saul Wold wrote:
>>
>>> On Mon, 2016-09-19 at 15:55 -0400, Bruce Ashfield wrote:
>>>
 On 2016-09-19 03:53 PM, Cal Sullivan wrote:

> Yep, these all have incorrect PVs.
> 628bf62756 Merge tag 'v4.4.11' into standard/base
> The problem seems fairly wide spread.
>
> Bruce, do you suggest updating PVs or updating the SRCREVs (is
> there a
> good reason to keep using old SRCREVs?)?
>
 Updating the SRCREVs is the right thing to do to sync them up now.

 but ..

 at the same time, they should probably have their own PVs, since
 next time up update 4.4.x, they'll fall out of sync and fail again.

 +1, I think that these need their own PV since they also don't update
>>> as fast as the base qemu recipes do.
>>>
>>> Sau!
>>>
>>> We want them to be aligned with the latest -stable, but we also
 don't need failures every time I push a new SRCREV and update the
 PV of the base recipe.

 Bruce


> ---
> Cal
>
>
> On 09/19/2016 11:54 AM, Burton, Ross wrote:
>
>>
>> On 19 September 2016 at 18:05, Cal Sullivan
>> > > wrote:
>>
>>  It looks like the function is doing as its supposed to, and
>> we
>>  need to update some PVs or SRCREVs to match PVs.
>>
>>  E.g., on the error below, SRCREV d6237b3b24 is indeed 4.1.31.
>>
>>
>> And some more builders failed with 4.4:
>>
>> ERROR: linux-yocto-4.4.20+gitAUTOINC+e66032e2d9_628bf62756-r0
>> do_kernel_version_sanity_check: Package Version
>> (4.4.20+gitAUTOINC+e66032e2d9_628bf62756) does not match of
>> kernel
>> being built (4.4.11). Please update the PV variable to match the
>> kernel source.
>> ERROR: linux-yocto-4.4.20+gitAUTOINC+e66032e2d9_628bf62756-r0
>> do_kernel_version_sanity_check: Function failed:
>> do_kernel_version_sanity_check (log file is located at
>> /home/pokybuild/yocto-autobuilder/yocto-worker/nightly-
>> arm/build/build/tmp/work/beaglebone-poky-linux-gnueabi/linux-
>> yocto/4.4.20+gitAUTOINC+e66032e2d9_628bf62756-
>> r0/temp/log.do_kernel_version_sanity_check.30210)
>> NOTE: recipe usbutils-008-r0: task do_fetch: Started
>> ERROR: Logfile of failure stored in:
>> /home/pokybuild/yocto-autobuilder/yocto-worker/nightly-
>> arm/build/build/tmp/work/beaglebone-poky-linux-gnueabi/linux-
>> yocto/4.4.20+gitAUTOINC+e66032e2d9_628bf62756-
>> r0/temp/log.do_kernel_version_sanity_check.30210
>> ERROR: Task
>> (/home/pokybuild/yocto-autobuilder/yocto-worker/nightly-
>> arm/build/meta/recipes-kernel/linux/linux-
>> yocto_4.4.bb:do_kernel_version_sanity_check)
>> failed with exit code '1'
>>
>> (ditto for ppc and x86)
>>
>> Ross
>>
>
>> --
>> ___
>> Openembedded-core mailing list
>> Openembedded-core@lists.openembedded.org
>> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>>
>
>
>
> --
> "Thou shalt not follow the NULL pointer, for chaos and madness await thee
> at its end"
>
>
>


-- 
"Thou shalt not follow the NULL pointer, for chaos and madness await thee
at its end"
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

[OE-core] [PATCH 1/1] linux-yocto*: Set MACHINE-specific LINUX_VERSION variables

[California Sullivan]

Some machines move to new kernel versions slower, making the catch-all
LINUX_VERSION variable inaccurate. This mismatch is a security concern
and with 5df5974d53f88a85b2bb789708b86049b091e3aa becomes a build time
error.

Fix this by setting each MACHINE's LINUX_VERSION to the kernel version
each MACHINE builds.

Signed-off-by: California Sullivan 
---
 meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.1.bbappend | 3 +++
 meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.4.bbappend | 3 +++
 2 files changed, 6 insertions(+)

diff --git a/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.1.bbappend 
b/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.1.bbappend
index 6dd173b..10a9ce0 100644
--- a/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.1.bbappend
+++ b/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.1.bbappend
@@ -21,3 +21,6 @@ COMPATIBLE_MACHINE_mpc8315e-rdb = "mpc8315e-rdb"
 
 LINUX_VERSION_genericx86 = "4.1.30"
 LINUX_VERSION_genericx86-64 = "4.1.30"
+LINUX_VERSION_edgerouter = "4.1.24"
+LINUX_VERSION_beaglebone = "4.1.24"
+LINUX_VERSION_mcp8315e-rdb = "4.1.24"
diff --git a/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.4.bbappend 
b/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.4.bbappend
index 4a7f7e2..6d9cd8d 100644
--- a/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.4.bbappend
+++ b/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.4.bbappend
@@ -21,3 +21,6 @@ COMPATIBLE_MACHINE_mpc8315e-rdb = "mpc8315e-rdb"
 
 LINUX_VERSION_genericx86 = "4.4.18"
 LINUX_VERSION_genericx86-64 = "4.4.18"
+LINUX_VERSION_edgerouter = "4.4.11"
+LINUX_VERSION_beaglebone = "4.4.11"
+LINUX_VERSION_mpc8315e-rdb = "4.4.11"
-- 
2.5.5

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [PATCH V2 1/1] kernel.bbclass: Add kernel_version_sanity_check function

[Cal Sullivan]

On 09/19/2016 03:55 PM, Bruce Ashfield wrote:



On Mon, Sep 19, 2016 at 6:02 PM, Cal Sullivan 
> wrote:


I don't have time to smoke test a SRCREV update for so many
machines right now, so I think for now I will just set the correct
PV in the various linux-yocto recipes so we don't block
master-next builds.

Is this acceptable?


In the linux-yocto bbappends of the various layers ? I keep track of 
the PV's in the

core recipes themselves, so they shouldn't need to be modified.
You're right. Only the linux-yocto bbappends in meta-yocto-bsp need 
MACHINE-specific PVs right now.
The issue with 4.1 (used by lsb right now) in oe-core is that 
LINUX_VERSION was bumped to 4.1.32 rather than 4.1.31 in error.


---
Cal



Bruce


Thanks,
Cal


On 09/19/2016 01:49 PM, Saul Wold wrote:

On Mon, 2016-09-19 at 15:55 -0400, Bruce Ashfield wrote:

On 2016-09-19 03:53 PM, Cal Sullivan wrote:

Yep, these all have incorrect PVs.
628bf62756 Merge tag 'v4.4.11' into standard/base
The problem seems fairly wide spread.

Bruce, do you suggest updating PVs or updating the
SRCREVs (is
there a
good reason to keep using old SRCREVs?)?

Updating the SRCREVs is the right thing to do to sync them
up now.

but ..

at the same time, they should probably have their own PVs,
since
next time up update 4.4.x, they'll fall out of sync and
fail again.

+1, I think that these need their own PV since they also don't
update
as fast as the base qemu recipes do.

Sau!

We want them to be aligned with the latest -stable, but we
also
don't need failures every time I push a new SRCREV and
update the
PV of the base recipe.

Bruce


---
Cal


On 09/19/2016 11:54 AM, Burton, Ross wrote:


On 19 September 2016 at 18:05, Cal Sullivan

>> wrote:

 It looks like the function is doing as its
supposed to, and
we
 need to update some PVs or SRCREVs to match PVs.

 E.g., on the error below, SRCREV d6237b3b24
is indeed 4.1.31.


And some more builders failed with 4.4:

ERROR:
linux-yocto-4.4.20+gitAUTOINC+e66032e2d9_628bf62756-r0
do_kernel_version_sanity_check: Package Version
(4.4.20+gitAUTOINC+e66032e2d9_628bf62756) does not
match of
kernel
being built (4.4.11). Please update the PV
variable to match the
kernel source.
ERROR:
linux-yocto-4.4.20+gitAUTOINC+e66032e2d9_628bf62756-r0
do_kernel_version_sanity_check: Function failed:
do_kernel_version_sanity_check (log file is located at
/home/pokybuild/yocto-autobuilder/yocto-worker/nightly-

arm/build/build/tmp/work/beaglebone-poky-linux-gnueabi/linux-
yocto/4.4.20+gitAUTOINC+e66032e2d9_628bf62756-
r0/temp/log.do_kernel_version_sanity_check.30210)
NOTE: recipe usbutils-008-r0: task do_fetch: Started
ERROR: Logfile of failure stored in:
/home/pokybuild/yocto-autobuilder/yocto-worker/nightly-

arm/build/build/tmp/work/beaglebone-poky-linux-gnueabi/linux-
yocto/4.4.20+gitAUTOINC+e66032e2d9_628bf62756-
r0/temp/log.do_kernel_version_sanity_check.30210
ERROR: Task
(/home/pokybuild/yocto-autobuilder/yocto-worker/nightly-
arm/build/meta/recipes-kernel/linux/linux-
yocto_4.4.bb:do_kernel_version_sanity_check)
failed with exit code '1'

(ditto for ppc and x86)

Ross


-- 
___

Openembedded-core mailing list
Openembedded-core@lists.openembedded.org

http://lists.openembedded.org/mailman/listinfo/openembedded-core





--
"Thou shalt not follow the NULL pointer, for chaos and madness 

Re: [OE-core] [PATCH V2 1/1] kernel.bbclass: Add kernel_version_sanity_check function

[Bruce Ashfield]

On Mon, Sep 19, 2016 at 6:02 PM, Cal Sullivan <
california.l.sulli...@intel.com> wrote:

> I don't have time to smoke test a SRCREV update for so many machines right
> now, so I think for now I will just set the correct PV in the various
> linux-yocto recipes so we don't block master-next builds.
>
> Is this acceptable?
>

In the linux-yocto bbappends of the various layers ? I keep track of the
PV's in the
core recipes themselves, so they shouldn't need to be modified.

Bruce


>
> Thanks,
> Cal
>
>
> On 09/19/2016 01:49 PM, Saul Wold wrote:
>
>> On Mon, 2016-09-19 at 15:55 -0400, Bruce Ashfield wrote:
>>
>>> On 2016-09-19 03:53 PM, Cal Sullivan wrote:
>>>
 Yep, these all have incorrect PVs.
 628bf62756 Merge tag 'v4.4.11' into standard/base
 The problem seems fairly wide spread.

 Bruce, do you suggest updating PVs or updating the SRCREVs (is
 there a
 good reason to keep using old SRCREVs?)?

>>> Updating the SRCREVs is the right thing to do to sync them up now.
>>>
>>> but ..
>>>
>>> at the same time, they should probably have their own PVs, since
>>> next time up update 4.4.x, they'll fall out of sync and fail again.
>>>
>>> +1, I think that these need their own PV since they also don't update
>> as fast as the base qemu recipes do.
>>
>> Sau!
>>
>> We want them to be aligned with the latest -stable, but we also
>>> don't need failures every time I push a new SRCREV and update the
>>> PV of the base recipe.
>>>
>>> Bruce
>>>
>>>
 ---
 Cal


 On 09/19/2016 11:54 AM, Burton, Ross wrote:

>
> On 19 September 2016 at 18:05, Cal Sullivan
>  > wrote:
>
>  It looks like the function is doing as its supposed to, and
> we
>  need to update some PVs or SRCREVs to match PVs.
>
>  E.g., on the error below, SRCREV d6237b3b24 is indeed 4.1.31.
>
>
> And some more builders failed with 4.4:
>
> ERROR: linux-yocto-4.4.20+gitAUTOINC+e66032e2d9_628bf62756-r0
> do_kernel_version_sanity_check: Package Version
> (4.4.20+gitAUTOINC+e66032e2d9_628bf62756) does not match of
> kernel
> being built (4.4.11). Please update the PV variable to match the
> kernel source.
> ERROR: linux-yocto-4.4.20+gitAUTOINC+e66032e2d9_628bf62756-r0
> do_kernel_version_sanity_check: Function failed:
> do_kernel_version_sanity_check (log file is located at
> /home/pokybuild/yocto-autobuilder/yocto-worker/nightly-
> arm/build/build/tmp/work/beaglebone-poky-linux-gnueabi/linux-
> yocto/4.4.20+gitAUTOINC+e66032e2d9_628bf62756-
> r0/temp/log.do_kernel_version_sanity_check.30210)
> NOTE: recipe usbutils-008-r0: task do_fetch: Started
> ERROR: Logfile of failure stored in:
> /home/pokybuild/yocto-autobuilder/yocto-worker/nightly-
> arm/build/build/tmp/work/beaglebone-poky-linux-gnueabi/linux-
> yocto/4.4.20+gitAUTOINC+e66032e2d9_628bf62756-
> r0/temp/log.do_kernel_version_sanity_check.30210
> ERROR: Task
> (/home/pokybuild/yocto-autobuilder/yocto-worker/nightly-
> arm/build/meta/recipes-kernel/linux/linux-
> yocto_4.4.bb:do_kernel_version_sanity_check)
> failed with exit code '1'
>
> (ditto for ppc and x86)
>
> Ross
>

> --
> ___
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>



-- 
"Thou shalt not follow the NULL pointer, for chaos and madness await thee
at its end"
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [PATCH V2 1/1] kernel.bbclass: Add kernel_version_sanity_check function

[Cal Sullivan]

I don't have time to smoke test a SRCREV update for so many machines 
right now, so I think for now I will just set the correct PV in the 
various linux-yocto recipes so we don't block master-next builds.


Is this acceptable?

Thanks,
Cal

On 09/19/2016 01:49 PM, Saul Wold wrote:

On Mon, 2016-09-19 at 15:55 -0400, Bruce Ashfield wrote:

On 2016-09-19 03:53 PM, Cal Sullivan wrote:

Yep, these all have incorrect PVs.
628bf62756 Merge tag 'v4.4.11' into standard/base
The problem seems fairly wide spread.

Bruce, do you suggest updating PVs or updating the SRCREVs (is
there a
good reason to keep using old SRCREVs?)?

Updating the SRCREVs is the right thing to do to sync them up now.

but ..

at the same time, they should probably have their own PVs, since
next time up update 4.4.x, they'll fall out of sync and fail again.


+1, I think that these need their own PV since they also don't update
as fast as the base qemu recipes do.

Sau!


We want them to be aligned with the latest -stable, but we also
don't need failures every time I push a new SRCREV and update the
PV of the base recipe.

Bruce



---
Cal


On 09/19/2016 11:54 AM, Burton, Ross wrote:


On 19 September 2016 at 18:05, Cal Sullivan
> wrote:

 It looks like the function is doing as its supposed to, and
we
 need to update some PVs or SRCREVs to match PVs.

 E.g., on the error below, SRCREV d6237b3b24 is indeed 4.1.31.


And some more builders failed with 4.4:

ERROR: linux-yocto-4.4.20+gitAUTOINC+e66032e2d9_628bf62756-r0
do_kernel_version_sanity_check: Package Version
(4.4.20+gitAUTOINC+e66032e2d9_628bf62756) does not match of
kernel
being built (4.4.11). Please update the PV variable to match the
kernel source.
ERROR: linux-yocto-4.4.20+gitAUTOINC+e66032e2d9_628bf62756-r0
do_kernel_version_sanity_check: Function failed:
do_kernel_version_sanity_check (log file is located at
/home/pokybuild/yocto-autobuilder/yocto-worker/nightly-
arm/build/build/tmp/work/beaglebone-poky-linux-gnueabi/linux-
yocto/4.4.20+gitAUTOINC+e66032e2d9_628bf62756-
r0/temp/log.do_kernel_version_sanity_check.30210)
NOTE: recipe usbutils-008-r0: task do_fetch: Started
ERROR: Logfile of failure stored in:
/home/pokybuild/yocto-autobuilder/yocto-worker/nightly-
arm/build/build/tmp/work/beaglebone-poky-linux-gnueabi/linux-
yocto/4.4.20+gitAUTOINC+e66032e2d9_628bf62756-
r0/temp/log.do_kernel_version_sanity_check.30210
ERROR: Task
(/home/pokybuild/yocto-autobuilder/yocto-worker/nightly-
arm/build/meta/recipes-kernel/linux/linux-
yocto_4.4.bb:do_kernel_version_sanity_check)
failed with exit code '1'

(ditto for ppc and x86)

Ross


--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

[OE-core] [meta-oe][PATCH] packagegroup-basic: make avahi depending on distro features

[Stefan Agner]

Depend on zeroconf distro feature whether to install avahi packages
as it is done in packagegroup-base.

While at it also get rid of some comment cruft.

Signed-off-by: Stefan Agner 
---
 meta-oe/recipes-core/packagegroups/packagegroup-basic.bb | 4 +---
 1 file changed, 1 insertion(+), 3 deletions(-)

diff --git a/meta-oe/recipes-core/packagegroups/packagegroup-basic.bb 
b/meta-oe/recipes-core/packagegroups/packagegroup-basic.bb
index 4f2992c..28e1f33 100644
--- a/meta-oe/recipes-core/packagegroups/packagegroup-basic.bb
+++ b/meta-oe/recipes-core/packagegroups/packagegroup-basic.bb
@@ -27,11 +27,9 @@ TASK_BASIC_SSHDAEMON ?= "dropbear openssh-sftp 
openssh-sftp-server"
 # It also avoids the choice between connman/networkmanager/ifupdown since that 
is an image feature, not a
 # distro feature.
 #
-# Util-linux (u)mount is included because the busybox one can't handle 
/etc/mtab being symlinked to /proc/mounts
-#
 RDEPENDS_${PN} = "\
 ${TASK_BASIC_SSHDAEMON} \
-avahi-daemon avahi-utils \
+${@bb.utils.contains("DISTRO_FEATURES", "zeroconf", "avahi-daemon 
avahi-utils", "", d)} \
 "
 
 #
-- 
2.5.5

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [PATCH V2 1/1] kernel.bbclass: Add kernel_version_sanity_check function

[Saul Wold]

On Mon, 2016-09-19 at 15:55 -0400, Bruce Ashfield wrote:
> On 2016-09-19 03:53 PM, Cal Sullivan wrote:
> > 
> > Yep, these all have incorrect PVs.
> > 628bf62756 Merge tag 'v4.4.11' into standard/base
> > The problem seems fairly wide spread.
> > 
> > Bruce, do you suggest updating PVs or updating the SRCREVs (is
> > there a
> > good reason to keep using old SRCREVs?)?
> 
> Updating the SRCREVs is the right thing to do to sync them up now.
> 
> but ..
> 
> at the same time, they should probably have their own PVs, since
> next time up update 4.4.x, they'll fall out of sync and fail again.
> 
+1, I think that these need their own PV since they also don't update
as fast as the base qemu recipes do.

Sau!

> We want them to be aligned with the latest -stable, but we also
> don't need failures every time I push a new SRCREV and update the
> PV of the base recipe.
> 
> Bruce
> 
> > 
> > 
> > ---
> > Cal
> > 
> > 
> > On 09/19/2016 11:54 AM, Burton, Ross wrote:
> > > 
> > > 
> > > On 19 September 2016 at 18:05, Cal Sullivan
> > >  > > > wrote:
> > > 
> > > It looks like the function is doing as its supposed to, and
> > > we
> > > need to update some PVs or SRCREVs to match PVs.
> > > 
> > > E.g., on the error below, SRCREV d6237b3b24 is indeed 4.1.31.
> > > 
> > > 
> > > And some more builders failed with 4.4:
> > > 
> > > ERROR: linux-yocto-4.4.20+gitAUTOINC+e66032e2d9_628bf62756-r0
> > > do_kernel_version_sanity_check: Package Version
> > > (4.4.20+gitAUTOINC+e66032e2d9_628bf62756) does not match of
> > > kernel
> > > being built (4.4.11). Please update the PV variable to match the
> > > kernel source.
> > > ERROR: linux-yocto-4.4.20+gitAUTOINC+e66032e2d9_628bf62756-r0
> > > do_kernel_version_sanity_check: Function failed:
> > > do_kernel_version_sanity_check (log file is located at
> > > /home/pokybuild/yocto-autobuilder/yocto-worker/nightly-
> > > arm/build/build/tmp/work/beaglebone-poky-linux-gnueabi/linux-
> > > yocto/4.4.20+gitAUTOINC+e66032e2d9_628bf62756-
> > > r0/temp/log.do_kernel_version_sanity_check.30210)
> > > NOTE: recipe usbutils-008-r0: task do_fetch: Started
> > > ERROR: Logfile of failure stored in:
> > > /home/pokybuild/yocto-autobuilder/yocto-worker/nightly-
> > > arm/build/build/tmp/work/beaglebone-poky-linux-gnueabi/linux-
> > > yocto/4.4.20+gitAUTOINC+e66032e2d9_628bf62756-
> > > r0/temp/log.do_kernel_version_sanity_check.30210
> > > ERROR: Task
> > > (/home/pokybuild/yocto-autobuilder/yocto-worker/nightly-
> > > arm/build/meta/recipes-kernel/linux/linux-
> > > yocto_4.4.bb:do_kernel_version_sanity_check)
> > > failed with exit code '1'
> > > 
> > > (ditto for ppc and x86)
> > > 
> > > Ross
> > 
> 
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [v2] e2fsprogs: add packageconfig for -file-

[Burton, Ross]

On 19 September 2016 at 21:22, Randy MacLeod 
wrote:

> +PACKAGECONFIG ??= "file"
> +PACKAGECONFIG[file] = ',,file'
>

This still has the non-determinism problem if file is disabled in
PACKAGECONFIG.

If the configure.ac doesn't have options but is doing standard
AC_CHECK_HEADERS or similar then you can preseed the autoconf cache values,
grepping oe-core or ac_cv_ will find plenty of prior art.

Ross
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

[OE-core] [v2] e2fsprogs: add packageconfig for -file-

[Randy MacLeod]

Without a packageconfig dependency for the file utility, there's
a rare compile faiure caused by a race where the magic.h
header file is not found:

 ../../../git/lib/support/plausible.c:33:19: fatal error: magic.h: No such file 
or directory

This file, plausible.c, is part of libsupport.a which is used by
many binaries produced by the e2fsprogs package. plausible.c attempts
to dynamically load libmagic.so if the e2fsprogs configure detects
that magic was available. Adding the packageconfig will eliminate
the compile-time as well as the possible configure-time race condition.

Signed-off-by: Randy MacLeod 
---
 meta/recipes-devtools/e2fsprogs/e2fsprogs_1.43.bb | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/meta/recipes-devtools/e2fsprogs/e2fsprogs_1.43.bb 
b/meta/recipes-devtools/e2fsprogs/e2fsprogs_1.43.bb
index f4855bc..0d7a42b 100644
--- a/meta/recipes-devtools/e2fsprogs/e2fsprogs_1.43.bb
+++ b/meta/recipes-devtools/e2fsprogs/e2fsprogs_1.43.bb
@@ -22,7 +22,8 @@ EXTRA_OECONF += "--libdir=${base_libdir} 
--sbindir=${base_sbindir} \
 
 EXTRA_OECONF_darwin = "--libdir=${base_libdir} --sbindir=${base_sbindir} 
--enable-bsd-shlibs"
 
-PACKAGECONFIG ??= ""
+PACKAGECONFIG ??= "file"
+PACKAGECONFIG[file] = ',,file'
 PACKAGECONFIG[fuse] = '--enable-fuse2fs,--disable-fuse2fs,fuse'
 
 do_configure_prepend () {
-- 
1.9.1

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [PATCH V2 1/1] kernel.bbclass: Add kernel_version_sanity_check function

[Bruce Ashfield]

On 2016-09-19 03:53 PM, Cal Sullivan wrote:

Yep, these all have incorrect PVs.
628bf62756 Merge tag 'v4.4.11' into standard/base
The problem seems fairly wide spread.

Bruce, do you suggest updating PVs or updating the SRCREVs (is there a
good reason to keep using old SRCREVs?)?


Updating the SRCREVs is the right thing to do to sync them up now.

but ..

at the same time, they should probably have their own PVs, since
next time up update 4.4.x, they'll fall out of sync and fail again.

We want them to be aligned with the latest -stable, but we also
don't need failures every time I push a new SRCREV and update the
PV of the base recipe.

Bruce



---
Cal


On 09/19/2016 11:54 AM, Burton, Ross wrote:


On 19 September 2016 at 18:05, Cal Sullivan
> wrote:

It looks like the function is doing as its supposed to, and we
need to update some PVs or SRCREVs to match PVs.

E.g., on the error below, SRCREV d6237b3b24 is indeed 4.1.31.


And some more builders failed with 4.4:

ERROR: linux-yocto-4.4.20+gitAUTOINC+e66032e2d9_628bf62756-r0
do_kernel_version_sanity_check: Package Version
(4.4.20+gitAUTOINC+e66032e2d9_628bf62756) does not match of kernel
being built (4.4.11). Please update the PV variable to match the
kernel source.
ERROR: linux-yocto-4.4.20+gitAUTOINC+e66032e2d9_628bf62756-r0
do_kernel_version_sanity_check: Function failed:
do_kernel_version_sanity_check (log file is located at
/home/pokybuild/yocto-autobuilder/yocto-worker/nightly-arm/build/build/tmp/work/beaglebone-poky-linux-gnueabi/linux-yocto/4.4.20+gitAUTOINC+e66032e2d9_628bf62756-r0/temp/log.do_kernel_version_sanity_check.30210)
NOTE: recipe usbutils-008-r0: task do_fetch: Started
ERROR: Logfile of failure stored in:
/home/pokybuild/yocto-autobuilder/yocto-worker/nightly-arm/build/build/tmp/work/beaglebone-poky-linux-gnueabi/linux-yocto/4.4.20+gitAUTOINC+e66032e2d9_628bf62756-r0/temp/log.do_kernel_version_sanity_check.30210
ERROR: Task
(/home/pokybuild/yocto-autobuilder/yocto-worker/nightly-arm/build/meta/recipes-kernel/linux/linux-yocto_4.4.bb:do_kernel_version_sanity_check)
failed with exit code '1'

(ditto for ppc and x86)

Ross




--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [PATCH V2 1/1] kernel.bbclass: Add kernel_version_sanity_check function

[Cal Sullivan]

Yep, these all have incorrect PVs.
628bf62756 Merge tag 'v4.4.11' into standard/base
The problem seems fairly wide spread.

Bruce, do you suggest updating PVs or updating the SRCREVs (is there a 
good reason to keep using old SRCREVs?)?


---
Cal


On 09/19/2016 11:54 AM, Burton, Ross wrote:


On 19 September 2016 at 18:05, Cal Sullivan 
> wrote:


It looks like the function is doing as its supposed to, and we
need to update some PVs or SRCREVs to match PVs.

E.g., on the error below, SRCREV d6237b3b24 is indeed 4.1.31.


And some more builders failed with 4.4:

ERROR: linux-yocto-4.4.20+gitAUTOINC+e66032e2d9_628bf62756-r0 
do_kernel_version_sanity_check: Package Version 
(4.4.20+gitAUTOINC+e66032e2d9_628bf62756) does not match of kernel 
being built (4.4.11). Please update the PV variable to match the 
kernel source.
ERROR: linux-yocto-4.4.20+gitAUTOINC+e66032e2d9_628bf62756-r0 
do_kernel_version_sanity_check: Function failed: 
do_kernel_version_sanity_check (log file is located at 
/home/pokybuild/yocto-autobuilder/yocto-worker/nightly-arm/build/build/tmp/work/beaglebone-poky-linux-gnueabi/linux-yocto/4.4.20+gitAUTOINC+e66032e2d9_628bf62756-r0/temp/log.do_kernel_version_sanity_check.30210)

NOTE: recipe usbutils-008-r0: task do_fetch: Started
ERROR: Logfile of failure stored in: 
/home/pokybuild/yocto-autobuilder/yocto-worker/nightly-arm/build/build/tmp/work/beaglebone-poky-linux-gnueabi/linux-yocto/4.4.20+gitAUTOINC+e66032e2d9_628bf62756-r0/temp/log.do_kernel_version_sanity_check.30210
ERROR: Task 
(/home/pokybuild/yocto-autobuilder/yocto-worker/nightly-arm/build/meta/recipes-kernel/linux/linux-yocto_4.4.bb:do_kernel_version_sanity_check) 
failed with exit code '1'


(ditto for ppc and x86)

Ross


-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] State of bitbake world 2016-09-15

[Andreas Müller]

On Mon, Sep 19, 2016 at 9:20 PM, Andreas Müller
 wrote:
> On Mon, Sep 19, 2016 at 4:49 PM, Martin Jansa  wrote:
>> == Number of issues - stats ==
>> {| class='wikitable'
>> !|Date   !!colspan='3'|Failed tasks 
>> !!colspan='6'|Failed depencencies!!|Signatures   
>>  !!colspan='12'|QA !!Comment
>> |-
>> ||  ||qemuarm   ||qemux86   ||qemux86_64
>> ||qemuarm||max||min ||qemux86||max||min ||all   ||already-stripped   
>>||libdir||textrel   ||build-deps||file-rdeps
>> ||version-going-backwards   ||host-user-contaminated
>> ||installed-vs-shipped  ||unknown-configure-option  ||symlink-to-sysroot 
>>||invalid-pkgconfig ||pkgname   ||
>> |-
>> ||2016-09-15||3 ||6 ||5 ||8 ||3 ||3 ||13||6  
>>||6 ||0 ||0 ||0 ||3 ||13  
>>   ||11||18||1 ||0 ||0
>>  ||0 ||0 ||0 ||
>> |}
>>
>> http://www.openembedded.org/wiki/Bitbake_World_Status
>>
>> == Failed tasks 2016-09-15 ==
>>
>> INFO: jenkins-job.sh-1.8.10 Complete log available at 
>> http://logs.nslu2-linux.org/buildlogs/oe/world/log.report.20160917_194919.log
>>
>> === common (3) ===
>> * 
>> meta-openembedded/meta-filesystems/recipes-utils/xfsprogs/xfsprogs_4.7.0.bb:do_compile
>> * 
>> meta-openembedded/meta-oe/recipes-extended/p7zip/p7zip_16.02.bb:do_populate_lic
>> * 
>> openembedded-core/meta/recipes-support/libunwind/libunwind_git.bb:do_compile
>>
>> === common-x86 (2) ===
>> * 
>> meta-openembedded/meta-networking/recipes-connectivity/samba/samba_4.4.5.bb:do_compile
> Again samba.. I checked the log: It seems that at least x86 for same
> issue as arm (was reported not to  fail for x86) will send correction
> - using bfd for all archs. Will put it ontop master-next
>
> Andreas
Oops - just noticed that my last patch was replaced - so no need for
further acrton - Thanks Martin

Andreas
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] State of bitbake world 2016-09-15

[Andreas Müller]

On Mon, Sep 19, 2016 at 4:49 PM, Martin Jansa  wrote:
> == Number of issues - stats ==
> {| class='wikitable'
> !|Date   !!colspan='3'|Failed tasks 
> !!colspan='6'|Failed depencencies!!|Signatures
> !!colspan='12'|QA !!Comment
> |-
> ||  ||qemuarm   ||qemux86   ||qemux86_64
> ||qemuarm||max||min ||qemux86||max||min ||all   ||already-stripped
>   ||libdir||textrel   ||build-deps||file-rdeps
> ||version-going-backwards   ||host-user-contaminated
> ||installed-vs-shipped  ||unknown-configure-option  ||symlink-to-sysroot  
>   ||invalid-pkgconfig ||pkgname   ||
> |-
> ||2016-09-15||3 ||6 ||5 ||8 ||3 ||3 ||13||6   
>   ||6 ||0 ||0 ||0 ||3 ||13
> ||11||18||1 ||0 ||0   
>   ||0 ||0 ||0 ||
> |}
>
> http://www.openembedded.org/wiki/Bitbake_World_Status
>
> == Failed tasks 2016-09-15 ==
>
> INFO: jenkins-job.sh-1.8.10 Complete log available at 
> http://logs.nslu2-linux.org/buildlogs/oe/world/log.report.20160917_194919.log
>
> === common (3) ===
> * 
> meta-openembedded/meta-filesystems/recipes-utils/xfsprogs/xfsprogs_4.7.0.bb:do_compile
> * 
> meta-openembedded/meta-oe/recipes-extended/p7zip/p7zip_16.02.bb:do_populate_lic
> * 
> openembedded-core/meta/recipes-support/libunwind/libunwind_git.bb:do_compile
>
> === common-x86 (2) ===
> * 
> meta-openembedded/meta-networking/recipes-connectivity/samba/samba_4.4.5.bb:do_compile
Again samba.. I checked the log: It seems that at least x86 for same
issue as arm (was reported not to  fail for x86) will send correction
- using bfd for all archs. Will put it ontop master-next

Andreas
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [PATCH V2 1/1] kernel.bbclass: Add kernel_version_sanity_check function

[Burton, Ross]

On 19 September 2016 at 18:05, Cal Sullivan  wrote:

> It looks like the function is doing as its supposed to, and we need to
> update some PVs or SRCREVs to match PVs.
>
> E.g., on the error below, SRCREV d6237b3b24 is indeed 4.1.31.
>

And some more builders failed with 4.4:

ERROR: linux-yocto-4.4.20+gitAUTOINC+e66032e2d9_628bf62756-r0
do_kernel_version_sanity_check: Package Version
(4.4.20+gitAUTOINC+e66032e2d9_628bf62756) does not match of kernel being
built (4.4.11). Please update the PV variable to match the kernel source.
ERROR: linux-yocto-4.4.20+gitAUTOINC+e66032e2d9_628bf62756-r0
do_kernel_version_sanity_check: Function failed:
do_kernel_version_sanity_check (log file is located at
/home/pokybuild/yocto-autobuilder/yocto-worker/nightly-arm/build/build/tmp/work/beaglebone-poky-linux-gnueabi/linux-yocto/4.4.20+gitAUTOINC+e66032e2d9_628bf62756-r0/temp/log.do_kernel_version_sanity_check.30210)
NOTE: recipe usbutils-008-r0: task do_fetch: Started
ERROR: Logfile of failure stored in:
/home/pokybuild/yocto-autobuilder/yocto-worker/nightly-arm/build/build/tmp/work/beaglebone-poky-linux-gnueabi/linux-yocto/4.4.20+gitAUTOINC+e66032e2d9_628bf62756-r0/temp/log.do_kernel_version_sanity_check.30210
ERROR: Task
(/home/pokybuild/yocto-autobuilder/yocto-worker/nightly-arm/build/meta/recipes-kernel/linux/linux-yocto_4.4.bb:do_kernel_version_sanity_check)
failed with exit code '1'

(ditto for ppc and x86)

Ross
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

[OE-core] [PATCH] oeqa/runtime/parselogs.py: Add ignore of tsc calibration fail in x86

[Aníbal Limón]

We are experimenting failures to calibrate CPU's using TSC in x86
VM's due to usage of nested KVM [1], this is a known issue [2][3]
in virtualization environments, for detail explnation see [4].

Also we already have an ignore for 'TSC Fast calibration fail'.

[1] http://errors.yoctoproject.org/Errors/Details/83684/
[2] https://bugzilla.redhat.com/show_bug.cgi?id=814231
[3] https://lists.nongnu.org/archive/html/qemu-devel/2010-09/msg01547.html
[4] https://www.kernel.org/doc/Documentation/virtual/kvm/timekeeping.txt

Signed-off-by: Aníbal Limón 
---
 meta/lib/oeqa/runtime/parselogs.py | 1 +
 1 file changed, 1 insertion(+)

diff --git a/meta/lib/oeqa/runtime/parselogs.py 
b/meta/lib/oeqa/runtime/parselogs.py
index b5017c2..763c42f 100644
--- a/meta/lib/oeqa/runtime/parselogs.py
+++ b/meta/lib/oeqa/runtime/parselogs.py
@@ -68,6 +68,7 @@ qemux86_common = [
 'Getting VBE info block failed',
 'vbe_init() failed with -22',
 'uvesafb: mode switch failed',
+'tsc: HPET/PMTIMER calibration failed',
 ] + common_errors
 
 ignore_errors = { 
-- 
2.1.4

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [PATCH] perf: Fix to obey LD failure on host i686

[Christopher Larson]

On Mon, Sep 19, 2016 at 4:10 AM, sujith h  wrote:

>
>
> On Thu, Sep 8, 2016 at 12:36 PM, Andre McCurdy 
> wrote:
>
>> On Wed, Sep 7, 2016 at 11:51 PM, Sujith H  wrote:
>> > From: Christopher Larson 
>> >
>> > When built on an i686 host for qemux86-64 without the
>> > fix to obey LD and it fails:
>> >
>> > /scratch/dogwood/toolchains/x86_64/bin/i686-pc-linux-gnu-ld:
>> > Relocatable linking with relocations from format elf64-x86-64
>> > (/scratch/dogwood/perf-ld-test/build/tmp/work/qemux86_64-mel-linux/perf
>> /1.0-r9/perf-1.0/fs/fs.o)
>> > to format elf32-i386 (/scratch/dogwood/perf-ld-test
>> /build/tmp/work/qemux86_64-mel-linux/perf/1.0-r9/perf-1.0/fs/libapi-in.o)
>> > is not supported
>> >
>> > This is because LD includes HOST_LD_ARCH, which contains TUNE_LDARGS,
>> > which is -m elf32_x86_64 for x86_64. Without that, direct use of ld
>> will fail.
>> >
>> > Signed-off-by: Christopher Larson 
>> > Signed-off-by: Sujith Haridasan 
>> > ---
>> >  meta/recipes-kernel/perf/perf.bb | 9 +
>> >  1 file changed, 9 insertions(+)
>> >
>> > diff --git a/meta/recipes-kernel/perf/perf.bb b/meta/recipes-kernel/
>> perf/perf.bb
>> > index 88e3a0a..85fe0ea 100644
>> > --- a/meta/recipes-kernel/perf/perf.bb
>> > +++ b/meta/recipes-kernel/perf/perf.bb
>> > @@ -79,6 +79,7 @@ EXTRA_OEMAKE = '\
>> >  ARCH=${ARCH} \
>> >  CC="${CC}" \
>> >  AR="${AR}" \
>> > +LD="${LD}" \
>> >  EXTRA_CFLAGS="-ldw" \
>> >  perfexecdir=${libexecdir} \
>> >  NO_GTK2=1 ${TUI_DEFINES} NO_DWARF=1 ${LIBUNWIND_DEFINES} \
>> > @@ -98,6 +99,14 @@ EXTRA_OEMAKE += "\
>> >  'infodir=${@os.path.relpath(infodir, prefix)}' \
>> >  "
>> >
>> > +do_configure_prepend () {
>> > +for makefile in "${S}/tools/perf/Makefile.perf" \
>> > +"${S}/tools/lib/api/Makefile"; do
>> > +if [ -e "$makefile" ]; then
>> > +sed -i 's,LD = $(CROSS_COMPILE)ld,#LD,' "$makefile"
>> > +fi
>> > +done
>> > +}
>>
>> Isn't passing LD via the Make command line enough to over-ride these
>> definitions in the Makefiles?
>>
>
> Unfortunately that didn't helped I believe. That's the reason, this patch
> was created.
>

The patch mirrored the handling of CC/AR, which also used sed at the time
the append was created. If upstream removed the sed for those, then we can
remove it for LD as well, presumably. I’d recommend actually testing that.
-- 
Christopher Larson
kergoth at gmail dot com
Founder - BitBake, OpenEmbedded, OpenZaurus
Maintainer - Tslib
Senior Software Engineer, Mentor Graphics
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

[OE-core] [PATCH v2] gcc-configure: Enable initfini-array

[Saul Wold]

This adds the correct support for initfini-array which replaces .init
and .fini with .init-array and .fini-array.  There is no appreciable
size difference with this change.

The change is needed since configure will not correctly detect support
when building cross-compilers.

Signed-off-by: Haitao Huang 
Signed-off-by: Saul Wold 
---
v2: Enable for all Architectures

 meta/recipes-devtools/gcc/gcc-configure-common.inc | 4 
 1 file changed, 4 insertions(+)

diff --git a/meta/recipes-devtools/gcc/gcc-configure-common.inc 
b/meta/recipes-devtools/gcc/gcc-configure-common.inc
index f4f76bd..b374c30 100644
--- a/meta/recipes-devtools/gcc/gcc-configure-common.inc
+++ b/meta/recipes-devtools/gcc/gcc-configure-common.inc
@@ -44,6 +44,10 @@ EXTRA_OECONF = "\
 ${@get_gcc_multiarch_setting(bb, d)} \
 "
 
+# Set this here since GCC configure won't auto-detect and enable
+# initfini-arry when cross compiling.
+EXTRA_OECONF_append = " --enable-initfini-array"
+
 export gcc_cv_collect2_libs = 'none required'
 # We need to set gcc_cv_collect2_libs else there is cross-compilation badness
 # in the config.log files (which might not get generated until do_compile
-- 
2.5.0

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [PATCH V2 1/1] kernel.bbclass: Add kernel_version_sanity_check function

[Cal Sullivan]

It looks like the function is doing as its supposed to, and we need to 
update some PVs or SRCREVs to match PVs.


E.g., on the error below, SRCREV d6237b3b24 is indeed 4.1.31.

---
Cal

On 09/19/2016 09:22 AM, Burton, Ross wrote:


On 19 September 2016 at 16:09, Burton, Ross > wrote:


This is being fired on the AB:

ERROR: linux-yocto-4.1.32+gitAUTOINC+b30b6b9ef2_d6237b3b24-r0
do_kernel_version_sanity_check: Package Version
(4.1.32+gitAUTOINC+b30b6b9ef2_d6237b3b24) does not match of kernel
being built (4.1.31). Please update the PV variable to match the
kernel source.
ERROR: linux-yocto-4.1.32+gitAUTOINC+b30b6b9ef2_d6237b3b24-r0
do_kernel_version_sanity_check: Function failed:
do_kernel_version_sanity_check (log file is located at

/home/pokybuild/yocto-autobuilder/yocto-worker/nightly-mips-lsb/build/build/tmp/work/qemumips-poky-linux/linux-yocto/4.1.32+gitAUTOINC+b30b6b9ef2_d6237b3b24-r0/temp/log.do_kernel_version_sanity_check.9143)
ERROR: Logfile of failure stored in:

/home/pokybuild/yocto-autobuilder/yocto-worker/nightly-mips-lsb/build/build/tmp/work/qemumips-poky-linux/linux-yocto/4.1.32+gitAUTOINC+b30b6b9ef2_d6237b3b24-r0/temp/log.do_kernel_version_sanity_check.9143


(This has happened for all the LSB builds so far)


-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

[OE-core] [PATCH] gcc-configure: Enable initfini-array for x86* Architecture

[Saul Wold]

This adds the correct support for initfini-array which replaces .init
and .fini with .init-array and .fini-array.  There is no appreciable
size difference with this change.

The change is needed since configure will not correctly detect support 
when building cross-compilers.

This only affect Intel architectures currently

Signed-off-by: Saul Wold 
---
 meta/recipes-devtools/gcc/gcc-configure-common.inc | 5 +
 1 file changed, 5 insertions(+)

diff --git a/meta/recipes-devtools/gcc/gcc-configure-common.inc 
b/meta/recipes-devtools/gcc/gcc-configure-common.inc
index f4f76bd..8845d00 100644
--- a/meta/recipes-devtools/gcc/gcc-configure-common.inc
+++ b/meta/recipes-devtools/gcc/gcc-configure-common.inc
@@ -44,6 +44,11 @@ EXTRA_OECONF = "\
 ${@get_gcc_multiarch_setting(bb, d)} \
 "
 
+# Set this here since GCC configure won't auto-detect and enable
+# initfini-arry when cross compiling.
+EXTRA_OECONF_append_x86 = " --enable-initfini-array"
+EXTRA_OECONF_append_x86-64 = " --enable-initfini-array"
+
 export gcc_cv_collect2_libs = 'none required'
 # We need to set gcc_cv_collect2_libs else there is cross-compilation badness
 # in the config.log files (which might not get generated until do_compile
-- 
2.5.0

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [PATCH V2 1/1] kernel.bbclass: Add kernel_version_sanity_check function

[Burton, Ross]

On 19 September 2016 at 16:09, Burton, Ross  wrote:

> This is being fired on the AB:
>
> ERROR: linux-yocto-4.1.32+gitAUTOINC+b30b6b9ef2_d6237b3b24-r0
> do_kernel_version_sanity_check: Package Version
> (4.1.32+gitAUTOINC+b30b6b9ef2_d6237b3b24) does not match of kernel being
> built (4.1.31). Please update the PV variable to match the kernel source.
> ERROR: linux-yocto-4.1.32+gitAUTOINC+b30b6b9ef2_d6237b3b24-r0
> do_kernel_version_sanity_check: Function failed:
> do_kernel_version_sanity_check (log file is located at
> /home/pokybuild/yocto-autobuilder/yocto-worker/
> nightly-mips-lsb/build/build/tmp/work/qemumips-poky-linux/
> linux-yocto/4.1.32+gitAUTOINC+b30b6b9ef2_d6237b3b24-r0/temp/
> log.do_kernel_version_sanity_check.9143)
> ERROR: Logfile of failure stored in: /home/pokybuild/yocto-
> autobuilder/yocto-worker/nightly-mips-lsb/build/build/
> tmp/work/qemumips-poky-linux/linux-yocto/4.1.32+gitAUTOINC+
> b30b6b9ef2_d6237b3b24-r0/temp/log.do_kernel_version_sanity_check.9143


(This has happened for all the LSB builds so far)
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [PATCH V2 1/1] kernel.bbclass: Add kernel_version_sanity_check function

[Burton, Ross]

On 19 September 2016 at 16:04, Bruce Ashfield 
wrote:

> Otherwise, I don't see anything obviously wrong (I looked at the regexs
> but didn't study them in detail) .. and it looks sane to me. A good
> balance between checking and not needing the entire kernel to be built
> and exported to work-shared.
>

This is being fired on the AB:

ERROR: linux-yocto-4.1.32+gitAUTOINC+b30b6b9ef2_d6237b3b24-r0
do_kernel_version_sanity_check: Package Version
(4.1.32+gitAUTOINC+b30b6b9ef2_d6237b3b24) does not match of kernel being
built (4.1.31). Please update the PV variable to match the kernel source.
ERROR: linux-yocto-4.1.32+gitAUTOINC+b30b6b9ef2_d6237b3b24-r0
do_kernel_version_sanity_check: Function failed:
do_kernel_version_sanity_check (log file is located at
/home/pokybuild/yocto-autobuilder/yocto-worker/nightly-mips-lsb/build/build/tmp/work/qemumips-poky-linux/linux-yocto/4.1.32+gitAUTOINC+b30b6b9ef2_d6237b3b24-r0/temp/log.do_kernel_version_sanity_check.9143)
ERROR: Logfile of failure stored in:
/home/pokybuild/yocto-autobuilder/yocto-worker/nightly-mips-lsb/build/build/tmp/work/qemumips-poky-linux/linux-yocto/4.1.32+gitAUTOINC+b30b6b9ef2_d6237b3b24-r0/temp/log.do_kernel_version_sanity_check.9143

Ross
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [PATCH V2 1/1] kernel.bbclass: Add kernel_version_sanity_check function

[Bruce Ashfield]

On 2016-09-16 07:48 PM, California Sullivan wrote:

The kernel being built should match what the recipe claims it is
building. This function ensures that happens by comparing the version
information in the kernel's Makefile to the PV the recipe is using.

v2 changes:
* Match against PV instead of LINUX_VERSION
* Match against EXTRAVERSION as well (e.g., -rc4)
* Cleaned up version string building

Fixes [YOCTO #6767].

Signed-off-by: California Sullivan 
---
 meta/classes/kernel.bbclass   | 30 ++
 meta/recipes-kernel/linux/linux-yocto.inc |  1 +
 2 files changed, 31 insertions(+)

diff --git a/meta/classes/kernel.bbclass b/meta/classes/kernel.bbclass
index a6112e8..f894795 100644
--- a/meta/classes/kernel.bbclass
+++ b/meta/classes/kernel.bbclass
@@ -327,6 +327,36 @@ kernel_do_install() {
 }
 do_install[prefuncs] += "package_get_auto_pr"

+# Must be ran no earlier than after do_kernel_checkout or else Makefile won't 
be in ${S}/Makefile
+do_kernel_version_sanity_check() {
+   # The Makefile determines the kernel version shown at runtime
+   # Don't use KERNEL_VERSION because the headers it grabs the version 
from aren't generated until do_compile
+   VERSION=$(grep "^VERSION =" ${S}/Makefile | sed s/.*=\ *//)
+   PATCHLEVEL=$(grep "^PATCHLEVEL =" ${S}/Makefile | sed s/.*=\ *//)
+   SUBLEVEL=$(grep "^SUBLEVEL =" ${S}/Makefile | sed s/.*=\ *//)
+   EXTRAVERSION=$(grep "^EXTRAVERSION =" ${S}/Makefile | sed s/.*=\ *//)
+
+   # Build a string for regex and a plain version string
+   reg="^${VERSION}\.${PATCHLEVEL}"
+   vers="${VERSION}.${PATCHLEVEL}"
+   if [ -n "${SUBLEVEL}" ]; then
+   # Ignoring a SUBLEVEL of zero is fine
+   if [ "${SUBLEVEL}" = "0" ]; then
+   reg="${reg}(\.${SUBLEVEL})?"
+   else
+   reg="${reg}\.${SUBLEVEL}"
+   vers="${vers}.${SUBLEVEL}"
+   fi
+   fi
+   vers="${vers}${EXTRAVERSION}"
+   reg="${reg}${EXTRAVERSION}"
+
+   if [ -z `echo ${PV} | grep -E "${reg}"` ]; then
+   bbfatal "Package Version (${PV}) does not match of kernel being 
built (${vers}). Please update the PV variable to match the kernel source."


My only 'nit is that this is a fairly long line. Would it be worth
splitting it into two ?

Otherwise, I don't see anything obviously wrong (I looked at the regexs
but didn't study them in detail) .. and it looks sane to me. A good
balance between checking and not needing the entire kernel to be built
and exported to work-shared.

Cheers,

Bruce


+   fi
+   exit 0
+}
+
 addtask shared_workdir after do_compile before do_compile_kernelmodules
 addtask shared_workdir_setscene

diff --git a/meta/recipes-kernel/linux/linux-yocto.inc 
b/meta/recipes-kernel/linux/linux-yocto.inc
index 98a48ec..d979662 100644
--- a/meta/recipes-kernel/linux/linux-yocto.inc
+++ b/meta/recipes-kernel/linux/linux-yocto.inc
@@ -55,6 +55,7 @@ do_install_append(){
 }

 # extra tasks
+addtask kernel_version_sanity_check after do_kernel_checkout before do_compile
 addtask kernel_link_images after do_compile before do_install
 addtask validate_branches before do_patch after do_kernel_checkout
 addtask kernel_configcheck after do_configure before do_compile



--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

[OE-core] State of bitbake world 2016-09-15

[Martin Jansa]

== Number of issues - stats ==
{| class='wikitable'
!|Date   !!colspan='3'|Failed tasks 
!!colspan='6'|Failed depencencies!!|Signatures
!!colspan='12'|QA !!Comment
|-
||  ||qemuarm   ||qemux86   ||qemux86_64
||qemuarm||max||min ||qemux86||max||min ||all   ||already-stripped  
||libdir||textrel   ||build-deps||file-rdeps
||version-going-backwards   ||host-user-contaminated
||installed-vs-shipped  ||unknown-configure-option  ||symlink-to-sysroot
||invalid-pkgconfig ||pkgname   ||  
|-
||2016-09-15||3 ||6 ||5 ||8 ||3 ||3 ||13||6 
||6 ||0 ||0 ||0 ||3 ||13
||11||18||1 ||0 ||0 
||0 ||0 ||0 ||  
|}

http://www.openembedded.org/wiki/Bitbake_World_Status

== Failed tasks 2016-09-15 ==

INFO: jenkins-job.sh-1.8.10 Complete log available at 
http://logs.nslu2-linux.org/buildlogs/oe/world/log.report.20160917_194919.log

=== common (3) ===
* 
meta-openembedded/meta-filesystems/recipes-utils/xfsprogs/xfsprogs_4.7.0.bb:do_compile
* 
meta-openembedded/meta-oe/recipes-extended/p7zip/p7zip_16.02.bb:do_populate_lic
* 
openembedded-core/meta/recipes-support/libunwind/libunwind_git.bb:do_compile

=== common-x86 (2) ===
* 
meta-openembedded/meta-networking/recipes-connectivity/samba/samba_4.4.5.bb:do_compile
* 
meta-openembedded/meta-oe/recipes-support/mcelog/mce-inject_git.bb:do_populate_lic

=== qemuarm (0) ===

=== qemux86 (1) ===
* meta-browser/recipes-browser/chromium/chromium_52.0.2743.76.bb:do_compile

=== qemux86_64 (0) ===

=== Number of failed tasks (14) ===
{| class=wikitable
|-
|| qemuarm  || 3 || 
http://logs.nslu2-linux.org/buildlogs/oe/world/log.world.qemuarm.20160914_225926.log/
 || http://errors.yoctoproject.org/Errors/Build/21714/
|-
|| qemux86  || 6 || 
http://logs.nslu2-linux.org/buildlogs/oe/world/log.world.qemux86.20160914_225932.log/
 || http://errors.yoctoproject.org/Errors/Build/21717/
|-
|| qemux86_64   || 5 || 
http://logs.nslu2-linux.org/buildlogs/oe/world/log.world.qemux86-64.20160915_232922.log/
 || http://errors.yoctoproject.org/Errors/Build/21750/
|}

=== PNBLACKLISTs (119) ===

=== QA issues (46) ===
{| class=wikitable
!| Count||Issue
|-
||0 ||already-stripped
|-
||0 ||installed-vs-shipped
|-
||0 ||invalid-pkgconfig
|-
||0 ||libdir
|-
||0 ||pkgname
|-
||0 ||symlink-to-sysroot
|-
||0 ||unknown-configure-option
|-
||11||file-rdeps
|-
||13||build-deps
|-
||18||version-going-backwards
|-
||1 ||host-user-contaminated
|-
||3 ||textrel
|}



=== Failed dependencies for qemuarm (8) ===

Complete log: 
http://logs.nslu2-linux.org/buildlogs/oe/world/log.dependencies.qemuarm.20160915_221022.log/
Found differences: 
* WARN: samba: samba rdepends on libpam, but it isn't a build dependency?
Found errors: 
* ERROR: 8 issues were found in these recipes: libunwind p7zip samba 
xfsprogs

=== Recipes failing with maximal dependencies for qemuarm (3) ===
* libunwind -- 
http://logs.nslu2-linux.org/buildlogs/oe/world/log.dependencies.qemuarm.20160915_221022.log//2_max/failed/libunwind.log
* p7zip -- 
http://logs.nslu2-linux.org/buildlogs/oe/world/log.dependencies.qemuarm.20160915_221022.log//2_max/failed/p7zip.log
* xfsprogs -- 
http://logs.nslu2-linux.org/buildlogs/oe/world/log.dependencies.qemuarm.20160915_221022.log//2_max/failed/xfsprogs.log

=== Recipes failing with minimal dependencies for qemuarm (3) ===
* libunwind -- 
http://logs.nslu2-linux.org/buildlogs/oe/world/log.dependencies.qemuarm.20160915_221022.log//3_min/failed/libunwind.log
* p7zip -- 
http://logs.nslu2-linux.org/buildlogs/oe/world/log.dependencies.qemuarm.20160915_221022.log//3_min/failed/p7zip.log
* xfsprogs -- 
http://logs.nslu2-linux.org/buildlogs/oe/world/log.dependencies.qemuarm.20160915_221022.log//3_min/failed/xfsprogs.log

=== Failed dependencies for qemux86 (13) ===

Complete log: 
http://logs.nslu2-linux.org/buildlogs/oe/world/log.dependencies.qemux86.20160916_222429.log/
Found differences: 
Found errors: 
* ERROR: 13 issues were found in these recipes: chromium libunwind 
mce-inject p7zip samba xfsprogs

=== Recipes failing with maximal dependencies for qemux86 (6) ===
* chromium -- 
http://logs.nslu2-linux.org/buildlogs/oe/world/log.dependencies.qemux86.20160916_222429.log//2_max/failed/chromium.log
* libunwind -- 
http://logs.nslu2-linux.org/buildlogs/oe/world/log.dependencies.qemux86.20160916_222429.log//2_max/failed/libunwind.log
* mce-inject -- 
http://logs.nslu2-linux.org/buildlogs/oe/world/log.dependencies.qemux86.20160916_222429.log//2_max/failed/mce-inject.log
* p7zip -- 

Re: [OE-core] [PATCH v2] ltp: 20160126 -> 20160510

[Randy MacLeod]

On 2016-09-19 02:35 AM, Wang Xin wrote:

1) Upgrade ltp from 20160126 to 20160510.
2) Modify some patches, since the data has been changed.
0011-Rename-sigset-variable-to-sigset1.patch
0030-lib-Use-PTHREAD_MUTEX_RECURSIVE-in-place-of-PTHREAD_.patch
3) Delete some patches, since they are no use.

Do you mean that they are integrated upstream? If so
it would be useful to provide the commit ID so that
anyone who wants to confirm that dropping the patch
makes sense, doesn't have to reproduce the work you
have done to also confirm that.

If there's another reason that these patches are not
useful, please explain since I presume that we added
each patch for a good reason previously.

../Randy


0001-ltp-Don-t-link-against-libfl.patch
0006-sendfile-Use-off64_t-instead-of-__off64_t.patch
0012-fsstress.c-Replace-__int64_t-with-int64_t.patch
0013-include-fcntl.h-for-getting-O_-definitions.patch
0014-hyperthreading-Include-sys-types.h-for-pid_t-definit.patch
0015-mincore01-Rename-PAGESIZE-to-pagesize.patch
0016-ustat-Change-header-from-ustat.h-to-sys-ustat.h.patch
0017-replace-sigval_t-with-union-sigval.patch
0019-tomoyo-Replace-canonicalize_file_name-with-realpath.patch
0032-regen.sh-Include-asm-unistd.h-explicitly.patch

Signed-off-by: Wang Xin 
---
 .../ltp/0001-ltp-Don-t-link-against-libfl.patch|  30 --
 ...sendfile-Use-off64_t-instead-of-__off64_t.patch |  31 --
 .../0011-Rename-sigset-variable-to-sigset1.patch   |  60 ++--
 ...fsstress.c-Replace-__int64_t-with-int64_t.patch | 351 -
 ...nclude-fcntl.h-for-getting-O_-definitions.patch |  67 
 ...ing-Include-sys-types.h-for-pid_t-definit.patch |  56 
 ...015-mincore01-Rename-PAGESIZE-to-pagesize.patch |  64 
 ...Change-header-from-ustat.h-to-sys-ustat.h.patch |  45 ---
 .../0017-replace-sigval_t-with-union-sigval.patch  |  88 --
 ...lace-canonicalize_file_name-with-realpath.patch |  32 --
 ...READ_MUTEX_RECURSIVE-in-place-of-PTHREAD_.patch |   6 +-
 ...-regen.sh-Include-asm-unistd.h-explicitly.patch |  30 --
 .../ltp/{ltp_20160126.bb => ltp_20160510.bb}   |  12 +-
 13 files changed, 34 insertions(+), 838 deletions(-)
 delete mode 100644 
meta/recipes-extended/ltp/ltp/0001-ltp-Don-t-link-against-libfl.patch
 delete mode 100644 
meta/recipes-extended/ltp/ltp/0006-sendfile-Use-off64_t-instead-of-__off64_t.patch
 delete mode 100644 
meta/recipes-extended/ltp/ltp/0012-fsstress.c-Replace-__int64_t-with-int64_t.patch
 delete mode 100644 
meta/recipes-extended/ltp/ltp/0013-include-fcntl.h-for-getting-O_-definitions.patch
 delete mode 100644 
meta/recipes-extended/ltp/ltp/0014-hyperthreading-Include-sys-types.h-for-pid_t-definit.patch
 delete mode 100644 
meta/recipes-extended/ltp/ltp/0015-mincore01-Rename-PAGESIZE-to-pagesize.patch
 delete mode 100644 
meta/recipes-extended/ltp/ltp/0016-ustat-Change-header-from-ustat.h-to-sys-ustat.h.patch
 delete mode 100644 
meta/recipes-extended/ltp/ltp/0017-replace-sigval_t-with-union-sigval.patch
 delete mode 100644 
meta/recipes-extended/ltp/ltp/0019-tomoyo-Replace-canonicalize_file_name-with-realpath.patch
 delete mode 100644 
meta/recipes-extended/ltp/ltp/0032-regen.sh-Include-asm-unistd.h-explicitly.patch
 rename meta/recipes-extended/ltp/{ltp_20160126.bb => ltp_20160510.bb} (88%)

diff --git 
a/meta/recipes-extended/ltp/ltp/0001-ltp-Don-t-link-against-libfl.patch 
b/meta/recipes-extended/ltp/ltp/0001-ltp-Don-t-link-against-libfl.patch
deleted file mode 100644
index 585b7cb..000
--- a/meta/recipes-extended/ltp/ltp/0001-ltp-Don-t-link-against-libfl.patch
+++ /dev/null
@@ -1,30 +0,0 @@
-From 14985fccf7428eaa0b45decc22bfd20fd780f621 Mon Sep 17 00:00:00 2001
-From: Chong Lu 
-Date: Tue, 11 Mar 2014 14:47:22 +0800
-Subject: [PATCH 01/32] ltp: Don't link against libfl
-
-We have already defined yywrap function in scan.l file. After this, we no 
longer need to
-link against libfl and so no longer get errors about undefined references to 
yylex.
-
-Signed-off-by: Chong Lu 
-Signed-off-by: Khem Raj 

- pan/Makefile | 2 +-
- 1 file changed, 1 insertion(+), 1 deletion(-)
-
-diff --git a/pan/Makefile b/pan/Makefile
-index 4cc6466..a4b575b 100644
 a/pan/Makefile
-+++ b/pan/Makefile
-@@ -31,7 +31,7 @@ CPPFLAGS += -Wno-error
-
- CPPFLAGS  += -I$(abs_srcdir)
-
--LDLIBS+= -lm $(LEXLIB)
-+LDLIBS+= -lm
-
- LFLAGS+= -l
-
---
-2.7.0
-
diff --git 
a/meta/recipes-extended/ltp/ltp/0006-sendfile-Use-off64_t-instead-of-__off64_t.patch
 
b/meta/recipes-extended/ltp/ltp/0006-sendfile-Use-off64_t-instead-of-__off64_t.patch
deleted file mode 100644
index 56a48ab..000
--- 
a/meta/recipes-extended/ltp/ltp/0006-sendfile-Use-off64_t-instead-of-__off64_t.patch
+++ /dev/null
@@ -1,31 +0,0 @@
-From fb8b895385a641d74f2186fe5f20a872209692ed Mon Sep 17 00:00:00 2001

[OE-core] [PATCH] enchant: add PACKAGECONFIG for *spell

[Martin Jansa]

* use PACKAGECONFIG for various *spell implementations

* keep aspell enabled by default

* prevent hunspell/myspell being autodetected as reported in "bitbake world 
status" e-mails:
  WARN: enchant: enchant rdepends on hunspell, but it isn't a build dependency?

Signed-off-by: Martin Jansa 
---
 meta/recipes-support/enchant/enchant_1.6.0.bb | 16 +---
 1 file changed, 9 insertions(+), 7 deletions(-)

diff --git a/meta/recipes-support/enchant/enchant_1.6.0.bb 
b/meta/recipes-support/enchant/enchant_1.6.0.bb
index 97a4761..44eb2e3 100644
--- a/meta/recipes-support/enchant/enchant_1.6.0.bb
+++ b/meta/recipes-support/enchant/enchant_1.6.0.bb
@@ -7,7 +7,7 @@ LICENSE = "LGPLv2.1+"
 LIC_FILES_CHKSUM = "file://COPYING.LIB;md5=dfcbabf9131dc9a95febef6753a2958b \
 
file://src/enchant.h;beginline=1;endline=29;md5=8d881caa1d37523567e1d8f726675a18"
 
-DEPENDS = "aspell glib-2.0"
+DEPENDS = "glib-2.0"
 
 inherit autotools pkgconfig
 
@@ -18,15 +18,17 @@ SRC_URI = 
"http://www.abisource.com/downloads/enchant/${PV}/enchant-${PV}.tar.gz
 SRC_URI[md5sum] = "de11011aff801dc61042828041fb59c7"
 SRC_URI[sha256sum] = 
"2fac9e7be7e9424b2c5570d8affe568db39f7572c10ed48d4e13cddf03f7097f"
 
-EXTRA_OECONF = "--with-aspell-prefix=${STAGING_DIR_HOST}${prefix} \
-   --enable-aspell br_cv_binreloc=no \
-   "
+PACKAGECONFIG ??= "aspell"
+PACKAGECONFIG[aspell]  = " --with-aspell-prefix=${STAGING_DIR_HOST}${prefix}  
--enable-aspell,  --disable-aspell,  aspell,  aspell"
+PACKAGECONFIG[ispell]  = " --with-ispell-prefix=${STAGING_DIR_HOST}${prefix}  
--enable-ispell,  --disable-ispell,  ispell,  ispell"
+PACKAGECONFIG[uspell]  = " --with-uspell-prefix=${STAGING_DIR_HOST}${prefix}  
--enable-uspell,  --disable-uspell,  uspell,  uspell"
+PACKAGECONFIG[hspell]  = " --with-hspell-prefix=${STAGING_DIR_HOST}${prefix}  
--enable-hspell,  --disable-hspell,  hspell,  hspell"
+PACKAGECONFIG[myspell] = "--with-myspell-prefix=${STAGING_DIR_HOST}${prefix} 
--enable-myspell, --disable-myspell, myspell, myspell"
+
+EXTRA_OECONF = "br_cv_binreloc=no"
 
 export CXXFLAGS += " -L${STAGING_LIBDIR} -lstdc++ "
 
 FILES_${PN} = "${bindir} ${libdir}/*${SOLIBS} ${datadir}/${BPN} 
${libdir}/${BPN}/*.so"
 FILES_${PN}-dev += "${libdir}/${BPN}/*{SOLIBSDEV} ${libdir}/${BPN}/*.la"
 FILES_${PN}-staticdev += "${libdir}/${BPN}/*.a"
-
-RDEPENDS_${PN} += "aspell"
-
-- 
2.10.0

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [PATCH] bash2dash conversion

[Burton, Ross]

On 19 September 2016 at 12:57, Peter Kjellerstedt <
peter.kjellerst...@axis.com> wrote:

> > ++mem_exists="`grep "^$groupname:[!:]*:[!:]*:\([!,
> ]*,\)*$username\(,[!,]*\)*"$rootdir/etc/group || true`"
> >   if test "x$mem_exists" = "x"; then
> >   bbfatal "${PN}: groupmems command did not succeed."
> >   fi
>
> The above change cannot be correct. Changing the expression "[^:]"
> (which means "anything but :") to "[!:]" (which means "! or :") is
> definitely not the same


My prediction is that this series is generated by running checkbashism over
the fragments, it fires a false-positive here (from memory because it
thinks it is processing a bash glob or something, not grep regex).

Note that I just submitted my verify-bashism script which has a whitelist
for things - such as use of command - which whilst not in POSIX are in fact
in bash/dash/ash so for all intents and purposes will work.

Ross
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [PATCH] bash2dash conversion

[Peter Kjellerstedt]

> -Original Message-
> From: openembedded-core-boun...@lists.openembedded.org
> [mailto:openembedded-core-boun...@lists.openembedded.org] On Behalf Of
> zhe...@windriver.com
> Sent: den 18 september 2016 04:52
> To: openembedded-core@lists.openembedded.org
> Subject: [OE-core] [PATCH] bash2dash conversion
 ^
Typically this is referred to as "Remove bashisms"...

> From: "Tim K. Chan" 
> 
> Change bash style to dash style
> 
> Signed-off-by: Tim K. Chan 
> [Adjust context]
> Signed-off-by: He Zhe 
> ---
>  meta/classes/systemd.bbclass|  4 ++--
>  meta/classes/update-rc.d.bbclass|  6 +++---
>  meta/classes/useradd_base.bbclass   |  4 ++--
>  meta/recipes-connectivity/resolvconf/resolvconf_1.79.bb |  2 +-
>  meta/recipes-core/glibc/glibc-package.inc   |  2 +-
>  meta/recipes-devtools/guile/guile_2.0.12.bb |  6 --
>  meta/recipes-devtools/rpm/rpm_5.4.16.bb | 13 +++--
>  7 files changed, 24 insertions(+), 13 deletions(-)

[cut]

> diff --git a/meta/classes/useradd_base.bbclass
> b/meta/classes/useradd_base.bbclass
> index f4dc713..35d5f06 100644
> --- a/meta/classes/useradd_base.bbclass
> +++ b/meta/classes/useradd_base.bbclass
> @@ -59,10 +59,10 @@ perform_groupmems () {
>   gshadow="no"
>   touch $rootdir${sysconfdir}/gshadow
>   fi
> - local mem_exists="`grep 
> "^$groupname:[^:]*:[^:]*:\([^,]*,\)*$username\(,[^,]*\)*"$rootdir/etc/group 
> || true`"
> + local mem_exists="`grep 
> "^$groupname:[!:]*:[!:]*:\([!,]*,\)*$username\(,[!,]*\)*"$rootdir/etc/group 
> || true`"
>   if test "x$mem_exists" = "x"; then
>   eval flock -x $rootdir${sysconfdir} -c \"$PSEUDO groupmems 
> \$opts\" || true
> - mem_exists="`grep 
> "^$groupname:[^:]*:[^:]*:\([^,]*,\)*$username\(,[^,]*\)*"$rootdir/etc/group 
> || true`"
> ++mem_exists="`grep 
> "^$groupname:[!:]*:[!:]*:\([!,]*,\)*$username\(,[!,]*\)*"$rootdir/etc/group 
> || true`"
>   if test "x$mem_exists" = "x"; then
>   bbfatal "${PN}: groupmems command did not succeed."
>   fi

The above change cannot be correct. Changing the expression "[^:]" 
(which means "anything but :") to "[!:]" (which means "! or :") is 
definitely not the same

> diff --git a/meta/recipes-devtools/guile/guile_2.0.12.bb
> b/meta/recipes-devtools/guile/guile_2.0.12.bb
> index d2fe511..3ada0f1 100644
> --- a/meta/recipes-devtools/guile/guile_2.0.12.bb
> +++ b/meta/recipes-devtools/guile/guile_2.0.12.bb
> @@ -91,8 +91,10 @@ guile_cross_config() { 
>   then
>   # Create guile-config returning target values instead of native 
> values
>   install -d ${SYSROOT_DESTDIR}${STAGING_BINDIR_CROSS}
> - echo '#!'`which ${BUILD_SYS}-guile`$' \\\n--no-auto-compile -e 
> main -s\n!#\n(define %guile-build-info '\'\( \
> - > ${B}/guile-config.cross
> + echo -n '#!' > ${B}/guile-config.cross
> + echo -n `which x86_64-linux-guile` >> ${B}/guile-config.cross
> + printf ' \\\n--no-auto-compile -e main -s\n!#\n(define 
> %%guile-build-info ' >> ${B}/guile-config.cross
> + echo "'(" >> ${B}/guile-config.cross
>   sed -n -e 's:^[ \t]*{[ \t]*":  (:' \
>   -e 's:",[ \t]*": . ":' \
>   -e 's:" *}, *\\:"):' \

I suggest to replace the entire guile_cross_config() function with this:

guile_cross_config() {
# this is only for target recipe
[ "${PN}" = "${BPN}" ] || return 0

vars=$(sed -n -e 's:^[ \t]*{[ \t]*":  (:' \
  -e 's:",[ \t]*": . ":' \
  -e 's:" *}, *\\:"):' \
  -e 's:^.*cachedir.*$::' \
  -e '/^  (/p' \
   < ${B}/libguile/libpath.h)

# Create guile-config returning target values instead of native values
install -d ${SYSROOT_DESTDIR}${bindir_crossscripts}
cat <${B}/guile-config.cross
#!$(which ${BUILD_SYS}-guile) \\
--no-auto-compile -e main -s
!#
(define %guile-build-info '(
$vars
))
EOF
cat ${B}/meta/guile-config >> ${B}/guile-config.cross
install ${B}/guile-config.cross 
${SYSROOT_DESTDIR}${bindir_crossscripts}/guile-config
}

That should make it a lot simpler to see what is going on.
Please note that I have corrected the installation path as well.

//Peter

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

[OE-core] [OE-Core][Patch] arch-mips: Restructure mips64 and add mips64r2

[Zubair Lutfullah Kakakhel]

The current file structure felt slightly unsuitable for adding
MIPS64r2. So I restructured it slightly and added MIPS64r2
support

Signed-off-by: Zubair Lutfullah Kakakhel 
---
 meta/conf/machine/include/mips/arch-mips.inc | 60 
 meta/conf/machine/include/tune-mips32.inc| 22 +++-
 meta/conf/machine/include/tune-mips64.inc| 80 +-
 meta/conf/machine/include/tune-mips64r2.inc  | 84 
 4 files changed, 184 insertions(+), 62 deletions(-)
 create mode 100644 meta/conf/machine/include/tune-mips64r2.inc

diff --git a/meta/conf/machine/include/mips/arch-mips.inc 
b/meta/conf/machine/include/mips/arch-mips.inc
index d3e83d1..6be84be 100644
--- a/meta/conf/machine/include/mips/arch-mips.inc
+++ b/meta/conf/machine/include/mips/arch-mips.inc
@@ -42,64 +42,4 @@ MIPSPKGSFX_ABI = "${@bb.utils.contains('TUNE_FEATURES', 
'n32', '-n32', '', d)}"
 TUNE_ARCH = "mips${MIPSPKGSFX_BYTE}${MIPSPKGSFX_ENDIAN}"
 TUNE_PKGARCH = 
"${MIPSPKGSFX_VARIANT_tune-${DEFAULTTUNE}}${MIPSPKGSFX_FPU}${MIPSPKGSFX_ABI}"
 
-# Base tunes
-AVAILTUNES += "mips mips64-n32 mips64 mipsel mips64el-n32 mips64el mips-nf 
mips64-nf-n32 mips64-nf mipsel-nf mips64el-nf-n32 mips64el-nf"
-TUNE_FEATURES_tune-mips = "o32 bigendian fpu-hard"
-BASE_LIB_tune-mips = "lib"
-MIPSPKGSFX_VARIANT_tune-mips = "${TUNE_ARCH}"
-PACKAGE_EXTRA_ARCHS_tune-mips = "mips"
 
-TUNE_FEATURES_tune-mips64-n32 = "n32 bigendian fpu-hard"
-BASE_LIB_tune-mips64-n32 = "lib32"
-MIPSPKGSFX_VARIANT_tune-mips64-n32 = "${TUNE_ARCH}"
-PACKAGE_EXTRA_ARCHS_tune-mips64-n32 = "mips64-n32"
-
-TUNE_FEATURES_tune-mips64 = "n64 bigendian fpu-hard"
-BASE_LIB_tune-mips64 = "lib64"
-MIPSPKGSFX_VARIANT_tune-mips64 = "${TUNE_ARCH}"
-PACKAGE_EXTRA_ARCHS_tune-mips64 = "mips64"
-
-TUNE_FEATURES_tune-mipsel = "o32 fpu-hard"
-BASE_LIB_tune-mipsel = "lib"
-MIPSPKGSFX_VARIANT_tune-mipsel = "${TUNE_ARCH}"
-PACKAGE_EXTRA_ARCHS_tune-mipsel = "mipsel"
-
-TUNE_FEATURES_tune-mips64el-n32 = "n32 fpu-hard"
-BASE_LIB_tune-mips64el-n32 = "lib32"
-MIPSPKGSFX_VARIANT_tune-mips64el-n32 = "${TUNE_ARCH}"
-PACKAGE_EXTRA_ARCHS_tune-mips64el-n32 = "mips64el-n32"
-
-TUNE_FEATURES_tune-mips64el = "n64 fpu-hard"
-BASE_LIB_tune-mips64el = "lib64"
-MIPSPKGSFX_VARIANT_tune-mips64el = "${TUNE_ARCH}"
-PACKAGE_EXTRA_ARCHS_tune-mips64el = "mips64el"
-
-TUNE_FEATURES_tune-mips-nf = "o32 bigendian"
-BASE_LIB_tune-mips-nf = "lib"
-MIPSPKGSFX_VARIANT_tune-mips-nf = "${TUNE_ARCH}"
-PACKAGE_EXTRA_ARCHS_tune-mips-nf = "mips-nf"
-
-TUNE_FEATURES_tune-mips64-nf-n32 = "n32 bigendian"
-BASE_LIB_tune-mips64-nf-n32 = "lib32"
-MIPSPKGSFX_VARIANT_tune-mips64-nf-n32 = "${TUNE_ARCH}"
-PACKAGE_EXTRA_ARCHS_tune-mips64-nf-n32 = "mips64-nf-n32"
-
-TUNE_FEATURES_tune-mips64-nf = "n64 bigendian"
-BASE_LIB_tune-mips64-nf = "lib64"
-MIPSPKGSFX_VARIANT_tune-mips64-nf = "${TUNE_ARCH}"
-PACKAGE_EXTRA_ARCHS_tune-mips64-nf = "mips64-nf"
-
-TUNE_FEATURES_tune-mipsel-nf = "o32"
-BASE_LIB_tune-mipsel-nf = "lib"
-MIPSPKGSFX_VARIANT_tune-mipsel-nf = "${TUNE_ARCH}"
-PACKAGE_EXTRA_ARCHS_tune-mipsel-nf = "mipsel-nf"
-
-TUNE_FEATURES_tune-mips64el-nf-n32 = "n32"
-BASE_LIB_tune-mips64el-nf-n32 = "lib32"
-MIPSPKGSFX_VARIANT_tune-mips64el-nf-n32 = "${TUNE_ARCH}"
-PACKAGE_EXTRA_ARCHS_tune-mips64el-nf-n32 = "mips64el-nf-n32"
-
-TUNE_FEATURES_tune-mips64el-nf = "n64"
-BASE_LIB_tune-mips64el-nf = "lib64"
-MIPSPKGSFX_VARIANT_tune-mips64el-nf = "${TUNE_ARCH}"
-PACKAGE_EXTRA_ARCHS_tune-mips64el-nf = "mips64el-nf"
diff --git a/meta/conf/machine/include/tune-mips32.inc 
b/meta/conf/machine/include/tune-mips32.inc
index ce0445f..4c3d93f 100644
--- a/meta/conf/machine/include/tune-mips32.inc
+++ b/meta/conf/machine/include/tune-mips32.inc
@@ -6,7 +6,27 @@ TUNEVALID[mips32] = "Enable mips32 specific processor 
optimizations"
 TUNECONFLICTS[mips32] = "n64 n32"
 TUNE_CCARGS .= "${@bb.utils.contains('TUNE_FEATURES', 'mips32', ' 
-march=mips32', '', d)}"
 
-AVAILTUNES += "mips32 mips32el mips32-nf mips32el-nf"
+AVAILTUNES += "mips mipsel mips-nf mipsel-nf mips32 mips32el mips32-nf 
mips32el-nf"
+
+TUNE_FEATURES_tune-mips = "o32 bigendian fpu-hard"
+BASE_LIB_tune-mips = "lib"
+MIPSPKGSFX_VARIANT_tune-mips = "${TUNE_ARCH}"
+PACKAGE_EXTRA_ARCHS_tune-mips = "mips"
+
+TUNE_FEATURES_tune-mipsel = "o32 fpu-hard"
+BASE_LIB_tune-mipsel = "lib"
+MIPSPKGSFX_VARIANT_tune-mipsel = "${TUNE_ARCH}"
+PACKAGE_EXTRA_ARCHS_tune-mipsel = "mipsel"
+
+TUNE_FEATURES_tune-mips-nf = "o32 bigendian"
+BASE_LIB_tune-mips-nf = "lib"
+MIPSPKGSFX_VARIANT_tune-mips-nf = "${TUNE_ARCH}"
+PACKAGE_EXTRA_ARCHS_tune-mips-nf = "mips-nf"
+
+TUNE_FEATURES_tune-mipsel-nf = "o32"
+BASE_LIB_tune-mipsel-nf = "lib"
+MIPSPKGSFX_VARIANT_tune-mipsel-nf = "${TUNE_ARCH}"
+PACKAGE_EXTRA_ARCHS_tune-mipsel-nf = "mipsel-nf"
 
 TUNE_FEATURES_tune-mips32 = "${TUNE_FEATURES_tune-mips} mips32"
 MIPSPKGSFX_VARIANT_tune-mips32 = "mips32"
diff --git a/meta/conf/machine/include/tune-mips64.inc 
b/meta/conf/machine/include/tune-mips64.inc
index 

Re: [OE-core] [PATCH] perf: Fix to obey LD failure on host i686

[sujith h]

On Thu, Sep 8, 2016 at 12:36 PM, Andre McCurdy  wrote:

> On Wed, Sep 7, 2016 at 11:51 PM, Sujith H  wrote:
> > From: Christopher Larson 
> >
> > When built on an i686 host for qemux86-64 without the
> > fix to obey LD and it fails:
> >
> > /scratch/dogwood/toolchains/x86_64/bin/i686-pc-linux-gnu-ld:
> > Relocatable linking with relocations from format elf64-x86-64
> > (/scratch/dogwood/perf-ld-test/build/tmp/work/qemux86_
> 64-mel-linux/perf/1.0-r9/perf-1.0/fs/fs.o)
> > to format elf32-i386 (/scratch/dogwood/perf-ld-
> test/build/tmp/work/qemux86_64-mel-linux/perf/1.0-r9/perf-
> 1.0/fs/libapi-in.o)
> > is not supported
> >
> > This is because LD includes HOST_LD_ARCH, which contains TUNE_LDARGS,
> > which is -m elf32_x86_64 for x86_64. Without that, direct use of ld will
> fail.
> >
> > Signed-off-by: Christopher Larson 
> > Signed-off-by: Sujith Haridasan 
> > ---
> >  meta/recipes-kernel/perf/perf.bb | 9 +
> >  1 file changed, 9 insertions(+)
> >
> > diff --git a/meta/recipes-kernel/perf/perf.bb
> b/meta/recipes-kernel/perf/perf.bb
> > index 88e3a0a..85fe0ea 100644
> > --- a/meta/recipes-kernel/perf/perf.bb
> > +++ b/meta/recipes-kernel/perf/perf.bb
> > @@ -79,6 +79,7 @@ EXTRA_OEMAKE = '\
> >  ARCH=${ARCH} \
> >  CC="${CC}" \
> >  AR="${AR}" \
> > +LD="${LD}" \
> >  EXTRA_CFLAGS="-ldw" \
> >  perfexecdir=${libexecdir} \
> >  NO_GTK2=1 ${TUI_DEFINES} NO_DWARF=1 ${LIBUNWIND_DEFINES} \
> > @@ -98,6 +99,14 @@ EXTRA_OEMAKE += "\
> >  'infodir=${@os.path.relpath(infodir, prefix)}' \
> >  "
> >
> > +do_configure_prepend () {
> > +for makefile in "${S}/tools/perf/Makefile.perf" \
> > +"${S}/tools/lib/api/Makefile"; do
> > +if [ -e "$makefile" ]; then
> > +sed -i 's,LD = $(CROSS_COMPILE)ld,#LD,' "$makefile"
> > +fi
> > +done
> > +}
>
> Isn't passing LD via the Make command line enough to over-ride these
> definitions in the Makefiles?
>

Unfortunately that didn't helped I believe. That's the reason, this patch
was created.


>
> >  do_compile() {
> > # Linux kernel build system is expected to do the right thing
> > --
> > 1.9.1
> >
> > --
> > ___
> > Openembedded-core mailing list
> > Openembedded-core@lists.openembedded.org
> > http://lists.openembedded.org/mailman/listinfo/openembedded-core
>



-- 
സുജിത് ഹരിദാസന്
Bangalore
Contributor to KDE project
Contributor to Yocto project
http://fci.wikia.com/wiki/Anti-DRM-Campaign
 http://sujithh.info
C-x C-c
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [PATCH v2 1/1] Make yocto-spdx support spdx2.0 SPEC

[Maxin B. John]

Hi,

Please find my comments below:

On Mon, Sep 19, 2016 at 04:39:50PM +0800, Lei Maohui wrote:
> More:
> - change spdx tool from fossology to dosocs2

It would be nice to include the reason for change from fossology to dosocs2
in the commit message too (from cover letter)

> Signed-off-by: Lei Maohui 
> ---
>  meta/classes/spdx.bbclass | 505 
> ++
>  meta/conf/licenses.conf   |  67 +-
>  2 files changed, 198 insertions(+), 374 deletions(-)
> 
> diff --git a/meta/classes/spdx.bbclass b/meta/classes/spdx.bbclass
> index 0c92765..27c0fa0 100644
> --- a/meta/classes/spdx.bbclass
> +++ b/meta/classes/spdx.bbclass
> @@ -1,365 +1,252 @@
>  # This class integrates real-time license scanning, generation of SPDX 
> standard
>  # output and verifiying license info during the building process.
> -# It is a combination of efforts from the OE-Core, SPDX and Fossology 
> projects.
> +# It is a combination of efforts from the OE-Core, SPDX and DoSOCSv2 
> projects.
>  #
> -# For more information on FOSSology:
> -#   http://www.fossology.org
> -#
> -# For more information on FOSSologySPDX commandline:
> -#   https://github.com/spdx-tools/fossology-spdx/wiki/Fossology-SPDX-Web-API
> +# For more information on DoSOCSv2:
> +#   https://github.com/DoSOCSv2

Instead of requesting the user to install the DoSOCSv2 from github or other 
repos,
can we make the spdx.bbclass depend on "dosocs-native" or similar and make that
"DoSOCSv2" recipe available in oe-core ?

That might make it easy to use this class.

>  # For more information on SPDX:
>  #   http://www.spdx.org
>  #
> +# Note:
> +# 1) Make sure DoSOCSv2 has beed installed in your host
> +# 2) By default,spdx files will be output to the path which is defined 
> as[SPDX_MANIFEST_DIR] 
> +#in ./meta/conf/licenses.conf.
>  
> -# SPDX file will be output to the path which is defined 
> as[SPDX_MANIFEST_DIR] 
> -# in ./meta/conf/licenses.conf.
> +SPDXOUTPUTDIR = "${WORKDIR}/spdx_output_dir"
>  SPDXSSTATEDIR = "${WORKDIR}/spdx_sstate_dir"
>  
>  # If ${S} isn't actually the top-level source directory, set SPDX_S to point 
> at
>  # the real top-level directory.
> +
>  SPDX_S ?= "${S}"
>  
>  python do_spdx () {
>  import os, sys
> -import json, shutil
> -
> -info = {} 
> -info['workdir'] = d.getVar('WORKDIR', True)
> -info['sourcedir'] = d.getVar('SPDX_S', True)
> -info['pn'] = d.getVar('PN', True)
> -info['pv'] = d.getVar('PV', True)
> -info['spdx_version'] = d.getVar('SPDX_VERSION', True)
> -info['data_license'] = d.getVar('DATA_LICENSE', True)
> -
> -sstatedir = d.getVar('SPDXSSTATEDIR', True)
> -sstatefile = os.path.join(sstatedir, info['pn'] + info['pv'] + ".spdx")
> +import json
>  
> -manifest_dir = d.getVar('SPDX_MANIFEST_DIR', True)
> -info['outfile'] = os.path.join(manifest_dir, info['pn'] + ".spdx" )
> +## It's no necessary  to get spdx files for *-native
> +if d.getVar('PN', True) == d.getVar('BPN', True) + "-native": 
> +return None
>  
> -info['spdx_temp_dir'] = d.getVar('SPDX_TEMP_DIR', True)
> -info['tar_file'] = os.path.join(info['workdir'], info['pn'] + ".tar.gz" )
> +## gcc is too big to get spdx file.
> +if 'gcc' in d.getVar('PN', True):
> +return None   
>  
> -# Make sure important dirs exist
> -try:
> -bb.utils.mkdirhier(manifest_dir)
> -bb.utils.mkdirhier(sstatedir)
> -bb.utils.mkdirhier(info['spdx_temp_dir'])
> -except OSError as e:
> -bb.error("SPDX: Could not set up required directories: " + str(e))
> -return
> +info = {} 
> +info['workdir'] = (d.getVar('WORKDIR', True) or "")
> +info['pn'] = (d.getVar( 'PN', True ) or "")
> +info['pv'] = (d.getVar( 'PV', True ) or "")
> +info['package_download_location'] = (d.getVar( 'SRC_URI', True ) or "")
> +if info['package_download_location'] != "":
> +info['package_download_location'] = 
> info['package_download_location'].split()[0]
> +info['spdx_version'] = (d.getVar('SPDX_VERSION', True) or '')
> +info['data_license'] = (d.getVar('DATA_LICENSE', True) or '')
> +info['creator'] = {}
> +info['creator']['Tool'] = (d.getVar('CREATOR_TOOL', True) or '')
> +info['license_list_version'] = (d.getVar('LICENSELISTVERSION', True) or 
> '')
> +info['package_homepage'] = (d.getVar('HOMEPAGE', True) or "")
> +info['package_summary'] = (d.getVar('SUMMARY', True) or "")
> +info['package_summary'] = info['package_summary'].replace("\n","")
> +info['package_summary'] = info['package_summary'].replace("'"," ")
> +
> +spdx_sstate_dir = (d.getVar('SPDXSSTATEDIR', True) or "")
> +manifest_dir = (d.getVar('SPDX_MANIFEST_DIR', True) or "")
> +info['outfile'] = os.path.join(manifest_dir, info['pn'] + "-" + 
> info['pv'] + ".spdx" )
> +sstatefile = os.path.join(spdx_sstate_dir, 
> +info['pn'] + "-" + info['pv'] + ".spdx" )

Re: [OE-core] [PATCH V2 8/8] runqemu: improve finding of rootfs, kernel and dtb

[Robert Yang]

On 09/19/2016 05:12 PM, Joshua Lock wrote:

On Sun, 2016-09-18 at 00:39 -0700, Robert Yang wrote:

* Search rootfs in the following order:
  - IMAGE_NAME*.FSTYPE
  - IMAGE_LINK_NAME*.FSTYPE

* Search kernel in the following order:
  - QB_DEFAULT_KERNEL
  - KERNEL_IMAGETYPE
  - KERNEL_IMAGETYPE*

* Search dtb in the following order:
   - QB_DTB
   - QB_DTB*
   - *.dtb

* Fix DTB, it should only work with "-kernel" option.

[YOCTO #10265]

Signed-off-by: Robert Yang 
---
 scripts/runqemu | 68 ++-
--
 1 file changed, 41 insertions(+), 27 deletions(-)

diff --git a/scripts/runqemu b/scripts/runqemu
index 60e2093..1c4e69b 100755
--- a/scripts/runqemu
+++ b/scripts/runqemu
@@ -157,6 +157,7 @@ class BaseConfig(object):
 self.kernel = ''
 self.kernel_cmdline = ''
 self.kernel_cmdline_script = ''
+self.dtb = ''
 self.fstype = ''
 self.kvm_enabled = False
 self.vhost_enabled = False
@@ -440,23 +441,23 @@ class BaseConfig(object):
 if self.fstype == 'nfs':
 return

+cmd_name = '%s/%s*.%s' % (self.get('DEPLOY_DIR_IMAGE'),
self.get('IMAGE_NAME'), self.fstype)
+cmd_link = '%s/%s*.%s' % (self.get('DEPLOY_DIR_IMAGE'),
self.get('IMAGE_LINK_NAME'), self.fstype)
+cmds = (cmd_name, cmd_link)
 if self.rootfs and not os.path.exists(self.rootfs):
 # Lazy rootfs
 self.rootfs = "%s/%s-%s.%s" %
(self.get('DEPLOY_DIR_IMAGE'),
 self.rootfs, self.get('MACHINE'),
 self.fstype)
 elif not self.rootfs:
-cmd = '%s/%s*.%s' % (self.get('DEPLOY_DIR_IMAGE'),
self.get('IMAGE_NAME'), self.fstype)
-all_files = glob.glob(cmd)
-if all_files:
-self.rootfs = all_files[0]
-else:
-cmd = '%s/%s*.%s' % (self.get('DEPLOY_DIR_IMAGE'),
self.get('IMAGE_LINK_NAME'), self.fstype)
+for cmd in cmds:
 all_files = glob.glob(cmd)
 if all_files:
 self.rootfs = all_files[0]
-else:
-raise Exception("Failed to find rootfs: %s" %
cmd)
+break
+
+if not self.rootfs:
+raise Exception("Failed to find rootfs: %s or %s" %
cmds)

 if not os.path.exists(self.rootfs):
 raise Exception("Can't find rootfs: %s" % self.rootfs)
@@ -466,28 +467,37 @@ class BaseConfig(object):
 # The vm image doesn't need a kernel
 if self.fstype in self.vmtypes:
 return
-kernel = self.kernel
+
 deploy_dir_image = self.get('DEPLOY_DIR_IMAGE')
-if not kernel:
-kernel = "%s/%s" % (deploy_dir_image,
self.get('QB_DEFAULT_KERNEL'))
+if not self.kernel:
+kernel_match_name = "%s/%s" % (deploy_dir_image,
self.get('QB_DEFAULT_KERNEL'))
+kernel_match_link = "%s/%s" % (deploy_dir_image,
self.get('KERNEL_IMAGETYPE'))
+kernel_startswith = "%s/%s*" % (deploy_dir_image,
self.get('KERNEL_IMAGETYPE'))


There are qemuboot.conf files in the wild which won't contain
KERNEL_IMAGETYPE, at which point we're just looking for matches to
DEPLOY_DIR_IMAGE or DEPLOY_DIR_IMAGE/*

I think we need to add some extra handling so that we don't end up
setting kernel to either DEPLOY_DIR_IMAGE or its first child?


Thanks, updated in the repo:

  git://git.openembedded.org/openembedded-core-contrib rbt/rq
  http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=rbt/rq

Joshua Lock (6):
  runqemu: add guidance to resolve issues with missing files
  qemuboot: write the full kernel filename, not the link name
  runqemu: clarify an INFO message
  qemuboot: also write the kernel link name to the conf file
  runqemu: try symlinks when kernel or rootfs can't be found
  runqemu: work even if a *.qemuboot.conf isn't found

Robert Yang (2):
  runqemu: use OECORE_NATIVE_SYSROOT from sdk
  runqemu: improve finding of rootfs, kernel and dtb

// Robert



Joshua


+cmds = (kernel_match_name, kernel_match_link,
kernel_startswith)
+for cmd in cmds:
+all_files = glob.glob(cmd)
+if all_files:
+self.kernel = all_files[0]
+break
+if not self.kernel:
+raise Exception('KERNEL not found: %s, %s or %s' %
cmds)

-if os.path.exists(kernel):
-self.kernel = kernel
-else:
-kernel = "%s/%s" % (deploy_dir_image,
self.get('KERNEL_IMAGETYPE'))
-if kernel != deploy_dir_image and
os.path.exists(kernel):
-self.kernel = kernel
-else:
-raise Exception("KERNEL %s not found" % kernel)
+if not os.path.exists(self.kernel):
+raise Exception("KERNEL %s not found" % self.kernel)

 dtb = self.get('QB_DTB')
 if dtb:

[OE-core] [PATCH v2] boost: switch to using C++11 atomics when available

[André Draszik]

The alleviates the need to use and maintain hand-written
assembly, just relying on the compiler to do the right
thing.

Signed-off-by: André Draszik 
---
 ...by-default-when-BOOST_NO_CXX11_HDR_ATOMIC.patch | 59 ++
 meta/recipes-support/boost/boost_1.61.0.bb |  1 +
 2 files changed, 60 insertions(+)
 create mode 100644 
meta/recipes-support/boost/boost/0004-Use-atomic-by-default-when-BOOST_NO_CXX11_HDR_ATOMIC.patch

diff --git 
a/meta/recipes-support/boost/boost/0004-Use-atomic-by-default-when-BOOST_NO_CXX11_HDR_ATOMIC.patch
 
b/meta/recipes-support/boost/boost/0004-Use-atomic-by-default-when-BOOST_NO_CXX11_HDR_ATOMIC.patch
new file mode 100644
index 000..ab7826b
--- /dev/null
+++ 
b/meta/recipes-support/boost/boost/0004-Use-atomic-by-default-when-BOOST_NO_CXX11_HDR_ATOMIC.patch
@@ -0,0 +1,59 @@
+From c234cc557f60729e071d6da59747c1a9289555c5 Mon Sep 17 00:00:00 2001
+From: Peter Dimov 
+Date: Sun, 28 Aug 2016 21:28:21 +0300
+Subject: [PATCH 4/4] Use  by default when BOOST_NO_CXX11_HDR_ATOMIC is
+ not defined
+
+---
+Upstream-Status: Backport 
[https://github.com/boostorg/smart_ptr/commit/20fedcff2ca3143503ec4e876d47745ab0ec7b0c]
+Signed-off-by: André Draszik 
+ boost/smart_ptr/detail/atomic_count.hpp| 3 +++
+ boost/smart_ptr/detail/sp_counted_base.hpp | 3 +++
+ boost/smart_ptr/detail/spinlock.hpp| 3 +++
+ 3 files changed, 9 insertions(+)
+
+diff --git a/boost/smart_ptr/detail/atomic_count.hpp 
b/boost/smart_ptr/detail/atomic_count.hpp
+index 8aefd44..6e4f71a 100644
+--- a/boost/smart_ptr/detail/atomic_count.hpp
 b/boost/smart_ptr/detail/atomic_count.hpp
+@@ -73,6 +73,9 @@
+ #elif defined( BOOST_DISABLE_THREADS ) && !defined( BOOST_SP_ENABLE_THREADS ) 
&& !defined( BOOST_DISABLE_WIN32 )
+ # include 
+ 
++#elif !defined( BOOST_NO_CXX11_HDR_ATOMIC )
++# include 
++
+ #elif defined( __GNUC__ ) && ( defined( __i386__ ) || defined( __x86_64__ ) ) 
&& !defined( __PATHSCALE__ )
+ # include 
+ 
+diff --git a/boost/smart_ptr/detail/sp_counted_base.hpp 
b/boost/smart_ptr/detail/sp_counted_base.hpp
+index 0995ca8..83ede23 100644
+--- a/boost/smart_ptr/detail/sp_counted_base.hpp
 b/boost/smart_ptr/detail/sp_counted_base.hpp
+@@ -44,6 +44,9 @@
+ #elif defined( BOOST_SP_HAS_CLANG_C11_ATOMICS )
+ # include 
+ 
++#elif !defined( BOOST_NO_CXX11_HDR_ATOMIC )
++# include 
++
+ #elif defined( __SNC__ )
+ # include 
+ 
+diff --git a/boost/smart_ptr/detail/spinlock.hpp 
b/boost/smart_ptr/detail/spinlock.hpp
+index 19f93d7..0b618df 100644
+--- a/boost/smart_ptr/detail/spinlock.hpp
 b/boost/smart_ptr/detail/spinlock.hpp
+@@ -43,6 +43,9 @@
+ #elif defined( BOOST_SP_USE_PTHREADS )
+ #  include 
+ 
++#elif !defined( BOOST_NO_CXX11_HDR_ATOMIC )
++#  include 
++
+ #elif defined(__GNUC__) && defined( __arm__ ) && !defined( __thumb__ )
+ #  include 
+ 
+-- 
+2.9.3
+
diff --git a/meta/recipes-support/boost/boost_1.61.0.bb 
b/meta/recipes-support/boost/boost_1.61.0.bb
index 6926e84..33f209c 100644
--- a/meta/recipes-support/boost/boost_1.61.0.bb
+++ b/meta/recipes-support/boost/boost_1.61.0.bb
@@ -8,4 +8,5 @@ SRC_URI += "\
 file://0001-boost-asio-detail-socket_types.hpp-fix-poll.h-includ.patch \
 file://0002-boost-test-execution_monitor.hpp-fix-mips-soft-float.patch \
 file://0003-smart_ptr-mips-assembly-doesn-t-compile-in-mips16e-m.patch \
+file://0004-Use-atomic-by-default-when-BOOST_NO_CXX11_HDR_ATOMIC.patch \
 "
-- 
2.9.3

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

[OE-core] [PATCH] boost: switch to using C++11 atomics when available

[André Draszik]

The alleviates the need to use and maintain hand-written
assembly, just relying on the compiler to do the right
thing.

Signed-off-by: André Draszik 
---
 ...by-default-when-BOOST_NO_CXX11_HDR_ATOMIC.patch | 58 ++
 meta/recipes-support/boost/boost_1.61.0.bb |  1 +
 2 files changed, 59 insertions(+)
 create mode 100644 
meta/recipes-support/boost/boost/0004-Use-atomic-by-default-when-BOOST_NO_CXX11_HDR_ATOMIC.patch

diff --git 
a/meta/recipes-support/boost/boost/0004-Use-atomic-by-default-when-BOOST_NO_CXX11_HDR_ATOMIC.patch
 
b/meta/recipes-support/boost/boost/0004-Use-atomic-by-default-when-BOOST_NO_CXX11_HDR_ATOMIC.patch
new file mode 100644
index 000..44b8b49
--- /dev/null
+++ 
b/meta/recipes-support/boost/boost/0004-Use-atomic-by-default-when-BOOST_NO_CXX11_HDR_ATOMIC.patch
@@ -0,0 +1,58 @@
+From c234cc557f60729e071d6da59747c1a9289555c5 Mon Sep 17 00:00:00 2001
+From: Peter Dimov 
+Date: Sun, 28 Aug 2016 21:28:21 +0300
+Subject: [PATCH 4/4] Use  by default when BOOST_NO_CXX11_HDR_ATOMIC is
+ not defined
+
+---
+Upstream-Status: Backport 
https://github.com/boostorg/smart_ptr/commit/20fedcff2ca3143503ec4e876d47745ab0ec7b0c
+ boost/smart_ptr/detail/atomic_count.hpp| 3 +++
+ boost/smart_ptr/detail/sp_counted_base.hpp | 3 +++
+ boost/smart_ptr/detail/spinlock.hpp| 3 +++
+ 3 files changed, 9 insertions(+)
+
+diff --git a/boost/smart_ptr/detail/atomic_count.hpp 
b/boost/smart_ptr/detail/atomic_count.hpp
+index 8aefd44..6e4f71a 100644
+--- a/boost/smart_ptr/detail/atomic_count.hpp
 b/boost/smart_ptr/detail/atomic_count.hpp
+@@ -73,6 +73,9 @@
+ #elif defined( BOOST_DISABLE_THREADS ) && !defined( BOOST_SP_ENABLE_THREADS ) 
&& !defined( BOOST_DISABLE_WIN32 )
+ # include 
+ 
++#elif !defined( BOOST_NO_CXX11_HDR_ATOMIC )
++# include 
++
+ #elif defined( __GNUC__ ) && ( defined( __i386__ ) || defined( __x86_64__ ) ) 
&& !defined( __PATHSCALE__ )
+ # include 
+ 
+diff --git a/boost/smart_ptr/detail/sp_counted_base.hpp 
b/boost/smart_ptr/detail/sp_counted_base.hpp
+index 0995ca8..83ede23 100644
+--- a/boost/smart_ptr/detail/sp_counted_base.hpp
 b/boost/smart_ptr/detail/sp_counted_base.hpp
+@@ -44,6 +44,9 @@
+ #elif defined( BOOST_SP_HAS_CLANG_C11_ATOMICS )
+ # include 
+ 
++#elif !defined( BOOST_NO_CXX11_HDR_ATOMIC )
++# include 
++
+ #elif defined( __SNC__ )
+ # include 
+ 
+diff --git a/boost/smart_ptr/detail/spinlock.hpp 
b/boost/smart_ptr/detail/spinlock.hpp
+index 19f93d7..0b618df 100644
+--- a/boost/smart_ptr/detail/spinlock.hpp
 b/boost/smart_ptr/detail/spinlock.hpp
+@@ -43,6 +43,9 @@
+ #elif defined( BOOST_SP_USE_PTHREADS )
+ #  include 
+ 
++#elif !defined( BOOST_NO_CXX11_HDR_ATOMIC )
++#  include 
++
+ #elif defined(__GNUC__) && defined( __arm__ ) && !defined( __thumb__ )
+ #  include 
+ 
+-- 
+2.9.3
+
diff --git a/meta/recipes-support/boost/boost_1.61.0.bb 
b/meta/recipes-support/boost/boost_1.61.0.bb
index 6926e84..33f209c 100644
--- a/meta/recipes-support/boost/boost_1.61.0.bb
+++ b/meta/recipes-support/boost/boost_1.61.0.bb
@@ -8,4 +8,5 @@ SRC_URI += "\
 file://0001-boost-asio-detail-socket_types.hpp-fix-poll.h-includ.patch \
 file://0002-boost-test-execution_monitor.hpp-fix-mips-soft-float.patch \
 file://0003-smart_ptr-mips-assembly-doesn-t-compile-in-mips16e-m.patch \
+file://0004-Use-atomic-by-default-when-BOOST_NO_CXX11_HDR_ATOMIC.patch \
 "
-- 
2.9.3

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [PATCH] boost: switch to using C++11 atomics when available

[Burton, Ross]

On 19 September 2016 at 10:38, André Draszik  wrote:

> +++ b/meta/recipes-support/boost/boost/0004-Use-atomic-by-
> default-when-BOOST_NO_CXX11_HDR_ATOMIC.patch
> @@ -0,0 +1,58 @@
> +From c234cc557f60729e071d6da59747c1a9289555c5 Mon Sep 17 00:00:00 2001
> +From: Peter Dimov 
> +Date: Sun, 28 Aug 2016 21:28:21 +0300
> +Subject: [PATCH 4/4] Use  by default when
> BOOST_NO_CXX11_HDR_ATOMIC is
> + not defined
> +
> +---
> +Upstream-Status: Backport https://github.com/boostorg/smart_ptr/commit/
> 20fedcff2ca3143503ec4e876d47745ab0ec7b0c
> + boost/smart_ptr/detail/atomic_count.hpp| 3 +++
> + boost/smart_ptr/detail/sp_counted_base.hpp | 3 +++
> + boost/smart_ptr/detail/spinlock.hpp| 3 +++
> + 3 files changed, 9 insertions(+)
>

This patch needs your s-o-b.

Ross
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

[OE-core] [PATCH 1/1] runqemu-gen-tapdevs: remove /etc/runqemu-nosudo when remove taps

[Robert Yang]

It creats /etc/runqemu-nosudo when creats taps, so should remove it when
remove taps.

Signed-off-by: Robert Yang 
---
 scripts/runqemu-gen-tapdevs | 46 +
 1 file changed, 26 insertions(+), 20 deletions(-)

diff --git a/scripts/runqemu-gen-tapdevs b/scripts/runqemu-gen-tapdevs
index 624deac..bfb60f4 100755
--- a/scripts/runqemu-gen-tapdevs
+++ b/scripts/runqemu-gen-tapdevs
@@ -69,32 +69,38 @@ if [ ! -x "$IFCONFIG" ]; then
exit 1
 fi
 
-# Ensure we start with a clean slate
-for tap in `$IFCONFIG link | grep tap | awk '{ print \$2 }' | sed s/://`; do
-   echo "Note: Destroying pre-existing tap interface $tap..."
-   $TUNCTL -d $tap
-done
-
-echo "Creating $COUNT tap devices for UID: $TUID GID: $GID..."
-for ((index=0; index < $COUNT; index++)); do
-   echo "Creating tap$index"
-   ifup=`$RUNQEMU_IFUP $TUID $GID $SYSROOT 2>&1`
-   if [ $? -ne 0 ]; then
-   echo "Error running tunctl: $ifup"
-   exit 1
-   fi
-done
+if [ $COUNT -ge 0 ]; then
+   # Ensure we start with a clean slate
+   for tap in `$IFCONFIG link | grep tap | awk '{ print \$2 }' | sed 
s/://`; do
+   echo "Note: Destroying pre-existing tap interface $tap..."
+   $TUNCTL -d $tap
+   done
+   rm -f /etc/runqemu-nosudo
+else
+   echo "Error: Incorrect count: $COUNT"
+   exit 1
+fi
 
 if [ $COUNT -gt 0 ]; then
+   echo "Creating $COUNT tap devices for UID: $TUID GID: $GID..."
+   for ((index=0; index < $COUNT; index++)); do
+   echo "Creating tap$index"
+   ifup=`$RUNQEMU_IFUP $TUID $GID $SYSROOT 2>&1`
+   if [ $? -ne 0 ]; then
+   echo "Error running tunctl: $ifup"
+   exit 1
+   fi
+   done
+
echo "Note: For systems running NetworkManager, it's recommended"
echo "Note: that the tap devices be set as unmanaged in the"
echo "Note: NetworkManager.conf file. Add the following lines to"
echo "Note: /etc/NetworkManager/NetworkManager.conf"
echo "[keyfile]"
echo "unmanaged-devices=interface-name:tap*"
-fi
 
-# The runqemu script will check for this file, and if it exists,
-# will use the existing bank of tap devices without creating
-# additional ones via sudo.
-touch /etc/runqemu-nosudo
+   # The runqemu script will check for this file, and if it exists,
+   # will use the existing bank of tap devices without creating
+   # additional ones via sudo.
+   touch /etc/runqemu-nosudo
+fi
-- 
2.9.0

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

[OE-core] [PATCH 0/1] runqemu-gen-tapdevs: remove /etc/runqemu-nosudo when remove taps

[Robert Yang]

The following changes since commit 5ac0604fdc7d5b783011c43d476210b427b5dae0:

  build-appliance-image: Create image in correct location (2016-09-19 08:58:04 
+0100)

are available in the git repository at:

  git://git.openembedded.org/openembedded-core-contrib rbt/rq-gen-tap
  
http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=rbt/rq-gen-tap

Robert Yang (1):
  runqemu-gen-tapdevs: remove /etc/runqemu-nosudo when remove taps

 scripts/runqemu-gen-tapdevs | 46 +
 1 file changed, 26 insertions(+), 20 deletions(-)

-- 
2.9.0

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [PATCH v2 0/1] To make yocto-spdx support spdx2.0 SPEC

[Lei, Maohui]

Hi all

  I have updated my patch for newest poky, can someone give me some comments? 
^_^

Best regards
Lei

> -Original Message-
> From: Lei, Maohui
> Sent: Monday, September 19, 2016 4:40 PM
> To: openembedded-core@lists.openembedded.org
> Cc: jsmoel...@linuxfoundation.org; Lei, Maohui
> Subject: [OE-core][PATCH v2 0/1] To make yocto-spdx support spdx2.0 SPEC
> 
> There are some problems in spdx module(spdx.bbclass).
> 1. The newest version of spdx specification is 2.0. But even spdx 1.1,
> yocto+SPDX can't support well.
> 2. It is complex to build a Yocto+SPDX environment.
> 3. Creating a spdx file spends too much time, especially for large software.
> 
> To improve spdx module ,I change the spdx create tool from fossology to 
> dosocs2.
> With this patch:
> 1. Also gets license informations by scanner from fossology.
> 1. Can support SPDX2.0 SPEC.
> 2. Because dosocs2 can work on directories, so there is no necessary to pack
> source code before do_spdx. It can save time for large software.
> 
> Lei Maohui (1):
>   Make yocto-spdx support spdx2.0 SPEC
> 
>  meta/classes/spdx.bbclass | 505 
> ++
>  meta/conf/licenses.conf   |  67 +-
>  2 files changed, 198 insertions(+), 374 deletions(-)
> 
> --
> 1.9.1



-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [PATCH V2 8/8] runqemu: improve finding of rootfs, kernel and dtb

[Joshua Lock]

On Sun, 2016-09-18 at 00:39 -0700, Robert Yang wrote:
> * Search rootfs in the following order:
>   - IMAGE_NAME*.FSTYPE
>   - IMAGE_LINK_NAME*.FSTYPE
> 
> * Search kernel in the following order:
>   - QB_DEFAULT_KERNEL
>   - KERNEL_IMAGETYPE
>   - KERNEL_IMAGETYPE*
> 
> * Search dtb in the following order:
>    - QB_DTB
>    - QB_DTB*
>    - *.dtb
> 
> * Fix DTB, it should only work with "-kernel" option.
> 
> [YOCTO #10265]
> 
> Signed-off-by: Robert Yang 
> ---
>  scripts/runqemu | 68 ++-
> --
>  1 file changed, 41 insertions(+), 27 deletions(-)
> 
> diff --git a/scripts/runqemu b/scripts/runqemu
> index 60e2093..1c4e69b 100755
> --- a/scripts/runqemu
> +++ b/scripts/runqemu
> @@ -157,6 +157,7 @@ class BaseConfig(object):
>  self.kernel = ''
>  self.kernel_cmdline = ''
>  self.kernel_cmdline_script = ''
> +self.dtb = ''
>  self.fstype = ''
>  self.kvm_enabled = False
>  self.vhost_enabled = False
> @@ -440,23 +441,23 @@ class BaseConfig(object):
>  if self.fstype == 'nfs':
>  return
>  
> +cmd_name = '%s/%s*.%s' % (self.get('DEPLOY_DIR_IMAGE'),
> self.get('IMAGE_NAME'), self.fstype)
> +cmd_link = '%s/%s*.%s' % (self.get('DEPLOY_DIR_IMAGE'),
> self.get('IMAGE_LINK_NAME'), self.fstype)
> +cmds = (cmd_name, cmd_link)
>  if self.rootfs and not os.path.exists(self.rootfs):
>  # Lazy rootfs
>  self.rootfs = "%s/%s-%s.%s" %
> (self.get('DEPLOY_DIR_IMAGE'),
>  self.rootfs, self.get('MACHINE'),
>  self.fstype)
>  elif not self.rootfs:
> -cmd = '%s/%s*.%s' % (self.get('DEPLOY_DIR_IMAGE'),
> self.get('IMAGE_NAME'), self.fstype)
> -all_files = glob.glob(cmd)
> -if all_files:
> -self.rootfs = all_files[0]
> -else:
> -cmd = '%s/%s*.%s' % (self.get('DEPLOY_DIR_IMAGE'),
> self.get('IMAGE_LINK_NAME'), self.fstype)
> +for cmd in cmds:
>  all_files = glob.glob(cmd)
>  if all_files:
>  self.rootfs = all_files[0]
> -else:
> -raise Exception("Failed to find rootfs: %s" %
> cmd)
> +break
> +
> +if not self.rootfs:
> +raise Exception("Failed to find rootfs: %s or %s" %
> cmds)
>  
>  if not os.path.exists(self.rootfs):
>  raise Exception("Can't find rootfs: %s" % self.rootfs)
> @@ -466,28 +467,37 @@ class BaseConfig(object):
>  # The vm image doesn't need a kernel
>  if self.fstype in self.vmtypes:
>  return
> -kernel = self.kernel
> +
>  deploy_dir_image = self.get('DEPLOY_DIR_IMAGE')
> -if not kernel:
> -kernel = "%s/%s" % (deploy_dir_image,
> self.get('QB_DEFAULT_KERNEL'))
> +if not self.kernel:
> +kernel_match_name = "%s/%s" % (deploy_dir_image,
> self.get('QB_DEFAULT_KERNEL'))
> +kernel_match_link = "%s/%s" % (deploy_dir_image,
> self.get('KERNEL_IMAGETYPE'))
> +kernel_startswith = "%s/%s*" % (deploy_dir_image,
> self.get('KERNEL_IMAGETYPE'))

There are qemuboot.conf files in the wild which won't contain
KERNEL_IMAGETYPE, at which point we're just looking for matches to
DEPLOY_DIR_IMAGE or DEPLOY_DIR_IMAGE/*

I think we need to add some extra handling so that we don't end up
setting kernel to either DEPLOY_DIR_IMAGE or its first child?

Joshua

> +cmds = (kernel_match_name, kernel_match_link,
> kernel_startswith)
> +for cmd in cmds:
> +all_files = glob.glob(cmd)
> +if all_files:
> +self.kernel = all_files[0]
> +break
> +if not self.kernel:
> +raise Exception('KERNEL not found: %s, %s or %s' %
> cmds)
>  
> -if os.path.exists(kernel):
> -self.kernel = kernel
> -else:
> -kernel = "%s/%s" % (deploy_dir_image,
> self.get('KERNEL_IMAGETYPE'))
> -if kernel != deploy_dir_image and
> os.path.exists(kernel):
> -self.kernel = kernel
> -else:
> -raise Exception("KERNEL %s not found" % kernel)
> +if not os.path.exists(self.kernel):
> +raise Exception("KERNEL %s not found" % self.kernel)
>  
>  dtb = self.get('QB_DTB')
>  if dtb:
> -dtb = "%s/%s" % (self.get('DEPLOY_DIR_IMAGE'), dtb)
> -if os.path.exists(dtb):
> -self.set('QB_DTB', '-dtb %s' % dtb)
> -else:
> -raise Exception("DTB %s not found" % dtb)
> -
> +cmd_match = "%s/%s" % (deploy_dir_image, dtb)
> +cmd_startswith = "%s/%s*" % (deploy_dir_image, dtb)
> +cmd_wild = "%s/*.dtb" % deploy_dir_image
> +cmds = (cmd_match, 

Re: [OE-core] [PATCH] package_manager.py: Restore FEED_DEPLOYDIR_BASE_URI functionality

[Burton, Ross]

On 2 September 2016 at 22:59, Reinhard Tartler 
wrote:

> According to the documentation, setting FEED_DEPLOYDIR_BASE_URI should
> be sufficient for setting up local feeds. This commit fixes the
> implementation to actually do that, even if BUILD_IMAGES_FROM_FEEDS is
> not set.
>
> Also fix some bugs in the old implementation:
>  - Fetch uncompressed Packages files, because
>'bitbake package-index' does not appear to create Packages.gz files.
>  - Add missing newline after the URI so that the options don't end up on
>the same line.
>  - Fix the check when local options are necessary.
>
> Signed-off-by: Reinhard Tartler 
>

Is this is case of duplicated functionality?  I've previously used
PACKAGE_FEED_URIS to get a working feed added to the target image, that
works for opkg and rpm too.

Ross
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

[OE-core] [PATCH v2 1/1] Make yocto-spdx support spdx2.0 SPEC

[Lei Maohui]

More:
- change spdx tool from fossology to dosocs2

Signed-off-by: Lei Maohui 
---
 meta/classes/spdx.bbclass | 505 ++
 meta/conf/licenses.conf   |  67 +-
 2 files changed, 198 insertions(+), 374 deletions(-)

diff --git a/meta/classes/spdx.bbclass b/meta/classes/spdx.bbclass
index 0c92765..27c0fa0 100644
--- a/meta/classes/spdx.bbclass
+++ b/meta/classes/spdx.bbclass
@@ -1,365 +1,252 @@
 # This class integrates real-time license scanning, generation of SPDX standard
 # output and verifiying license info during the building process.
-# It is a combination of efforts from the OE-Core, SPDX and Fossology projects.
+# It is a combination of efforts from the OE-Core, SPDX and DoSOCSv2 projects.
 #
-# For more information on FOSSology:
-#   http://www.fossology.org
-#
-# For more information on FOSSologySPDX commandline:
-#   https://github.com/spdx-tools/fossology-spdx/wiki/Fossology-SPDX-Web-API
+# For more information on DoSOCSv2:
+#   https://github.com/DoSOCSv2
 #
 # For more information on SPDX:
 #   http://www.spdx.org
 #
+# Note:
+# 1) Make sure DoSOCSv2 has beed installed in your host
+# 2) By default,spdx files will be output to the path which is defined 
as[SPDX_MANIFEST_DIR] 
+#in ./meta/conf/licenses.conf.
 
-# SPDX file will be output to the path which is defined as[SPDX_MANIFEST_DIR] 
-# in ./meta/conf/licenses.conf.
-
+SPDXOUTPUTDIR = "${WORKDIR}/spdx_output_dir"
 SPDXSSTATEDIR = "${WORKDIR}/spdx_sstate_dir"
 
 # If ${S} isn't actually the top-level source directory, set SPDX_S to point at
 # the real top-level directory.
+
 SPDX_S ?= "${S}"
 
 python do_spdx () {
 import os, sys
-import json, shutil
-
-info = {} 
-info['workdir'] = d.getVar('WORKDIR', True)
-info['sourcedir'] = d.getVar('SPDX_S', True)
-info['pn'] = d.getVar('PN', True)
-info['pv'] = d.getVar('PV', True)
-info['spdx_version'] = d.getVar('SPDX_VERSION', True)
-info['data_license'] = d.getVar('DATA_LICENSE', True)
-
-sstatedir = d.getVar('SPDXSSTATEDIR', True)
-sstatefile = os.path.join(sstatedir, info['pn'] + info['pv'] + ".spdx")
+import json
 
-manifest_dir = d.getVar('SPDX_MANIFEST_DIR', True)
-info['outfile'] = os.path.join(manifest_dir, info['pn'] + ".spdx" )
+## It's no necessary  to get spdx files for *-native
+if d.getVar('PN', True) == d.getVar('BPN', True) + "-native": 
+return None
 
-info['spdx_temp_dir'] = d.getVar('SPDX_TEMP_DIR', True)
-info['tar_file'] = os.path.join(info['workdir'], info['pn'] + ".tar.gz" )
+## gcc is too big to get spdx file.
+if 'gcc' in d.getVar('PN', True):
+return None   
 
-# Make sure important dirs exist
-try:
-bb.utils.mkdirhier(manifest_dir)
-bb.utils.mkdirhier(sstatedir)
-bb.utils.mkdirhier(info['spdx_temp_dir'])
-except OSError as e:
-bb.error("SPDX: Could not set up required directories: " + str(e))
-return
+info = {} 
+info['workdir'] = (d.getVar('WORKDIR', True) or "")
+info['pn'] = (d.getVar( 'PN', True ) or "")
+info['pv'] = (d.getVar( 'PV', True ) or "")
+info['package_download_location'] = (d.getVar( 'SRC_URI', True ) or "")
+if info['package_download_location'] != "":
+info['package_download_location'] = 
info['package_download_location'].split()[0]
+info['spdx_version'] = (d.getVar('SPDX_VERSION', True) or '')
+info['data_license'] = (d.getVar('DATA_LICENSE', True) or '')
+info['creator'] = {}
+info['creator']['Tool'] = (d.getVar('CREATOR_TOOL', True) or '')
+info['license_list_version'] = (d.getVar('LICENSELISTVERSION', True) or '')
+info['package_homepage'] = (d.getVar('HOMEPAGE', True) or "")
+info['package_summary'] = (d.getVar('SUMMARY', True) or "")
+info['package_summary'] = info['package_summary'].replace("\n","")
+info['package_summary'] = info['package_summary'].replace("'"," ")
+
+spdx_sstate_dir = (d.getVar('SPDXSSTATEDIR', True) or "")
+manifest_dir = (d.getVar('SPDX_MANIFEST_DIR', True) or "")
+info['outfile'] = os.path.join(manifest_dir, info['pn'] + "-" + info['pv'] 
+ ".spdx" )
+sstatefile = os.path.join(spdx_sstate_dir, 
+info['pn'] + "-" + info['pv'] + ".spdx" )
 
 ## get everything from cache.  use it to decide if 
-## something needs to be rerun 
-cur_ver_code = get_ver_code(info['sourcedir'])
+## something needs to be rerun
+if not os.path.exists( spdx_sstate_dir ):
+bb.utils.mkdirhier( spdx_sstate_dir )
+
+d.setVar('WORKDIR', d.getVar('SPDX_TEMP_DIR', True))
+info['sourcedir'] = (d.getVar('SPDX_S', True) or "")
+cur_ver_code = get_ver_code( info['sourcedir'] ).split()[0]
 cache_cur = False
-if os.path.exists(sstatefile):
+if os.path.exists( sstatefile ):
 ## cache for this package exists. read it in
-cached_spdx = get_cached_spdx(sstatefile)
-
-if 

[OE-core] [PATCH v2 0/1] To make yocto-spdx support spdx2.0 SPEC

[Lei Maohui]

There are some problems in spdx module(spdx.bbclass).
1. The newest version of spdxi specification is 2.0. But even spdx 1.1, 
yocto+SPDX can't support well.
2. It is complex to build a Yocto+SPDX environment.
3. Creating a spdx file spends too much time, especially for large software.

To improve spdx module ,I change the spdx create tool from fossology to dosocs2.
With this patch:
1. Also gets license informations by scanner from fossology.
1. Can support SPDX2.0 SPEC.
2. Because dosocs2 can work on directories, so there is no necessary to pack 
source code before do_spdx. It can save time for large software.

Lei Maohui (1):
  Make yocto-spdx support spdx2.0 SPEC

 meta/classes/spdx.bbclass | 505 ++
 meta/conf/licenses.conf   |  67 +-
 2 files changed, 198 insertions(+), 374 deletions(-)

-- 
1.9.1



-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [PATCH] openssh: fix potential signed overflow to enable compilation with -ftrapv

[Yu, Mingli]

ping

Thanks,

On 2016年08月26日 09:57, Yuanjie Huang wrote:

From: Yuanjie Huang 

Pointer arithmatic results in implementation defined signed integer
type, so that 's - src' in strlcpy and others may trigger signed overflow.
In case of compilation by gcc or clang with -ftrapv option, the overflow
would lead to program abort.

Upstream-status: Submitted [https://bugzilla.mindrot.org/show_bug.cgi?id=2608]

Signed-off-by: Yuanjie Huang 
---
  ...ial-signed-overflow-in-pointer-arithmatic.patch | 99 ++
  meta/recipes-connectivity/openssh/openssh_7.3p1.bb |  1 +
  2 files changed, 100 insertions(+)
  create mode 100644 
meta/recipes-connectivity/openssh/openssh/fix-potential-signed-overflow-in-pointer-arithmatic.patch

diff --git 
a/meta/recipes-connectivity/openssh/openssh/fix-potential-signed-overflow-in-pointer-arithmatic.patch
 
b/meta/recipes-connectivity/openssh/openssh/fix-potential-signed-overflow-in-pointer-arithmatic.patch
new file mode 100644
index 000..df64a14
--- /dev/null
+++ 
b/meta/recipes-connectivity/openssh/openssh/fix-potential-signed-overflow-in-pointer-arithmatic.patch
@@ -0,0 +1,99 @@
+From 3328e98bcbf2930cd7eea3e6c92ad5dcbdf4794f Mon Sep 17 00:00:00 2001
+From: Yuanjie Huang 
+Date: Wed, 24 Aug 2016 03:15:43 +
+Subject: [PATCH] Fix potential signed overflow in pointer arithmatic
+
+Pointer arithmatic results in implementation defined signed integer
+type, so that 's - src' in strlcpy and others may trigger signed overflow.
+In case of compilation by gcc or clang with -ftrapv option, the overflow
+would lead to program abort.
+
+Upstream-status: Submitted [http://bugzilla.mindrot.org/show_bug.cgi?id=2608]
+
+Signed-off-by: Yuanjie Huang 
+---
+ openbsd-compat/strlcat.c | 8 ++--
+ openbsd-compat/strlcpy.c | 8 ++--
+ openbsd-compat/strnlen.c | 8 ++--
+ 3 files changed, 18 insertions(+), 6 deletions(-)
+
+diff --git a/openbsd-compat/strlcat.c b/openbsd-compat/strlcat.c
+index bcc1b61..e758ebf 100644
+--- a/openbsd-compat/strlcat.c
 b/openbsd-compat/strlcat.c
+@@ -23,6 +23,7 @@
+
+ #include 
+ #include 
++#include 
+
+ /*
+  * Appends src to string dst of size siz (unlike strncat, siz is the
+@@ -55,8 +56,11 @@ strlcat(char *dst, const char *src, size_t siz)
+   s++;
+   }
+   *d = '\0';
+-
+-  return(dlen + (s - src));   /* count does not include NUL */
++/*
++   * Cast pointers to unsigned type before calculation, to avoid signed
++   * overflow when the string ends where the MSB has changed.
++   */
++  return (dlen + ((uintptr_t)s - (uintptr_t)src));/* count does 
not include NUL */
+ }
+
+ #endif /* !HAVE_STRLCAT */
+diff --git a/openbsd-compat/strlcpy.c b/openbsd-compat/strlcpy.c
+index b4b1b60..b06f374 100644
+--- a/openbsd-compat/strlcpy.c
 b/openbsd-compat/strlcpy.c
+@@ -23,6 +23,7 @@
+
+ #include 
+ #include 
++#include 
+
+ /*
+  * Copy src to string dst of size siz.  At most siz-1 characters
+@@ -51,8 +52,11 @@ strlcpy(char *dst, const char *src, size_t siz)
+   while (*s++)
+   ;
+   }
+-
+-  return(s - src - 1);/* count does not include NUL */
++/*
++   * Cast pointers to unsigned type before calculation, to avoid signed
++   * overflow when the string ends where the MSB has changed.
++   */
++  return ((uintptr_t)s - (uintptr_t)src - 1); /* count does not 
include NUL */
+ }
+
+ #endif /* !HAVE_STRLCPY */
+diff --git a/openbsd-compat/strnlen.c b/openbsd-compat/strnlen.c
+index 93d5155..9b8de5d 100644
+--- a/openbsd-compat/strnlen.c
 b/openbsd-compat/strnlen.c
+@@ -23,6 +23,7 @@
+ #include 
+
+ #include 
++#include 
+
+ size_t
+ strnlen(const char *str, size_t maxlen)
+@@ -31,7 +32,10 @@ strnlen(const char *str, size_t maxlen)
+
+   for (cp = str; maxlen != 0 && *cp != '\0'; cp++, maxlen--)
+   ;
+-
+-  return (size_t)(cp - str);
++/*
++   * Cast pointers to unsigned type before calculation, to avoid signed
++   * overflow when the string ends where the MSB has changed.
++   */
++  return (size_t)((uintptr_t)cp - (uintptr_t)str);
+ }
+ #endif
+--
+1.9.1
+
diff --git a/meta/recipes-connectivity/openssh/openssh_7.3p1.bb 
b/meta/recipes-connectivity/openssh/openssh_7.3p1.bb
index b319726..039b0ff 100644
--- a/meta/recipes-connectivity/openssh/openssh_7.3p1.bb
+++ b/meta/recipes-connectivity/openssh/openssh_7.3p1.bb
@@ -24,6 +24,7 @@ SRC_URI = 
"http://ftp.openbsd.org/pub/OpenBSD/OpenSSH/portable/openssh-${PV}.tar
 file://run-ptest \
 file://openssh-7.1p1-conditional-compile-des-in-cipher.patch \
 file://openssh-7.1p1-conditional-compile-des-in-pkcs11.patch \
+   file://fix-potential-signed-overflow-in-pointer-arithmatic.patch \
 "

  PAM_SRC_URI = "file://sshd"


--

[OE-core] [PATCH 1/1] runqemu: acquire_lock() should fail when failed to open the file

[Robert Yang]

The open(self.lock, 'w') may fail when the lock is created by other
users, return false for this case to let it try other devices.

Fixed:
runqemu - INFO - Running /sbin/ip link...
runqemu - INFO - Acquiring lockfile /tmp/qemu-tap-locks/tap0.lock...
Traceback (most recent call last):
  File "/buildarea/lyang1/poky/scripts/runqemu", line 972, in 
ret = main()
  File "/buildarea/lyang1/poky/scripts/runqemu", line 963, in main
config.setup_network()
  File "/buildarea/lyang1/poky/scripts/runqemu", line 810, in setup_network
self.setup_tap()
  File "/buildarea/lyang1/poky/scripts/runqemu", line 761, in setup_tap
if self.acquire_lock():
  File "/buildarea/lyang1/poky/scripts/runqemu", line 182, in acquire_lock
lock_descriptor = open(self.lock, 'w')
PermissionError: [Errno 13] Permission denied: '/tmp/qemu-tap-locks/tap0.lock'

Signed-off-by: Robert Yang 
---
 scripts/runqemu | 8 
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/scripts/runqemu b/scripts/runqemu
index b6bc0ba..3805685 100755
--- a/scripts/runqemu
+++ b/scripts/runqemu
@@ -168,14 +168,14 @@ class BaseConfig(object):
 
 def acquire_lock(self):
 logger.info("Acquiring lockfile %s..." % self.lock)
-lock_descriptor = open(self.lock, 'w')
 try:
-fcntl.flock(lock_descriptor, fcntl.LOCK_EX|fcntl.LOCK_NB)
+self.lock_descriptor = open(self.lock, 'w')
+fcntl.flock(self.lock_descriptor, fcntl.LOCK_EX|fcntl.LOCK_NB)
 except Exception as e:
 logger.info("Acquiring lockfile %s failed: %s" % (self.lock, e))
-lock_descriptor.close()
+if self.lock_descriptor:
+self.lock_descriptor.close()
 return False
-self.lock_descriptor = lock_descriptor
 return True
 
 def release_lock(self):
-- 
2.9.0

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

[OE-core] [PATCH 0/1] runqemu: acquire_lock() should fail when failed to open the file

[Robert Yang]

The following changes since commit d77fe838ab7631a19e90ff4226f0712e54aa4e22:

  scripts: add tool to scan for bashisms recipe shell scripts (2016-09-16 
15:19:31 +0100)

are available in the git repository at:

  git://git.openembedded.org/openembedded-core-contrib rbt/rq_lock
  
http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=rbt/rq_lock

Robert Yang (1):
  runqemu: acquire_lock() should fail when failed to open the file

 scripts/runqemu | 8 
 1 file changed, 4 insertions(+), 4 deletions(-)

-- 
2.9.0

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [PATCH] e2fsprogs: add packageconfig for -file-

[Ulf Magnusson]

On Mon, Sep 19, 2016 at 7:00 AM, Ulf Magnusson  wrote:
> On Mon, Sep 19, 2016 at 5:42 AM, Robert Yang  
> wrote:
>>
>>
>> On 09/19/2016 11:32 AM, Randy MacLeod wrote:
>>>
>>> On 2016-09-18 10:37 PM, Christopher Larson wrote:


 On Sun, Sep 18, 2016 at 7:32 PM, Randy MacLeod
 > wrote:

 On 2016-09-17 01:09 AM, Christopher Larson wrote:


 On Fri, Sep 16, 2016 at 6:37 PM, Randy MacLeod
 
 >> wrote:

 Without a packageconfig dependency for the file utility,
 there's
 a very rare compile faiure caused by a race where the magic.h
 header file is not found:

  ../../../git/lib/support/plausible.c:33:19: fatal error:
 magic.h:
 No such file or directory

 This file, plausible.c, is part of libsupport.a which is used
 by
 many binaries produced by the e2fsprogs package. plausible.c
 attempts
 to dynamically load libmagic.so if the e2fsprogs configure
 detects
 that magic was available. Adding the packageconfig will
 eliminate
 the build as well as the possible configure-time race
 condition.

 Signed-off-by: Randy MacLeod 
 >>
 ---
  meta/recipes-devtools/e2fsprogs/e2fsprogs_1.43.bb
 
  | 1 +
  1 file changed, 1 insertion(+)

 diff --git
 a/meta/recipes-devtools/e2fsprogs/e2fsprogs_1.43.bb
 
 
 b/meta/recipes-devtools/e2fsprogs/e2fsprogs_1.43.bb
 
 
 index f4855bc..1707cb9 100644
 --- a/meta/recipes-devtools/e2fsprogs/e2fsprogs_1.43.bb
 
 
 +++ b/meta/recipes-devtools/e2fsprogs/e2fsprogs_1.43.bb
 
 
 @@ -23,6 +23,7 @@ EXTRA_OECONF += "--libdir=${base_libdir}
 --sbindir=${base_sbindir} \
  EXTRA_OECONF_darwin = "--libdir=${base_libdir}
 --sbindir=${base_sbindir} --enable-bsd-shlibs"

  PACKAGECONFIG ??= ""
 +PACKAGECONFIG[file] = ',,file'


 This isn’t going to be good enough. You aren’t explicitly
 enabling/disabling the option, so it’ll still detect based on
 what’s in
 the sysroot, so recipe build order will result in
 non-deterministic
 behavior.


 Hi Christopher,

 Thanks for the response but I don't understand.
 I'm probably wrong so please explain.
 It seems that you're suggesting that I add:
  --with[out]-magic to e2fsprogs configure, and while
 I could do that, it does not seem to be needed.


 Short response:

   This change forces 'file' to be built before e2fsprogs if 'file'
   is present in the image or world build. Then e2fsprogs will
   detect magic.h,libmagic.so and  the race is eliminated.


 That’s only the case if ‘file’ is in PACKAGECONFIG, if not, it’ll still
 behave the way it did before, and change its deps based on build order.
 Our policy is to avoid floating deps period, regardless of
 PACKAGECONFIG. If a given packageconfig is not enabled, then explicitly
 disable the dependency, don’t detect and use it anyway.
>>>http://www.yoctoproject.org/docs/2.2/ref-manual/ref-manual.html#checking-for-missing-build-time-dependencies
>>>
>>> Ah right and now I see some uses where there would not be a
>>> package dependency required.
>>>
>>> I'll likely send a v2 adding just:
>>>PACKAGECONFIG ??= "file"
>>
>>
>> I'm afraid that this can't fix the floating deps, if file is a must
>> and can't be disabled, you can set:
>>
>> DEPENDS += "file"
>>
>> rather than use a PACKAGECONFIG.
>>
>>> since 'fuse' is in the meta-filesystems layer but
>>
>>
>> For fuse:
>> PACKAGECONFIG ??= ""
>> PACKAGECONFIG[fuse] = '--enable-fuse2fs,--disable-fuse2fs,fuse'
>>
>> It is disabled by default, but other layers use a 

[OE-core] [PATCH v2] ltp: 20160126 -> 20160510

[Wang Xin]

1) Upgrade ltp from 20160126 to 20160510.
2) Modify some patches, since the data has been changed.
0011-Rename-sigset-variable-to-sigset1.patch
0030-lib-Use-PTHREAD_MUTEX_RECURSIVE-in-place-of-PTHREAD_.patch
3) Delete some patches, since they are no use.
0001-ltp-Don-t-link-against-libfl.patch
0006-sendfile-Use-off64_t-instead-of-__off64_t.patch
0012-fsstress.c-Replace-__int64_t-with-int64_t.patch
0013-include-fcntl.h-for-getting-O_-definitions.patch
0014-hyperthreading-Include-sys-types.h-for-pid_t-definit.patch
0015-mincore01-Rename-PAGESIZE-to-pagesize.patch
0016-ustat-Change-header-from-ustat.h-to-sys-ustat.h.patch
0017-replace-sigval_t-with-union-sigval.patch
0019-tomoyo-Replace-canonicalize_file_name-with-realpath.patch
0032-regen.sh-Include-asm-unistd.h-explicitly.patch

Signed-off-by: Wang Xin 
---
 .../ltp/0001-ltp-Don-t-link-against-libfl.patch|  30 --
 ...sendfile-Use-off64_t-instead-of-__off64_t.patch |  31 --
 .../0011-Rename-sigset-variable-to-sigset1.patch   |  60 ++--
 ...fsstress.c-Replace-__int64_t-with-int64_t.patch | 351 -
 ...nclude-fcntl.h-for-getting-O_-definitions.patch |  67 
 ...ing-Include-sys-types.h-for-pid_t-definit.patch |  56 
 ...015-mincore01-Rename-PAGESIZE-to-pagesize.patch |  64 
 ...Change-header-from-ustat.h-to-sys-ustat.h.patch |  45 ---
 .../0017-replace-sigval_t-with-union-sigval.patch  |  88 --
 ...lace-canonicalize_file_name-with-realpath.patch |  32 --
 ...READ_MUTEX_RECURSIVE-in-place-of-PTHREAD_.patch |   6 +-
 ...-regen.sh-Include-asm-unistd.h-explicitly.patch |  30 --
 .../ltp/{ltp_20160126.bb => ltp_20160510.bb}   |  12 +-
 13 files changed, 34 insertions(+), 838 deletions(-)
 delete mode 100644 
meta/recipes-extended/ltp/ltp/0001-ltp-Don-t-link-against-libfl.patch
 delete mode 100644 
meta/recipes-extended/ltp/ltp/0006-sendfile-Use-off64_t-instead-of-__off64_t.patch
 delete mode 100644 
meta/recipes-extended/ltp/ltp/0012-fsstress.c-Replace-__int64_t-with-int64_t.patch
 delete mode 100644 
meta/recipes-extended/ltp/ltp/0013-include-fcntl.h-for-getting-O_-definitions.patch
 delete mode 100644 
meta/recipes-extended/ltp/ltp/0014-hyperthreading-Include-sys-types.h-for-pid_t-definit.patch
 delete mode 100644 
meta/recipes-extended/ltp/ltp/0015-mincore01-Rename-PAGESIZE-to-pagesize.patch
 delete mode 100644 
meta/recipes-extended/ltp/ltp/0016-ustat-Change-header-from-ustat.h-to-sys-ustat.h.patch
 delete mode 100644 
meta/recipes-extended/ltp/ltp/0017-replace-sigval_t-with-union-sigval.patch
 delete mode 100644 
meta/recipes-extended/ltp/ltp/0019-tomoyo-Replace-canonicalize_file_name-with-realpath.patch
 delete mode 100644 
meta/recipes-extended/ltp/ltp/0032-regen.sh-Include-asm-unistd.h-explicitly.patch
 rename meta/recipes-extended/ltp/{ltp_20160126.bb => ltp_20160510.bb} (88%)

diff --git 
a/meta/recipes-extended/ltp/ltp/0001-ltp-Don-t-link-against-libfl.patch 
b/meta/recipes-extended/ltp/ltp/0001-ltp-Don-t-link-against-libfl.patch
deleted file mode 100644
index 585b7cb..000
--- a/meta/recipes-extended/ltp/ltp/0001-ltp-Don-t-link-against-libfl.patch
+++ /dev/null
@@ -1,30 +0,0 @@
-From 14985fccf7428eaa0b45decc22bfd20fd780f621 Mon Sep 17 00:00:00 2001
-From: Chong Lu 
-Date: Tue, 11 Mar 2014 14:47:22 +0800
-Subject: [PATCH 01/32] ltp: Don't link against libfl
-
-We have already defined yywrap function in scan.l file. After this, we no 
longer need to
-link against libfl and so no longer get errors about undefined references to 
yylex.
-
-Signed-off-by: Chong Lu 
-Signed-off-by: Khem Raj 

- pan/Makefile | 2 +-
- 1 file changed, 1 insertion(+), 1 deletion(-)
-
-diff --git a/pan/Makefile b/pan/Makefile
-index 4cc6466..a4b575b 100644
 a/pan/Makefile
-+++ b/pan/Makefile
-@@ -31,7 +31,7 @@ CPPFLAGS += -Wno-error
- 
- CPPFLAGS  += -I$(abs_srcdir)
- 
--LDLIBS+= -lm $(LEXLIB)
-+LDLIBS+= -lm
- 
- LFLAGS+= -l
- 
--- 
-2.7.0
-
diff --git 
a/meta/recipes-extended/ltp/ltp/0006-sendfile-Use-off64_t-instead-of-__off64_t.patch
 
b/meta/recipes-extended/ltp/ltp/0006-sendfile-Use-off64_t-instead-of-__off64_t.patch
deleted file mode 100644
index 56a48ab..000
--- 
a/meta/recipes-extended/ltp/ltp/0006-sendfile-Use-off64_t-instead-of-__off64_t.patch
+++ /dev/null
@@ -1,31 +0,0 @@
-From fb8b895385a641d74f2186fe5f20a872209692ed Mon Sep 17 00:00:00 2001
-From: Khem Raj 
-Date: Thu, 7 Jan 2016 18:24:20 +
-Subject: [PATCH 06/32] sendfile: Use off64_t instead of __off64_t
-
-__off64_t is specific to glibc where as off64_t is widely available
-Add _GNU_SOURCE for off64_t defines from sys/types.h
-Fixes
-:0:7: error: unknown type name 'off64_t'
-sendfile02.c:97:18: note: in expansion of macro 'OFF_T'
-
-Signed-off-by: Khem Raj 

- 

[OE-core] [PATCH 1/1] qemuppc.conf: adjust kernel console

[Robert Yang]

Fixed kernel trace when booting:
[   12.825809] random: crng init done
[   13.918323] irq 36: nobody cared (try booting with the "irqpoll" option)
[   13.924821] CPU: 0 PID: 335 Comm: getty Not tainted 4.8.0-rc5-yocto-standard 
#1
[   13.930492] Call Trace:
[   13.936214] [cff73f20] [c00790f0] __report_bad_irq.isra.0+0x3c/0x128 
(unreliable)
[   13.941908] [cff73f40] [c0079518] note_interrupt+0x2b8/0x304
[   13.947265] [cff73f70] [c00766f4] handle_irq_event_percpu+0x5c/0x74
[   13.952503] [cff73f90] [c0076768] handle_irq_event+0x5c/0xdc
[   13.957667] [cff73fa0] [c007a29c] handle_fasteoi_irq+0xdc/0x234
[   13.962984] [cff73fc0] [c007592c] generic_handle_irq+0x3c/0x58
[   13.968288] [cff73fd0] [c0006c74] __do_irq+0x54/0x18c
[   13.973612] [cff73ff0] [c000f9c8] call_do_irq+0x24/0x3c
[   13.978742] [cf0cdb70] [c0006e40] do_IRQ+0x94/0x110
[   13.983992] [cf0cdba0] [c001215c] ret_from_except+0x0/0x14
[   13.989281] --- interrupt: 501 at pmz_set_termios+0x130/0x6d8
[   13.989281] LR = pmz_set_termios+0xf0/0x6d8
[   13.999353] [cf0cdc90] [c049f130] uart_change_speed.isra.2+0x60/0x168
[   14.004436] [cf0cdcb0] [c049fdbc] uart_startup.part.8+0xec/0x1e0
[   14.009625] [cf0cdce0] [c04a0ab4] uart_open+0x138/0x16c
[   14.014723] [cf0cdd00] [c047e510] tty_open+0x118/0x65c
[   14.019743] [cf0cdd60] [c01894c8] chrdev_open+0xdc/0x1e0
[   14.024616] [cf0cdd90] [c01807d0] do_dentry_open+0x23c/0x358
[   14.029418] [cf0cddc0] [c0194878] path_openat+0x58c/0x1084
[   14.034054] [cf0cde50] [c01965b4] do_filp_open+0xbc/0x10c
[   14.038539] [cf0cdf00] [c01822fc] do_sys_open+0x154/0x224
[   14.043105] [cf0cdf40] [c0011a44] ret_from_syscall+0x0/0x38
[   14.047828] --- interrupt: c01 at 0xfeef5a0
[   14.047828] LR = 0xfeef544
[   14.056543] handlers:
[   14.060980] [] pmz_interrupt
[   14.065468] Disabling IRQ #36

Signed-off-by: Robert Yang 
---
 meta/conf/machine/qemuppc.conf | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/conf/machine/qemuppc.conf b/meta/conf/machine/qemuppc.conf
index e4c8dac..e54c3dd 100644
--- a/meta/conf/machine/qemuppc.conf
+++ b/meta/conf/machine/qemuppc.conf
@@ -15,6 +15,6 @@ SERIAL_CONSOLES = "115200;ttyS0 115200;ttyS1"
 QB_SYSTEM_NAME = "qemu-system-ppc"
 QB_MACHINE = "-machine mac99"
 QB_CPU = "-cpu G4"
-QB_KERNEL_CMDLINE_APPEND = "console=ttyS0 console=tty"
+QB_KERNEL_CMDLINE_APPEND = "console=tty console=ttyS0"
 QB_OPT_APPEND = "-show-cursor -usb -usbdevice tablet"
 QB_TAP_OPT = "-netdev tap,id=net0,ifname=@TAP@,script=no,downscript=no -device 
virtio-net-pci,netdev=net0,mac=@MAC@"
-- 
2.9.0

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

[OE-core] [PATCH 0/1] qemuppc.conf: adjust kernel console

[Robert Yang]

The following changes since commit d77fe838ab7631a19e90ff4226f0712e54aa4e22:

  scripts: add tool to scan for bashisms recipe shell scripts (2016-09-16 
15:19:31 +0100)

are available in the git repository at:

  git://git.openembedded.org/openembedded-core-contrib rbt/qemuppc
  
http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=rbt/qemuppc

Robert Yang (1):
  qemuppc.conf: adjust kernel console

 meta/conf/machine/qemuppc.conf | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

-- 
2.9.0

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core