Re: [OE-core] [PATCH v2] elfutils: fix ptest failures

2019-05-28 Thread Yu, Mingli 



On 2019年05月28日 18:01, richard.pur...@linuxfoundation.org wrote:

On Tue, 2019-05-28 at 17:40 +0800, mingli...@windriver.com wrote:

From: Mingli Yu 

* Add missing -ptest package dependencies (needs
   ${PN}-dev)

* Add missing files which needed by ptest test
   to fix the ptest failures such as:
   | sh: ../src/elflint: No such file or directory
   | FAIL: asm-tst4

* Rework 0001-skip-the-test-when-gcc-not-deployed.patch
   to skip the tests which depend on gcc

* Don't split the -debug package for elfutils as
   most cases needs the binary to have .symtab.


Can you provide more details on what this last item means?


That means elfutils tests need the binary not stripped, so we need below 
logic:


INHIBIT_PACKAGE_STRIP = "1"
INHIBIT_PACKAGE_DEBUG_SPLIT = "1"



Do you mean elfutils is generally broken without the symtab section?
That seems unusual? Or do you mean the tests need it to be present?


Not sure whether elfutils is broken, but at least it is broken with 
regard to test part. If strip the binary, the test result:


Recipe   | Passed| Failed   | Skipped

elfutils | 184   | 15| 4


And all the failed case as below is because the binary is stripped.


FAIL: test-nlist
FAIL: run-strip-reloc.sh
FAIL: run-strip-strmerge.sh
FAIL: run-nm-self.sh
FAIL: run-readelf-self.sh
FAIL: run-varlocs-self.sh
FAIL: run-exprlocs-self.sh
FAIL: run-backtrace-native.sh
FAIL: run-backtrace-data.sh
FAIL: run-backtrace-native-core.sh
FAIL: run-deleted.sh
FAIL: run-dwarf-die-addr-die.sh
FAIL: run-get-units-invalid.sh
FAIL: run-get-units-split.sh
FAIL: run-unit-info.sh

For the test-nlist, the upstream also said the binary cannot be stripped 
to guarantee the test pass as 
https://sourceware.org/ml/elfutils-devel/2019-q2/msg00098.html and 
https://sourceware.org/ml/elfutils-devel/2019-q2/msg00103.html



So to fix this kind of below failures, we need to make the binary not 
stripped.


runtest /usr/lib64/elfutils/ptest/tests/..//src/strip
/usr/bin/eu-readelf: cannot get debug context descriptor: No DWARF 
information found
*** failure readelf -w debugfile1 
/usr/lib64/elfutils/ptest/tests/..//src/strip
/usr/bin/eu-readelf: cannot get debug context descriptor: No DWARF 
information found
*** failure readelf -w debugfile2 
/usr/lib64/elfutils/ptest/tests/..//src/strip

runtest /usr/lib64/elfutils/ptest/tests/..//src/strip.o
runtest strip-uncompressed.o
runtest strip-compressed.o
runtest testfile-debug-rel-ppc64.o
runtest testfile-debug-rel-ppc64-z.o
runtest testfile-debug-rel-ppc64-g.o
FAIL: run-strip-reloc.sh

/usr/lib64/elfutils/ptest/tests/..//tests/elfstrmerge: 
/usr/lib64/elfutils/ptest/tests/..//tests/elfstrmerge: couldn't get 
symtab data: no error

FAIL: run-strip-strmerge.sh

/usr/bin/eu-nm: /usr/lib64/elfutils/ptest/tests/..//src/nm: no symbols
FAIL: run-nm-self.sh



Not striping the binary at all is likely to cause a significant size
increase for elfutils and we want to avoid that, particularly if its
only to fix tests. We will probably have to find a different solution
(e.g. second copy with the symtab section in the ptest package, added
to PATH in the runner?)


During my test, if we strip the debug info to elfutils-dbg, first we 
need to make elfutils-ptest rdepends on elfutils-dbg and second the test 
still fails as above even the elfutils-dbg package deployed as below:

# pwd
/usr/lib64/elfutils/ptest
root@qemux86-64:/usr/lib64/elfutils/ptest# ls src/strip
src/strip
root@qemux86-64:/usr/lib64/elfutils/ptest# ls src/.debug/strip
src/.debug/strip
/.debug/strip64:/usr/lib64/elfutils/ptest# rpm -qf 
/usr/lib64/elfutils/ptest/src/.debug/strip

elfutils-dbg-0.176-r0.core2_64

Thanks,



Cheers,

Richard





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

Re: [OE-core] [PATCH 3/5] bootchart2: add initscripts-functions as rconflict

2019-05-28 Thread Changqing Li 


On 5/29/19 7:13 AM, Richard Purdie wrote:

On Tue, 2019-05-28 at 12:01 +0800, changqing...@windriver.com wrote:

From: Changqing Li 

bootchart2 rdepend on lsb, lsb rdepend on lsbinitscripts,
lsbinitscripts rconflict with initscripts-functions. so also add
rconflict for this one.

Signed-off-by: Changqing Li 
---
  meta/recipes-devtools/bootchart2/bootchart2_0.14.8.bb | 1 +
  1 file changed, 1 insertion(+)

diff --git a/meta/recipes-devtools/bootchart2/bootchart2_0.14.8.bb
b/meta/recipes-devtools/bootchart2/bootchart2_0.14.8.bb
index 396d0ec..36092e6 100644
--- a/meta/recipes-devtools/bootchart2/bootchart2_0.14.8.bb
+++ b/meta/recipes-devtools/bootchart2/bootchart2_0.14.8.bb
@@ -143,6 +143,7 @@ RDEPENDS_pybootchartgui = "python3-pycairo
python3-compression python3-image pyt
  RDEPENDS_${PN}_class-target += "${@bb.utils.contains('DISTRO_FEATURE
S', 'sysvinit', 'sysvinit-pidof', 'procps', d)}"
  RDEPENDS_${PN}_class-target += "lsb"
  DEPENDS_append_class-native = " python3-pycairo-native"
+RCONFLICTS_${PN}_class-target = "initscripts-functions"

If lsb and initscripts-functions have the conflict, why do we need this
in bootchart2 as well?

Cheers,

Richard


Yes,  this is wrong for indirect rconflict,  especially that, this maybe 
break someday when lsb changed.  Same as lsb/lsbtest in patch  4/5 and 5/5.



For patch 1/5, 2/5,  it is direct rconflict.  It will also report 
rconflict during do_rootfs when both are  installed  if only one package 
set rconflict.


but I think it is better to set rconflict for both packages, in this 
way,  when user parse the recipe to get the recipe info, it can get  
this rconflict


info.





--
BRs

Sandy(Li Changqing)

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

Re: [OE-core] [PATCH v3 1/2] local.conf.sample: make systemd as default init manager

2019-05-28 Thread Kang Kai 

On 2019/5/28 下午5:28, Paul Barker wrote:



On 27/05/2019 02:49, Kang Kai wrote:

On 2019/5/25 上午3:23, Peter Kjellerstedt wrote:

-Original Message-
From: Khem Raj 
Sent: den 23 maj 2019 22:59
To: Peter Kjellerstedt 
Cc: kai.k...@windriver.com; 
openembedded-core@lists.openembedded.org; 
richard.pur...@linuxfoundation.org
Subject: Re: [OE-core] [PATCH v3 1/2] local.conf.sample: make 
systemd as default init manager


On Thu, May 23, 2019 at 1:41 PM Peter Kjellerstedt 
 wrote:

-Original Message-
From: mailto:openembedded-core-boun...@lists.openembedded.org 

mailto:core-boun...@lists.openembedded.org> On Behalf Of
mailto:kai.k...@windriver.com
Sent: den 23 maj 2019 10:26
To: mailto:richard.pur...@linuxfoundation.org
Cc: mailto:openembedded-core@lists.openembedded.org
Subject: [OE-core] [PATCH v3 1/2] local.conf.sample: make systemd as
default init manager

From: Kai Kang 

Move configurations from local.conf.sample.extended to 
local.conf.sample

to make systemd as default init manager for poky.
If we're going to change the default init manager to be systemd, 
wouldn't
it be more appropriate to change the real default values in 
bitbake.conf

and http://packagegroup-core-boot.bb? And then include an example in
local.conf.sample.extended to show how to configure sysvinit as init
manager?

That would change it for Oe-core and other distributions as well which
is not the intention
Ok, then I'd say the change belongs in poky.conf. Doing this kind of 
changes

in local.conf.sample seems very wrong to me. Why? Because if I have an
existing build tree it will not be affected, but if I setup a new 
tree with
oe-init-build-env it will all of a sudden behave differently from 
the old
tree. In my mind, local.conf.sample should only be used for things 
the user
are likely to want to configure to adapt the build for his/her 
environment,

not to define the distribution (that's what poky.conf is for).



If put the settings to poky.conf, it is complicated to override the 
settings and hard for users to turn back to sysvinit when he/she wants.


If you want to make this override-able you could do something like 
this (forgive any mistakes or bad wrapping I'm just writing this in my 
email client without testing):


POKY_USE_SYSTEMD ?= "1"
DISTRO_FEATURES_append = "${@bb.utils.conditional("POKY_USE_SYSTEMD", 
"1", "systemd", "", d)}"

... etc ...

That would allow someone to set `POKY_USE_SYSTEMD = "0"` in their 
local.conf.


There may be more elegant ways to do this as well, but we the default 
can certainly be set in the distro config in a way that can be 
overridden in local.conf.


OK. I'll move them to poky.conf.

Thanks.

Kai




Thanks,



--
Kai Kang

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

Re: [OE-core] [PATCH] ca-certificates: Fix openssl runtime dependency

2019-05-28 Thread Richard Purdie 
On Tue, 2019-05-28 at 15:30 +0100, Andrei Gherzan wrote:
> Since yocto thud, and more specifically since poky switched to
> openssl 1.1 line, the openssl binary is provided by 'openssl-bin'.
> 
> Signed-off-by: Andrei Gherzan 
> ---
>  .../recipes-support/ca-certificates/ca-certificates_20190110.bb | 2
> +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/meta/recipes-support/ca-certificates/ca-
> certificates_20190110.bb b/meta/recipes-support/ca-certificates/ca-
> certificates_20190110.bb
> index 4c0425302f..bc69c55daa 100644
> --- a/meta/recipes-support/ca-certificates/ca-
> certificates_20190110.bb
> +++ b/meta/recipes-support/ca-certificates/ca-
> certificates_20190110.bb
> @@ -82,6 +82,6 @@ do_install_append_class-native () {
>  SYSROOT="${D}${base_prefix}" ${D}${sbindir}/update-ca-
> certificates
>  }
>  
> -RDEPENDS_${PN} += "openssl"
> +RDEPENDS_${PN} += "openssl-bin"

Doesn't work for ca-certificates-native:

https://autobuilder.yoctoproject.org/typhoon/#/builders/39/builds/638
[amongst many other failures]


Cheers,

Richard

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

Re: [OE-core] [PATCH 3/5] bootchart2: add initscripts-functions as rconflict

2019-05-28 Thread Richard Purdie 
On Tue, 2019-05-28 at 12:01 +0800, changqing...@windriver.com wrote:
> From: Changqing Li 
> 
> bootchart2 rdepend on lsb, lsb rdepend on lsbinitscripts,
> lsbinitscripts rconflict with initscripts-functions. so also add
> rconflict for this one.
> 
> Signed-off-by: Changqing Li 
> ---
>  meta/recipes-devtools/bootchart2/bootchart2_0.14.8.bb | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/meta/recipes-devtools/bootchart2/bootchart2_0.14.8.bb
> b/meta/recipes-devtools/bootchart2/bootchart2_0.14.8.bb
> index 396d0ec..36092e6 100644
> --- a/meta/recipes-devtools/bootchart2/bootchart2_0.14.8.bb
> +++ b/meta/recipes-devtools/bootchart2/bootchart2_0.14.8.bb
> @@ -143,6 +143,7 @@ RDEPENDS_pybootchartgui = "python3-pycairo
> python3-compression python3-image pyt
>  RDEPENDS_${PN}_class-target += "${@bb.utils.contains('DISTRO_FEATURE
> S', 'sysvinit', 'sysvinit-pidof', 'procps', d)}"
>  RDEPENDS_${PN}_class-target += "lsb"
>  DEPENDS_append_class-native = " python3-pycairo-native"
> +RCONFLICTS_${PN}_class-target = "initscripts-functions"

If lsb and initscripts-functions have the conflict, why do we need this
in bootchart2 as well?

Cheers,

Richard

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

Re: [OE-core] Should systemd be marked as incompatible with musl?

2019-05-28 Thread Andre McCurdy 
On Sat, May 25, 2019 at 12:25 AM Adrian Bunk  wrote:
>
> Is there development capacity to support musl?

It would be shame if there wasn't enough developer capacity to support
musl but in the end it comes down to what contributors to OE want to
work on.

There's a danger that the areas which OE contributors want to work on
don't exactly match what the overall Embedded Linux community wants
and we alienate potential users (for example we ditched uClibc support
not because no one wants to use uClibc any more but because no
contributors to OE wanted to spend time on uClibc) but overall the
model seems to work OK. I think right now we have enough interest in
musl to keep it alive.

> Supporting musl is a real pain across the board,
> with new issues all the time.

There are always new issues and bugs to be solved in OE as a
consequence of trying to keep all packages up to date. Whether the
issues arising from musl are a real pain or a fun new set of problems
to solve is mostly a matter of perspective.

> For really tiny systems you need both a tiny C library and a tiny init> 
> system, so not properly supporting the combination of both forces users
> to use alternative options instead of OE.
>
> Which minimizes the benefits gained by the pains of supporting musl.

A modern tiny init system would be nice to have, but it's not
essential or fair to say that musl is useless without one. Many
projects, especially tiny ones, manage fine with init scripts and
custom process management.

> > It's certainly a problem and we should try to fix it. It's not at all
> > uncommon that patches to fix build issues with musl, clang, a new
> > version of gcc, etc have a life cycle... a first pass just to fix the
> > build and then updates as issues are found or better solutions get
> > merged upstream. It's the normal process. You could argue that we are
> > sometimes too quick to merge the first pass hacks and too slow to
> > review and update them, but unfortunately that's just a consequence of
> > limited developer resources (and it's always more fun to try to get
> > the latest version of something working than review and cleanup old
> > patches...).
>
> If upstreaming is possible at all.
>
> With systemd on musl there is also the fundamental problem that
> neither of the upstreams is interested in compromising their
> software for the other.
>
> Not to blame either of them, there is simply a fundamental conflict
> between the systemd "use all functionality available" and the musl
> "be a tiny C library" and "follow standards and provide only some
> GNU extensions".
>
> One example:
>
> systemd uses qsort_r.
> musl upstream doesn't want to add qsort_r since it is nonstandard
> and BSD and glibc ended up providing incompatible versions.
> Most C libraries for Linux just follow glibc on that,
> but musl upstream is not doing this with a reasonable
> technical justification.
>
> For 0002-don-t-use-glibc-specific-qsort_r.patch (which looks as if it
> does cause data corruption) upstream is therefore in practice POSIX,
> unless you manage to convince systemd upstream to use something like
> gnulib to provide all the functionality they use that is not provided
> by musl. Which would also be a constant effort you have to makes since
> systemd upstream would not care about musl when making changes to
> their code.
>
> Even harder are cases like on_exit(3) (not currently hit by systemd but
> by other Linux-only software), which might not be implementable as an
> external function outside the C library.

Upstreamable solutions should always be preferred but if you can
accept that OE may need to carry patches which will never be
upstreamed (which isn't too much of a stretch given the age of some of
the patches we carry for gcc, busybox, etc) then none of the currently
known issues with systemd and musl seem like fundamental problems. A
few pragmatic patches applied by OE would go a long way to bridging
the conflicting goals of the two upstream projects. It's basically the
approach we've taken already - the question is just one of improving
the patches we already have (and maybe patching musl to add missing
functionality instead of only trying to patch systemd to not depend on
it).
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [PATCH] cmake: Use compiler launcher variable when ccache is enabled

2019-05-28 Thread Philippe Normand 
On 2019-05-28 20:22, Andre McCurdy wrote:
> On Tue, May 28, 2019 at 12:13 PM Philippe Normand  wrote:
>>
>> Setting the CMAKE_C{,XX}_COMPILER_LAUNCHER variables is the recomended way to
>> deal with ccache in CMake. It allows build scripts to optionally opt-out of
>> CMake, which is especially useful when the pre-processed GCC output is 
>> required.
> 
> Opt out of CMake? Or ccache ?
> 

The latter. Sorry about this typo, I'll send an amended patch :)

Philippe

>>
>> Signed-off-by: Philippe Normand 
>> ---
>>  meta/classes/cmake.bbclass | 11 +--
>>  1 file changed, 9 insertions(+), 2 deletions(-)
>>
>> diff --git a/meta/classes/cmake.bbclass b/meta/classes/cmake.bbclass
>> index d3f0d70847..a5cffedbc6 100644
>> --- a/meta/classes/cmake.bbclass
>> +++ b/meta/classes/cmake.bbclass
>> @@ -26,14 +26,16 @@ python() {
>>  if not d.getVar('OECMAKE_C_COMPILER'):
>>  cc_list = d.getVar('CC').split()
>>  if cc_list[0] == 'ccache':
>> -d.setVar('OECMAKE_C_COMPILER', '%s %s' % (cc_list[0], 
>> cc_list[1]))
>> +d.setVar('OECMAKE_C_COMPILER_LAUNCHER', cc_list[0])
>> +d.setVar('OECMAKE_C_COMPILER', cc_list[1])
>>  else:
>>  d.setVar('OECMAKE_C_COMPILER', cc_list[0])
>>
>>  if not d.getVar('OECMAKE_CXX_COMPILER'):
>>  cxx_list = d.getVar('CXX').split()
>>  if cxx_list[0] == 'ccache':
>> -d.setVar('OECMAKE_CXX_COMPILER', '%s %s' % (cxx_list[0], 
>> cxx_list[1]))
>> +d.setVar('OECMAKE_CXX_COMPILER_LAUNCHER', cxx_list[0])
>> +d.setVar('OECMAKE_CXX_COMPILER', cxx_list[1])
>>  else:
>>  d.setVar('OECMAKE_CXX_COMPILER', cxx_list[0])
>>  }
>> @@ -49,6 +51,9 @@ OECMAKE_CXX_LINK_FLAGS ?= "${HOST_CC_ARCH} 
>> ${TOOLCHAIN_OPTIONS} ${CXXFLAGS} ${LD
>>  CXXFLAGS += "${HOST_CC_ARCH} ${TOOLCHAIN_OPTIONS}"
>>  CFLAGS += "${HOST_CC_ARCH} ${TOOLCHAIN_OPTIONS}"
>>
>> +OECMAKE_C_COMPILER_LAUNCHER ?= ""
>> +OECMAKE_CXX_COMPILER_LAUNCHER ?= ""
>> +
>>  OECMAKE_RPATH ?= ""
>>  OECMAKE_PERLNATIVE_DIR ??= ""
>>  OECMAKE_EXTRA_ROOT_PATH ?= ""
>> @@ -86,6 +91,8 @@ set( CMAKE_SYSTEM_NAME `echo ${TARGET_OS} | sed -e 
>> 's/^./\u&/' -e 's/^\(Linux\).
>>  set( CMAKE_SYSTEM_PROCESSOR 
>> ${@map_target_arch_to_uname_arch(d.getVar('TARGET_ARCH'))} )
>>  set( CMAKE_C_COMPILER ${OECMAKE_C_COMPILER} )
>>  set( CMAKE_CXX_COMPILER ${OECMAKE_CXX_COMPILER} )
>> +set( CMAKE_C_COMPILER_LAUNCHER ${OECMAKE_C_COMPILER_LAUNCHER} )
>> +set( CMAKE_CXX_COMPILER_LAUNCHER ${OECMAKE_CXX_COMPILER_LAUNCHER} )
>>  set( CMAKE_ASM_COMPILER ${OECMAKE_C_COMPILER} )
>>  set( CMAKE_AR ${OECMAKE_AR} CACHE FILEPATH "Archiver" )
>>  set( CMAKE_C_FLAGS "${OECMAKE_C_FLAGS}" CACHE STRING "CFLAGS" )
>> --
>> 2.20.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] cmake: Use compiler launcher variable when ccache is enabled

2019-05-28 Thread Andre McCurdy 
On Tue, May 28, 2019 at 12:13 PM Philippe Normand  wrote:
>
> Setting the CMAKE_C{,XX}_COMPILER_LAUNCHER variables is the recomended way to
> deal with ccache in CMake. It allows build scripts to optionally opt-out of
> CMake, which is especially useful when the pre-processed GCC output is 
> required.

Opt out of CMake? Or ccache ?

>
> Signed-off-by: Philippe Normand 
> ---
>  meta/classes/cmake.bbclass | 11 +--
>  1 file changed, 9 insertions(+), 2 deletions(-)
>
> diff --git a/meta/classes/cmake.bbclass b/meta/classes/cmake.bbclass
> index d3f0d70847..a5cffedbc6 100644
> --- a/meta/classes/cmake.bbclass
> +++ b/meta/classes/cmake.bbclass
> @@ -26,14 +26,16 @@ python() {
>  if not d.getVar('OECMAKE_C_COMPILER'):
>  cc_list = d.getVar('CC').split()
>  if cc_list[0] == 'ccache':
> -d.setVar('OECMAKE_C_COMPILER', '%s %s' % (cc_list[0], 
> cc_list[1]))
> +d.setVar('OECMAKE_C_COMPILER_LAUNCHER', cc_list[0])
> +d.setVar('OECMAKE_C_COMPILER', cc_list[1])
>  else:
>  d.setVar('OECMAKE_C_COMPILER', cc_list[0])
>
>  if not d.getVar('OECMAKE_CXX_COMPILER'):
>  cxx_list = d.getVar('CXX').split()
>  if cxx_list[0] == 'ccache':
> -d.setVar('OECMAKE_CXX_COMPILER', '%s %s' % (cxx_list[0], 
> cxx_list[1]))
> +d.setVar('OECMAKE_CXX_COMPILER_LAUNCHER', cxx_list[0])
> +d.setVar('OECMAKE_CXX_COMPILER', cxx_list[1])
>  else:
>  d.setVar('OECMAKE_CXX_COMPILER', cxx_list[0])
>  }
> @@ -49,6 +51,9 @@ OECMAKE_CXX_LINK_FLAGS ?= "${HOST_CC_ARCH} 
> ${TOOLCHAIN_OPTIONS} ${CXXFLAGS} ${LD
>  CXXFLAGS += "${HOST_CC_ARCH} ${TOOLCHAIN_OPTIONS}"
>  CFLAGS += "${HOST_CC_ARCH} ${TOOLCHAIN_OPTIONS}"
>
> +OECMAKE_C_COMPILER_LAUNCHER ?= ""
> +OECMAKE_CXX_COMPILER_LAUNCHER ?= ""
> +
>  OECMAKE_RPATH ?= ""
>  OECMAKE_PERLNATIVE_DIR ??= ""
>  OECMAKE_EXTRA_ROOT_PATH ?= ""
> @@ -86,6 +91,8 @@ set( CMAKE_SYSTEM_NAME `echo ${TARGET_OS} | sed -e 
> 's/^./\u&/' -e 's/^\(Linux\).
>  set( CMAKE_SYSTEM_PROCESSOR 
> ${@map_target_arch_to_uname_arch(d.getVar('TARGET_ARCH'))} )
>  set( CMAKE_C_COMPILER ${OECMAKE_C_COMPILER} )
>  set( CMAKE_CXX_COMPILER ${OECMAKE_CXX_COMPILER} )
> +set( CMAKE_C_COMPILER_LAUNCHER ${OECMAKE_C_COMPILER_LAUNCHER} )
> +set( CMAKE_CXX_COMPILER_LAUNCHER ${OECMAKE_CXX_COMPILER_LAUNCHER} )
>  set( CMAKE_ASM_COMPILER ${OECMAKE_C_COMPILER} )
>  set( CMAKE_AR ${OECMAKE_AR} CACHE FILEPATH "Archiver" )
>  set( CMAKE_C_FLAGS "${OECMAKE_C_FLAGS}" CACHE STRING "CFLAGS" )
> --
> 2.20.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

[OE-core] [PATCH] cmake: Use compiler launcher variable when ccache is enabled

2019-05-28 Thread Philippe Normand 
Setting the CMAKE_C{,XX}_COMPILER_LAUNCHER variables is the recomended way to
deal with ccache in CMake. It allows build scripts to optionally opt-out of
CMake, which is especially useful when the pre-processed GCC output is required.

Signed-off-by: Philippe Normand 
---
 meta/classes/cmake.bbclass | 11 +--
 1 file changed, 9 insertions(+), 2 deletions(-)

diff --git a/meta/classes/cmake.bbclass b/meta/classes/cmake.bbclass
index d3f0d70847..a5cffedbc6 100644
--- a/meta/classes/cmake.bbclass
+++ b/meta/classes/cmake.bbclass
@@ -26,14 +26,16 @@ python() {
 if not d.getVar('OECMAKE_C_COMPILER'):
 cc_list = d.getVar('CC').split()
 if cc_list[0] == 'ccache':
-d.setVar('OECMAKE_C_COMPILER', '%s %s' % (cc_list[0], cc_list[1]))
+d.setVar('OECMAKE_C_COMPILER_LAUNCHER', cc_list[0])
+d.setVar('OECMAKE_C_COMPILER', cc_list[1])
 else:
 d.setVar('OECMAKE_C_COMPILER', cc_list[0])
 
 if not d.getVar('OECMAKE_CXX_COMPILER'):
 cxx_list = d.getVar('CXX').split()
 if cxx_list[0] == 'ccache':
-d.setVar('OECMAKE_CXX_COMPILER', '%s %s' % (cxx_list[0], 
cxx_list[1]))
+d.setVar('OECMAKE_CXX_COMPILER_LAUNCHER', cxx_list[0])
+d.setVar('OECMAKE_CXX_COMPILER', cxx_list[1])
 else:
 d.setVar('OECMAKE_CXX_COMPILER', cxx_list[0])
 }
@@ -49,6 +51,9 @@ OECMAKE_CXX_LINK_FLAGS ?= "${HOST_CC_ARCH} 
${TOOLCHAIN_OPTIONS} ${CXXFLAGS} ${LD
 CXXFLAGS += "${HOST_CC_ARCH} ${TOOLCHAIN_OPTIONS}"
 CFLAGS += "${HOST_CC_ARCH} ${TOOLCHAIN_OPTIONS}"
 
+OECMAKE_C_COMPILER_LAUNCHER ?= ""
+OECMAKE_CXX_COMPILER_LAUNCHER ?= ""
+
 OECMAKE_RPATH ?= ""
 OECMAKE_PERLNATIVE_DIR ??= ""
 OECMAKE_EXTRA_ROOT_PATH ?= ""
@@ -86,6 +91,8 @@ set( CMAKE_SYSTEM_NAME `echo ${TARGET_OS} | sed -e 
's/^./\u&/' -e 's/^\(Linux\).
 set( CMAKE_SYSTEM_PROCESSOR 
${@map_target_arch_to_uname_arch(d.getVar('TARGET_ARCH'))} )
 set( CMAKE_C_COMPILER ${OECMAKE_C_COMPILER} )
 set( CMAKE_CXX_COMPILER ${OECMAKE_CXX_COMPILER} )
+set( CMAKE_C_COMPILER_LAUNCHER ${OECMAKE_C_COMPILER_LAUNCHER} )
+set( CMAKE_CXX_COMPILER_LAUNCHER ${OECMAKE_CXX_COMPILER_LAUNCHER} )
 set( CMAKE_ASM_COMPILER ${OECMAKE_C_COMPILER} )
 set( CMAKE_AR ${OECMAKE_AR} CACHE FILEPATH "Archiver" )
 set( CMAKE_C_FLAGS "${OECMAKE_C_FLAGS}" CACHE STRING "CFLAGS" )
-- 
2.20.1


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

[OE-core] [PATCH] p11-kit: update to 0.23.16.1

2019-05-28 Thread Oleksandr Kravchuk 
Signed-off-by: Oleksandr Kravchuk 
---
 .../p11-kit/{p11-kit_0.23.15.bb => p11-kit_0.23.16.1.bb}| 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
 rename meta/recipes-support/p11-kit/{p11-kit_0.23.15.bb => 
p11-kit_0.23.16.1.bb} (97%)

diff --git a/meta/recipes-support/p11-kit/p11-kit_0.23.15.bb 
b/meta/recipes-support/p11-kit/p11-kit_0.23.16.1.bb
similarity index 97%
rename from meta/recipes-support/p11-kit/p11-kit_0.23.15.bb
rename to meta/recipes-support/p11-kit/p11-kit_0.23.16.1.bb
index 59e675b542..54455da1bb 100644
--- a/meta/recipes-support/p11-kit/p11-kit_0.23.15.bb
+++ b/meta/recipes-support/p11-kit/p11-kit_0.23.16.1.bb
@@ -9,7 +9,7 @@ DEPENDS = "libtasn1 libffi"
 SRC_URI = "git://github.com/p11-glue/p11-kit \

file://0001-LINGUAS-drop-the-languages-for-which-upstream-does-n.patch \
"
-SRCREV = "1ba80c67c492f25581ed97c8c31ffb5f20636d06"
+SRCREV = "c689917b393379d288b868f70b2f7b7f6aafe430"
 S = "${WORKDIR}/git"
 
 AUTOTOOLS_AUXDIR = "${S}/build/litter"
-- 
2.17.1

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

[OE-core] [PATCH] file: update to 5.37

2019-05-28 Thread Oleksandr Kravchuk 
Signed-off-by: Oleksandr Kravchuk 
---
 meta/recipes-devtools/file/{file_5.36.bb => file_5.37.bb} | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
 rename meta/recipes-devtools/file/{file_5.36.bb => file_5.37.bb} (96%)

diff --git a/meta/recipes-devtools/file/file_5.36.bb 
b/meta/recipes-devtools/file/file_5.37.bb
similarity index 96%
rename from meta/recipes-devtools/file/file_5.36.bb
rename to meta/recipes-devtools/file/file_5.37.bb
index 9a0e5bd220..803aa9a271 100644
--- a/meta/recipes-devtools/file/file_5.36.bb
+++ b/meta/recipes-devtools/file/file_5.37.bb
@@ -16,7 +16,7 @@ UPSTREAM_CHECK_GITTAGREGEX = "FILE(?P(?!6_23).+)"
 
 SRC_URI = "git://github.com/file/file.git"
 
-SRCREV = "f3a4b9ada3ca99e62c62b9aa78eee4935a8094fe"
+SRCREV = "a0d5b0e4e9f97d74a9911e95cedd579852e25398"
 S = "${WORKDIR}/git"
 
 inherit autotools update-alternatives
-- 
2.17.1

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

[OE-core] Yocto Project Status WW22'19

2019-05-28 Thread Richard Purdie 
Current Dev Position: YP 2.8 M1Next Deadline: YP 2.8 Milestone 1 Cutoff
June 9th, 2019
SWAT Team Rotation: * SWAT lead is currently: Chen
 * SWAT team rotation: Chen -> Armin on May. 31, 2019
 * SWAT team rotation: Armin -> Anuj on June 7, 2019
 * https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team

Next Team Meetings: * Bug Triage meeting Thursday May 30th at 7:30am
PDT (https://zoom.us/j/454367603)
 * Monthly Project Meeting Tuesday June 4th at 8am PDT (
https://zoom.us/j/990892712) 

Key Status/Updates: * Stephen is going to be unavailable for several
weeks, please refer any queries to Richard
 * Mailing lists are moving to groups.io instead of our current mailman
setup. For various reasons the move was delayed and will take place on
3rd June. This shouldn’t impact users directly, more details will be
sent to the mailing lists in due course.
 * We have a new “newcomer” bug category which are bugs suited to
someone new to the project. These can be seen here: 
https://wiki.yoctoproject.org/wiki/Bug_Triage#Newcomer_Bugs
 * Adrian Bunk has done some much appreciated work in removing patches
which are no longer needed or appropriate.
 * Various upgrades and ptest dependency fixes merged. Work is still
needed on ptest dependencies, particularly on perl modules.
 * Gcc 9 is now the default, thanks to Khem for working around the
remaining bug in OE-Core.


Planned Releases for YP 2.8: * M1 Cutoff June 9th
 * M1 Release June 21st
 * M2 Cutoff 14th July
 * M2 Release 26th July
 * M3 Cutoff (Feature Freeze) 25th Aug
 * M3 Release 6th Sept
 * M4 Cutoff 30th Sept
 * 2.8 (M4) Final Release 25th Oct

Planned upcoming dot releases: * YP 2.6.3 (Thud) is in planning
 * YP 2.7.1 (Warrior) is in planning

Tracking Metrics: * WDD 2524 (last week 2559) (
https://wiki.yoctoproject.org/charts/combo.html)
 * Poky Patch Metrics  
* Total patches found: 1525 (last week 1531)
* Patches in the Pending State: 649 (43%) [last week 655 (43%)]

Key Status Links for YP:
https://wiki.yoctoproject.org/wiki/Yocto_Project_v2.8_Statushttps://wiki.yoctoproject.org/wiki/Yocto_2.8_Schedulehttps://wiki.yoctoproject.org/wiki/Yocto_2.8_Features
The Status reports are now stored on the wiki at: 
https://wiki.yoctoproject.org/wiki/Weekly_Status
[If anyone has suggestions for other information you’d like to see on
this weekly status update, let us know!]




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

[OE-core] [PATCH 2/2] Bash: Allow new-exp ptest to pass when run as root.

2019-05-28 Thread Sakib Sajal 
The ptest was failing as it was expecting non-root user.
Ptests are only run as root.

Signed-off-by: Sakib Sajal 
Signed-off-by: Randy Macleod 
---
 ...llow-ptest-new-exp-to-be-run-as-root.patch | 45 +++
 meta/recipes-extended/bash/bash_5.0.bb|  1 +
 2 files changed, 46 insertions(+)
 create mode 100644 
meta/recipes-extended/bash/bash/0001-Bash-Allow-ptest-new-exp-to-be-run-as-root.patch

diff --git 
a/meta/recipes-extended/bash/bash/0001-Bash-Allow-ptest-new-exp-to-be-run-as-root.patch
 
b/meta/recipes-extended/bash/bash/0001-Bash-Allow-ptest-new-exp-to-be-run-as-root.patch
new file mode 100644
index 00..bc0154692e
--- /dev/null
+++ 
b/meta/recipes-extended/bash/bash/0001-Bash-Allow-ptest-new-exp-to-be-run-as-root.patch
@@ -0,0 +1,45 @@
+From d360a22e7a0b75f1e081f6d7cbf4d55745ecce6b Mon Sep 17 00:00:00 2001
+From: Sakib Sajal 
+Date: Mon, 27 May 2019 17:57:04 -0400
+Subject: [PATCH] Bash: Allow ptest, new-exp, to be run as root
+
+Upstream-Status: inappropriate [embedded specific]
+
+The ptest was failing as it was expecting non-root user.
+Ptests are only run as root.
+
+Signed-off-by: Sakib Sajal 
+Signed-off-by: Randy Macleod 
+---
+ tests/new-exp.right | 2 +-
+ tests/new-exp.tests | 4 
+ 2 files changed, 1 insertion(+), 5 deletions(-)
+
+diff --git a/tests/new-exp.right b/tests/new-exp.right
+index c0f78fbb..9a42ec81 100644
+--- a/tests/new-exp.right
 b/tests/new-exp.right
+@@ -624,7 +624,7 @@ c Sub = 0 2 4 8
+ <'ab cd'> 
+ <'4'> <'ab cd'> 
+ <> 
+-argv[1] = 
++argv[1] = 
+ < 
+ >
+ <' \t\n'>
+diff --git a/tests/new-exp.tests b/tests/new-exp.tests
+index 557d6b44..31e15468 100644
+--- a/tests/new-exp.tests
 b/tests/new-exp.tests
+@@ -1,7 +1,3 @@
+-if (( $UID == 0 )); then
+-  echo "new-exp.tests: the test suite should not be run as root" >&2
+-fi
+-
+ # must do this because posix mode causes process substitution to be disabled
+ # and flagged as a syntax error, which causes the shell to exit
+ set +o posix
+-- 
+2.20.1
+
diff --git a/meta/recipes-extended/bash/bash_5.0.bb 
b/meta/recipes-extended/bash/bash_5.0.bb
index e60e5304a5..953f3cb0e1 100644
--- a/meta/recipes-extended/bash/bash_5.0.bb
+++ b/meta/recipes-extended/bash/bash_5.0.bb
@@ -19,6 +19,7 @@ SRC_URI = "${GNU_MIRROR}/bash/${BP}.tar.gz;name=tarball \
file://fix-run-coproc-run-heredoc-run-execscript-run-test-f.patch \
file://run-ptest \
file://fix-run-builtins.patch \
+  file://0001-Bash-Allow-ptest-new-exp-to-be-run-as-root.patch \
"
 
 SRC_URI[tarball.md5sum] = "2b44b47b905be16f45709648f671820b"
-- 
2.20.1

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

[OE-core] [PATCH 1/2] bash: add iso8859-1 gconv RDEPENDS needed by bash-ptest.

2019-05-28 Thread Sakib Sajal 
One of the ptests failed for internationalization.
>From the failed ptest log:
   run-intl
   fr_FR.ISO8859-1: Error Encoding U+0080 to  [ "$'\200'" != "\\u0080" ]
   (125 similar errors related to same encoding)
The test was unable to convert iso8859-1 encoding to perform comparison.

Signed-off-by: Sakib Sajal 
Signed-off-by: Randy Macleod 
---
 meta/recipes-extended/bash/bash.inc | 11 +--
 1 file changed, 9 insertions(+), 2 deletions(-)

diff --git a/meta/recipes-extended/bash/bash.inc 
b/meta/recipes-extended/bash/bash.inc
index 4b3692c613..1e4dc55d01 100644
--- a/meta/recipes-extended/bash/bash.inc
+++ b/meta/recipes-extended/bash/bash.inc
@@ -26,8 +26,15 @@ RDEPENDS_${PN}_class-nativesdk = ""
 RDEPENDS_${PN}-ptest += "make coreutils perl"
 
 DEPENDS_append_libc-glibc = " virtual/libc-locale"
-RDEPENDS_${PN}-ptest_append_libc-glibc = " locale-base-en-us locale-base-fr-fr 
locale-base-fr-fr.iso-8859-1 locale-base-de-de locale-base-zh-hk.big5-hkscs 
glibc-utils"
-
+RDEPENDS_${PN}-ptest_append_libc-glibc = " \
+   glibc-gconv-iso8859-1 \
+   glibc-utils \
+   locale-base-de-de \
+   locale-base-en-us \
+   locale-base-fr-fr \
+   locale-base-fr-fr.iso-8859-1 \
+   locale-base-zh-hk.big5-hkscs \
+   "
 USERADD_PACKAGES = "${PN}-ptest"
 USERADD_PARAM_${PN}-ptest = "--create-home --user-group test"
 
-- 
2.20.1

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

[OE-core] [PATCH] ca-certificates: Fix openssl runtime dependency

2019-05-28 Thread Andrei Gherzan 
Since yocto thud, and more specifically since poky switched to
openssl 1.1 line, the openssl binary is provided by 'openssl-bin'.

Signed-off-by: Andrei Gherzan 
---
 .../recipes-support/ca-certificates/ca-certificates_20190110.bb | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/recipes-support/ca-certificates/ca-certificates_20190110.bb 
b/meta/recipes-support/ca-certificates/ca-certificates_20190110.bb
index 4c0425302f..bc69c55daa 100644
--- a/meta/recipes-support/ca-certificates/ca-certificates_20190110.bb
+++ b/meta/recipes-support/ca-certificates/ca-certificates_20190110.bb
@@ -82,6 +82,6 @@ do_install_append_class-native () {
 SYSROOT="${D}${base_prefix}" ${D}${sbindir}/update-ca-certificates
 }
 
-RDEPENDS_${PN} += "openssl"
+RDEPENDS_${PN} += "openssl-bin"
 
 BBCLASSEXTEND = "native nativesdk"
-- 
2.17.1

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

Re: [OE-core] [PATCH v2] elfutils: fix ptest failures

2019-05-28 Thread richard . purdie 
On Tue, 2019-05-28 at 17:40 +0800, mingli...@windriver.com wrote:
> From: Mingli Yu 
> 
> * Add missing -ptest package dependencies (needs
>   ${PN}-dev)
> 
> * Add missing files which needed by ptest test
>   to fix the ptest failures such as:
>   | sh: ../src/elflint: No such file or directory
>   | FAIL: asm-tst4
> 
> * Rework 0001-skip-the-test-when-gcc-not-deployed.patch
>   to skip the tests which depend on gcc
> 
> * Don't split the -debug package for elfutils as
>   most cases needs the binary to have .symtab.

Can you provide more details on what this last item means?

Do you mean elfutils is generally broken without the symtab section?
That seems unusual? Or do you mean the tests need it to be present?

Not striping the binary at all is likely to cause a significant size
increase for elfutils and we want to avoid that, particularly if its
only to fix tests. We will probably have to find a different solution
(e.g. second copy with the symtab section in the ptest package, added
to PATH in the runner?)

Cheers,

Richard



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

[OE-core] [PATCH v2] elfutils: fix ptest failures

2019-05-28 Thread mingli.yu 
From: Mingli Yu 

* Add missing -ptest package dependencies (needs
  ${PN}-dev)

* Add missing files which needed by ptest test
  to fix the ptest failures such as:
  | sh: ../src/elflint: No such file or directory
  | FAIL: asm-tst4

* Rework 0001-skip-the-test-when-gcc-not-deployed.patch
  to skip the tests which depend on gcc

* Don't split the -debug package for elfutils as
  most cases needs the binary to have .symtab.

Before:

Recipe   | Passed| Failed   | Skipped

elfutils | 176   | 23   | 4


After:

Recipe   | Passed| Failed   | Skipped

elfutils | 199   | 0   | 4


Signed-off-by: Mingli Yu 
---
 meta/recipes-devtools/elfutils/elfutils_0.176.bb   | 15 -
 .../0001-skip-the-test-when-gcc-not-deployed.patch | 38 +++---
 2 files changed, 47 insertions(+), 6 deletions(-)

diff --git a/meta/recipes-devtools/elfutils/elfutils_0.176.bb 
b/meta/recipes-devtools/elfutils/elfutils_0.176.bb
index 157551e..c845a29 100644
--- a/meta/recipes-devtools/elfutils/elfutils_0.176.bb
+++ b/meta/recipes-devtools/elfutils/elfutils_0.176.bb
@@ -44,7 +44,7 @@ inherit autotools gettext ptest
 
 EXTRA_OECONF = "--program-prefix=eu- --without-lzma"
 EXTRA_OECONF_append_class-native = " --without-bzlib"
-RDEPENDS_${PN}-ptest = "libasm libelf bash make coreutils ${PN}-binutils ${PN}"
+RDEPENDS_${PN}-ptest = "libasm libelf bash make coreutils ${PN}-binutils ${PN} 
${PN}-dev"
 
 EXTRA_OECONF_append_class-target += "--disable-tests-rpath"
 
@@ -61,6 +61,16 @@ do_compile_ptest() {
 
 do_install_ptest() {
if [ ${PTEST_ENABLED} = "1" ]; then
+   # copy the files which needed by the cases
+   TEST_FILES="strip strip.o addr2line elfcmp objdump readelf 
size.o nm.o nm elflint"
+   install -d -m 755   ${D}${PTEST_PATH}/src
+   install -d -m 755   ${D}${PTEST_PATH}/libelf
+   install -d -m 755   ${D}${PTEST_PATH}/libdw
+   for test_file in ${TEST_FILES}; do
+   cp -r ${B}/src/${test_file} ${D}${PTEST_PATH}/src
+   done
+   ln -s ${libdir}/libelf.so ${D}${PTEST_PATH}/libelf/libelf.so
+   ln -s ${libdir}/libdw.so ${D}${PTEST_PATH}/libdw/libdw.so
cp -r ${S}/tests/   ${D}${PTEST_PATH}
cp -r ${B}/tests/*  ${D}${PTEST_PATH}/tests
cp -r ${B}/config.h ${D}${PTEST_PATH}
@@ -109,3 +119,6 @@ FILES_libdw  = "${libdir}/libdw-${PV}.so 
${libdir}/libdw.so.* ${libdir}/elfutils
 
 # The package contains symlinks that trip up insane
 INSANE_SKIP_${MLPREFIX}libdw = "dev-so"
+INSANE_SKIP_${PN}-ptest += "dev-deps"
+INHIBIT_PACKAGE_STRIP = "1"
+INHIBIT_PACKAGE_DEBUG_SPLIT = "1"
diff --git 
a/meta/recipes-devtools/elfutils/files/0001-skip-the-test-when-gcc-not-deployed.patch
 
b/meta/recipes-devtools/elfutils/files/0001-skip-the-test-when-gcc-not-deployed.patch
index 67ca0e4..de8c05f 100644
--- 
a/meta/recipes-devtools/elfutils/files/0001-skip-the-test-when-gcc-not-deployed.patch
+++ 
b/meta/recipes-devtools/elfutils/files/0001-skip-the-test-when-gcc-not-deployed.patch
@@ -1,19 +1,47 @@
-From 61939d2e552e7645ecd671fa01cf1c7a72caa82a Mon Sep 17 00:00:00 2001
+From e82a055f85e398cb03a4eaf5faf351a3a1f19344 Mon Sep 17 00:00:00 2001
 From: Mingli Yu 
-Date: Fri, 12 Apr 2019 16:29:58 +0800
-Subject: [PATCH] skip the test when gcc not deployed
+Date: Tue, 21 May 2019 15:20:34 +0800
+Subject: [PATCH v2] skip the test when gcc not deployed
 
 Skip the tests which depend on gcc when
 gcc not deployed.
 
-Upstream-Status: Inappropriate [oe specific]
+Upstream-Status: 
Submitted[https://sourceware.org/ml/elfutils-devel/2019-q2/msg00091.html]
 
 Signed-off-by: Mingli Yu 
 ---
+ tests/run-disasm-x86-64.sh | 2 ++
+ tests/run-disasm-x86.sh| 2 ++
  tests/run-strip-g.sh   | 2 ++
  tests/run-strip-nothing.sh | 2 ++
- 2 files changed, 4 insertions(+)
+ 4 files changed, 8 insertions(+)
 
+diff --git a/tests/run-disasm-x86-64.sh b/tests/run-disasm-x86-64.sh
+index a6be62b..c3ef238 100755
+--- a/tests/run-disasm-x86-64.sh
 b/tests/run-disasm-x86-64.sh
+@@ -22,6 +22,8 @@ case "`uname -m`" in
+   x86_64)
+ tempfiles testfile45.o
+ testfiles testfile45.S testfile45.expect
++# skip the case if no gcc deployed
++which gcc || exit 77
+ gcc -m64 -c -o testfile45.o testfile45.S
+ testrun_compare ${abs_top_builddir}/src/objdump -d testfile45.o < 
testfile45.expect
+ ;;
+diff --git a/tests/run-disasm-x86.sh b/tests/run-disasm-x86.sh
+index 28a3df7..544fc28 100755
+--- a/tests/run-disasm-x86.sh
 b/tests/run-disasm-x86.sh
+@@ -22,6 +22,8 @@ case

Re: [OE-core] [PATCH] base.bbclass: add named SRCREVs to the sstate hash

2019-05-28 Thread Michael.Ho 
Hi Martin,

Ah okay, sorry, I misread and thought you meant it was a known issue and it is 
expected to set vardeps manually.

Thanks for the +1.

Kind regards,
Michael Ho

--
BMW Car IT GmbH
Michael Ho
Spezialist Entwicklung – Build and Release Engineering
Lise-Meitner-Straße 14
89081 Ulm

Tel.: ­+49-731-37804-071
Mobil: +49-152-54980-471
Fax: +49-731-37804-001
Mail: michael...@bmw-carit.de
Web: http://www.bmw-carit.de
-
BMW Car IT GmbH
Geschäftsführer: Kai-Uwe Balszuweit und Christian Salzmann
Sitz und Registergericht: München HRB 134810
-


From: Martin Jansa 
Date: Monday, 27 May 2019 at 6:56 pm
To: "Ho Michael, JC-3UL" 
Cc: Chris Larson , Patches and discussions about the oe-core 
layer 
Subject: Re: [OE-core] [PATCH] base.bbclass: add named SRCREVs to the sstate 
hash

Hi Michael,

sorry I wasn't clear in the reply, I meant that it's easy to work around this 
issue, but it's error prone.

Your patch does it automatically and I don't see any cases where we wouldn't 
want all the SRCREVs included in do_fetch signature, so I like your patch.

+1 from me.

Cheers,

On Mon, May 27, 2019 at 6:34 PM mailto:michael...@bmw.de>> 
wrote:
Hi Martin,

It seems a little tricky though to need to know about the sstate hashing in 
order to use named
source revisions and it could be a bit confusing that using a normal SRCREV 
doesn’t require any
extra effort but named SRCREVs require additional lines of metadata. As you can 
see in the
commit message of my patches, the vulkan-demos recipe in poky also has this 
issue so it might
be quite easy to forget.

Thanks for the feedback. If the patch idea isn’t good, let me know if you think 
I should instead
post a patch for the documentation to try to more explicitly note the need for 
the additional vardeps
statements when using named SRCREVs.

Thanks.

Kind regards,
Michael

--
BMW Car IT GmbH
Michael Ho
Spezialist Entwicklung – Build and Release Engineering
Lise-Meitner-Straße 14
89081 Ulm

Tel.: ­+49-731-37804-071
Mobil: +49-152-54980-471
Fax: +49-731-37804-001
Mail: michael...@bmw-carit.de
Web: http://www.bmw-carit.de
-
BMW Car IT GmbH
Geschäftsführer: Kai-Uwe Balszuweit und Christian Salzmann
Sitz und Registergericht: München HRB 134810
-


From: Martin Jansa mailto:martin.ja...@gmail.com>>
Date: Monday, 27 May 2019 at 5:44 pm
To: "Ho Michael, JC-3UL" mailto:michael...@bmw.de>>
Cc: Chris Larson mailto:kerg...@gmail.com>>, Patches and 
discussions about the oe-core layer 
mailto:openembedded-core@lists.openembedded.org>>
Subject: Re: [OE-core] [PATCH] base.bbclass: add named SRCREVs to the sstate 
hash

In those recipes which don't include SRCPV in PV (for whatever reason) we 
usually add them explicitly with:
do_fetch[vardeps] += "SRCREV_common"
it's not ideal as people sometimes forget about this. Good practice is to add 
this next to the SRCREV_FORMAT (if you set one, to clearly show which revs are 
and aren't included).

On Mon, May 27, 2019 at 5:37 PM mailto:michael...@bmw.de>> 
wrote:
Hi Christopher,

Thank you for the feedback. Since SRCPV is not always enforced (correct me if 
I’m wrong), it seems easy to trip over this bug when just following the 
documentation on multiple named source uri’s (also if you purposely don’t want 
to include the secondary source revisions in the package version). I’ll give it 
another shot to make it more efficient. If it’s not expected to be an 
encounterable bug case you can ignore the patch.

Thanks.

Kind regards,
Michael

--
BMW Car IT GmbH
Michael Ho
Spezialist Entwicklung – Build and Release Engineering
Lise-Meitner-Straße 14
89081 Ulm

Tel.: ­+49-731-37804-071
Mobil: +49-152-54980-471
Fax: +49-731-37804-001
Mail: michael...@bmw-carit.de
Web: http://www.bmw-carit.de
-
BMW Car IT GmbH
Geschäftsführer: Kai-Uwe Balszuweit und Christian Salzmann
Sitz und Registergericht: München HRB 134810
-


From: Christopher Larson mailto:kerg...@gmail.com>>
Date: Wednesday, 8 May 2019 at 5:17 pm
To: "Ho Michael, JC-3UL" mailto:michael...@bmw.de>>
Cc: Patches and discussions about the oe-core layer 
mailto:openembedded-core@lists.openembedded.org>>
Subject: Re: [OE-core] [PATCH] base.bbclass: add named SRCREVs to the sstate 
hash

Does SRCPV not already cover this in the majority of cases? SRCREV_FORMAT 
controls how the multiple revs end up in PV, and the change to PV results in 
rebuilding anyway. And iterating over d.keys() is inefficient, *if*

Re: [OE-core] [PATCH v3 1/2] local.conf.sample: make systemd as default init manager

2019-05-28 Thread Paul Barker 



On 27/05/2019 02:49, Kang Kai wrote:

On 2019/5/25 上午3:23, Peter Kjellerstedt wrote:

-Original Message-
From: Khem Raj 
Sent: den 23 maj 2019 22:59
To: Peter Kjellerstedt 
Cc: kai.k...@windriver.com; openembedded-core@lists.openembedded.org; 
richard.pur...@linuxfoundation.org
Subject: Re: [OE-core] [PATCH v3 1/2] local.conf.sample: make systemd 
as default init manager


On Thu, May 23, 2019 at 1:41 PM Peter Kjellerstedt 
 wrote:

-Original Message-
From: mailto:openembedded-core-boun...@lists.openembedded.org 

mailto:core-boun...@lists.openembedded.org> On Behalf Of
mailto:kai.k...@windriver.com
Sent: den 23 maj 2019 10:26
To: mailto:richard.pur...@linuxfoundation.org
Cc: mailto:openembedded-core@lists.openembedded.org
Subject: [OE-core] [PATCH v3 1/2] local.conf.sample: make systemd as
default init manager

From: Kai Kang 

Move configurations from local.conf.sample.extended to 
local.conf.sample

to make systemd as default init manager for poky.
If we're going to change the default init manager to be systemd, 
wouldn't

it be more appropriate to change the real default values in bitbake.conf
and http://packagegroup-core-boot.bb? And then include an example in
local.conf.sample.extended to show how to configure sysvinit as init
manager?

That would change it for Oe-core and other distributions as well which
is not the intention
Ok, then I'd say the change belongs in poky.conf. Doing this kind of 
changes

in local.conf.sample seems very wrong to me. Why? Because if I have an
existing build tree it will not be affected, but if I setup a new tree 
with

oe-init-build-env it will all of a sudden behave differently from the old
tree. In my mind, local.conf.sample should only be used for things the 
user
are likely to want to configure to adapt the build for his/her 
environment,

not to define the distribution (that's what poky.conf is for).



If put the settings to poky.conf, it is complicated to override the 
settings and hard for users to turn back to sysvinit when he/she wants.


If you want to make this override-able you could do something like this 
(forgive any mistakes or bad wrapping I'm just writing this in my email 
client without testing):


POKY_USE_SYSTEMD ?= "1"
DISTRO_FEATURES_append = "${@bb.utils.conditional("POKY_USE_SYSTEMD", 
"1", "systemd", "", d)}"

... etc ...

That would allow someone to set `POKY_USE_SYSTEMD = "0"` in their 
local.conf.


There may be more elegant ways to do this as well, but we the default 
can certainly be set in the distro config in a way that can be 
overridden in local.conf.


Thanks,

--
Paul Barker
Managing Director & Principal Engineer
Beta Five Ltd
--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [PATCH] elfutils: fix ptest failures

2019-05-28 Thread Yu, Mingli 



On 2019年05月26日 04:16, richard.pur...@linuxfoundation.org wrote:

On Wed, 2019-05-22 at 17:11 +0800, mingli...@windriver.com wrote:

From: Mingli Yu 

* Add missing -ptest package dependencies (needs
   ${PN}-dbg)

* Add missing files which needed by ptest test
   to fix below failures:
   | ./run-ar.sh: line 23: cd:
/usr/lib64/elfutils/ptest/tests/..//src: No such file or directory
   | FAIL: run-ar.sh

   | sh: ../src/elflint: No such file or directory
   | FAIL: asm-tst4

* Rework 0001-skip-the-test-when-gcc-not-deployed.patch
   to skip the tests which depend on gcc

Before:

Recipe   | Passed| Failed   | Skipped

elfutils | 176   | 23   | 4


After:

Recipe   | Passed| Failed   | Skipped

elfutils | 184   | 15   | 4




Unfortunately if I add this to the build we see failures due to core-
image-sato-sdk-ptest becomming too large for generix86-64 as the image
exceeds the 4GB limit its FSTYPE allows.

I tried reducing the amount of free space in the image but then the
strace and until-linux ptests fail:

https://autobuilder.yocto.io/pub/non-release/20190524-8/testresults/testresult-report.txt

We do plan to change the hddimg format and use wic to avoid the 4GB
limit sometime in 2.8 but those patches aren't ready yet. I'm therefore
not quite sure what to do here. Is there any way we can save space in
the images so we could merge this?


It will be better if any space can be saved.



Wth regard to the src/ directory, I did wonder if there needed to be a
patch to one of the other scripts to use installed files (similar to
how I fixed some of these last time)?


Have checked your patch about new target oecheck. Anyway, I have 
narrowed down a little to copy only the needed files to src/ dir.


And I also send out v2 patch then which updated to fix all the tests.

Thanks,



Cheers,

Richard



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

[OE-core] [PATCH] packagegroup-core-full-cmdline: Make nfs-utils/rpcbind optional

2019-05-28 Thread Oliver Stäbler 
Consider DISTRO_FEATURES for nfs-utils and rpcbind.
This is to prevent the following warning while booting:
NFS daemon support not enabled in kernel

Signed-off-by: Oliver Stäbler 
---
 .../packagegroups/packagegroup-core-full-cmdline.bb| 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git 
a/meta/recipes-extended/packagegroups/packagegroup-core-full-cmdline.bb 
b/meta/recipes-extended/packagegroups/packagegroup-core-full-cmdline.bb
index ec67f8d123..d38f545e06 100644
--- a/meta/recipes-extended/packagegroups/packagegroup-core-full-cmdline.bb
+++ b/meta/recipes-extended/packagegroups/packagegroup-core-full-cmdline.bb
@@ -135,6 +135,5 @@ RDEPENDS_packagegroup-core-full-cmdline-sys-services = "\
 at \
 cronie \
 logrotate \
-nfs-utils \
-rpcbind \
+${@bb.utils.contains('DISTRO_FEATURES', 'nfs', 'nfs-utils rpcbind', '', 
d)} \
 "
-- 
2.21.0

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

[OE-core] [PATCH V2] gcc: reduce the variables in symtab

2019-05-28 Thread Zhixiong Chi 
Backport the patch from upstream:
https://github.com/gcc-mirror/gcc.git [commit beb921e]
https://gcc.gnu.org/viewcvs/gcc?view=revision=269925

Add the premark_used_variables function, meanwhile do not mark
not premarked external variables in prune_unused_types_walk.

Signed-off-by: Zhixiong Chi 
---
 meta/recipes-devtools/gcc/gcc-8.3.inc |  1 +
 .../gcc/gcc-8.3/0042-PR-debug-86964.patch | 94 +++
 2 files changed, 95 insertions(+)
 create mode 100644 meta/recipes-devtools/gcc/gcc-8.3/0042-PR-debug-86964.patch

diff --git a/meta/recipes-devtools/gcc/gcc-8.3.inc 
b/meta/recipes-devtools/gcc/gcc-8.3.inc
index fe9c7c3602..a6b772aadd 100644
--- a/meta/recipes-devtools/gcc/gcc-8.3.inc
+++ b/meta/recipes-devtools/gcc/gcc-8.3.inc
@@ -72,6 +72,7 @@ SRC_URI = "\
file://0039-riscv-Disable-multilib-for-OE.patch \
file://0040-powerpc-powerpc64-Add-support-for-musl-ldso.patch \

file://0041-Add-a-recursion-limit-to-libiberty-s-demangling-code.patch \
+   file://0042-PR-debug-86964.patch \
 "
 SRC_URI[md5sum] = "65b210b4bfe7e060051f799e0f994896"
 SRC_URI[sha256sum] = 
"64baadfe6cc0f4947a84cb12d7f0dfaf45bb58b7e92461639596c21e02d97d2c"
diff --git a/meta/recipes-devtools/gcc/gcc-8.3/0042-PR-debug-86964.patch 
b/meta/recipes-devtools/gcc/gcc-8.3/0042-PR-debug-86964.patch
new file mode 100644
index 00..d9b5d39b77
--- /dev/null
+++ b/meta/recipes-devtools/gcc/gcc-8.3/0042-PR-debug-86964.patch
@@ -0,0 +1,94 @@
+From beb921e1106b5bcbb0c6e2be84b241327e2ffc51 Mon Sep 17 00:00:00 2001
+From: law 
+Date: Mon, 25 Mar 2019 21:19:09 +
+Subject: [PATCH]   PR debug/86964  * dwarf2out.c
+ (premark_used_variables): New function.   (prune_unused_types_walk): Do
+ not mark not premarked external   variables.  (prune_unused_types):
+ Call premark_used_variables.
+
+   * gcc.dg/debug/dwarf2/pr86964.c: New testcase.
+
+git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@269925 
138bc75d-0d04-0410-961f-82ee72b054a4
+
+Upstream-Status: Backport
+Signed-off-by: Zhixiong Chi 
+---
+ gcc/ChangeLog   |  8 ++
+ gcc/dwarf2out.c | 32 +
+ 2 files changed, 40 insertions(+)
+
+diff --git a/gcc/ChangeLog b/gcc/ChangeLog
+index 2075480ca2b..cdce539ac6f 100644
+--- a/gcc/ChangeLog
 b/gcc/ChangeLog
+@@ -1,3 +1,11 @@
++2019-03-25  Johan Karlsson 
++
++  PR debug/86964
++  * dwarf2out.c (premark_used_variables): New function.
++  (prune_unused_types_walk): Do not mark not premarked external
++  variables.
++  (prune_unused_types): Call premark_used_variables.
++
+ 2019-02-22  Release Manager
+ 
+   * GCC 8.3.0 released.
+diff --git a/gcc/dwarf2out.c b/gcc/dwarf2out.c
+index ae8bdee9981..b9a624e1ac7 100644
+--- a/gcc/dwarf2out.c
 b/gcc/dwarf2out.c
+@@ -22658,6 +22658,21 @@ premark_types_used_by_global_vars (void)
+   ->traverse (NULL);
+ }
+ 
++/* Mark all variables used by the symtab as perennial.  */
++
++static void
++premark_used_variables (void)
++{
++  /* Mark DIEs in the symtab as used.  */
++  varpool_node *var;
++  FOR_EACH_VARIABLE (var)
++{
++  dw_die_ref die = lookup_decl_die (var->decl);
++  if (die)
++  die->die_perennial_p = 1;
++}
++}
++
+ /* Generate a DW_TAG_call_site DIE in function DECL under SUBR_DIE
+for CA_LOC call arg loc node.  */
+ 
+@@ -29264,6 +29279,19 @@ prune_unused_types_walk (dw_die_ref die)
+ 
+   return;
+ 
++case DW_TAG_variable:
++  if (flag_debug_only_used_symbols)
++  {
++if (die->die_perennial_p)
++  break;
++
++/* premark_used_variables marks external variables --- don't mark
++   them here.  */
++if (get_AT (die, DW_AT_external))
++  return;
++  }
++  /* FALLTHROUGH */
++
+ default:
+   /* Mark everything else.  */
+   break;
+@@ -29390,6 +29418,10 @@ prune_unused_types (void)
+   /* Mark types that are used in global variables.  */
+   premark_types_used_by_global_vars ();
+ 
++  /* Mark variables used in the symtab.  */
++  if (flag_debug_only_used_symbols)
++premark_used_variables ();
++
+   /* Set the mark on nodes that are actually used.  */
+   prune_unused_types_walk (comp_unit_die ());
+   for (node = limbo_die_list; node; node = node->next)
+-- 
+2.21.0
-- 
2.21.0

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

Re: [OE-core] [PATCH] gcc: reduce the variables in symtab

2019-05-28 Thread Zhixiong Chi 

Please ignore it. I will send V2.

Thanks.


On 2019年05月28日 15:56, Zhixiong Chi wrote:

Signed-off-by: Zhixiong Chi 
---
  meta/recipes-devtools/gcc/gcc-8.3.inc |  1 +
  .../gcc/gcc-8.3/0042-PR-debug-86964.patch | 94 +++
  2 files changed, 95 insertions(+)
  create mode 100644 meta/recipes-devtools/gcc/gcc-8.3/0042-PR-debug-86964.patch

diff --git a/meta/recipes-devtools/gcc/gcc-8.3.inc 
b/meta/recipes-devtools/gcc/gcc-8.3.inc
index fe9c7c3602..a6b772aadd 100644
--- a/meta/recipes-devtools/gcc/gcc-8.3.inc
+++ b/meta/recipes-devtools/gcc/gcc-8.3.inc
@@ -72,6 +72,7 @@ SRC_URI = "\
 file://0039-riscv-Disable-multilib-for-OE.patch \
 file://0040-powerpc-powerpc64-Add-support-for-musl-ldso.patch \
 
file://0041-Add-a-recursion-limit-to-libiberty-s-demangling-code.patch \
+   file://0042-PR-debug-86964.patch \
  "
  SRC_URI[md5sum] = "65b210b4bfe7e060051f799e0f994896"
  SRC_URI[sha256sum] = 
"64baadfe6cc0f4947a84cb12d7f0dfaf45bb58b7e92461639596c21e02d97d2c"
diff --git a/meta/recipes-devtools/gcc/gcc-8.3/0042-PR-debug-86964.patch 
b/meta/recipes-devtools/gcc/gcc-8.3/0042-PR-debug-86964.patch
new file mode 100644
index 00..d9b5d39b77
--- /dev/null
+++ b/meta/recipes-devtools/gcc/gcc-8.3/0042-PR-debug-86964.patch
@@ -0,0 +1,94 @@
+From beb921e1106b5bcbb0c6e2be84b241327e2ffc51 Mon Sep 17 00:00:00 2001
+From: law 
+Date: Mon, 25 Mar 2019 21:19:09 +
+Subject: [PATCH]   PR debug/86964  * dwarf2out.c
+ (premark_used_variables): New function.   (prune_unused_types_walk): Do
+ not mark not premarked external   variables.  (prune_unused_types):
+ Call premark_used_variables.
+
+   * gcc.dg/debug/dwarf2/pr86964.c: New testcase.
+
+git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@269925 
138bc75d-0d04-0410-961f-82ee72b054a4
+
+Upstream-Status: Backport
+Signed-off-by: Zhixiong Chi 
+---
+ gcc/ChangeLog   |  8 ++
+ gcc/dwarf2out.c | 32 +
+ 2 files changed, 40 insertions(+)
+
+diff --git a/gcc/ChangeLog b/gcc/ChangeLog
+index 2075480ca2b..cdce539ac6f 100644
+--- a/gcc/ChangeLog
 b/gcc/ChangeLog
+@@ -1,3 +1,11 @@
++2019-03-25  Johan Karlsson 
++
++  PR debug/86964
++  * dwarf2out.c (premark_used_variables): New function.
++  (prune_unused_types_walk): Do not mark not premarked external
++  variables.
++  (prune_unused_types): Call premark_used_variables.
++
+ 2019-02-22  Release Manager
+
+   * GCC 8.3.0 released.
+diff --git a/gcc/dwarf2out.c b/gcc/dwarf2out.c
+index ae8bdee9981..b9a624e1ac7 100644
+--- a/gcc/dwarf2out.c
 b/gcc/dwarf2out.c
+@@ -22658,6 +22658,21 @@ premark_types_used_by_global_vars (void)
+   ->traverse (NULL);
+ }
+
++/* Mark all variables used by the symtab as perennial.  */
++
++static void
++premark_used_variables (void)
++{
++  /* Mark DIEs in the symtab as used.  */
++  varpool_node *var;
++  FOR_EACH_VARIABLE (var)
++{
++  dw_die_ref die = lookup_decl_die (var->decl);
++  if (die)
++  die->die_perennial_p = 1;
++}
++}
++
+ /* Generate a DW_TAG_call_site DIE in function DECL under SUBR_DIE
+for CA_LOC call arg loc node.  */
+
+@@ -29264,6 +29279,19 @@ prune_unused_types_walk (dw_die_ref die)
+
+   return;
+
++case DW_TAG_variable:
++  if (flag_debug_only_used_symbols)
++  {
++if (die->die_perennial_p)
++  break;
++
++/* premark_used_variables marks external variables --- don't mark
++   them here.  */
++if (get_AT (die, DW_AT_external))
++  return;
++  }
++  /* FALLTHROUGH */
++
+ default:
+   /* Mark everything else.  */
+   break;
+@@ -29390,6 +29418,10 @@ prune_unused_types (void)
+   /* Mark types that are used in global variables.  */
+   premark_types_used_by_global_vars ();
+
++  /* Mark variables used in the symtab.  */
++  if (flag_debug_only_used_symbols)
++premark_used_variables ();
++
+   /* Set the mark on nodes that are actually used.  */
+   prune_unused_types_walk (comp_unit_die ());
+   for (node = limbo_die_list; node; node = node->next)
+--
+2.21.0


--
-
Thanks,
Zhixiong Chi
Tel: +86-10-8477-7036

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

[OE-core] [PATCH] gcc: reduce the variables in symtab

2019-05-28 Thread Zhixiong Chi 
Signed-off-by: Zhixiong Chi 
---
 meta/recipes-devtools/gcc/gcc-8.3.inc |  1 +
 .../gcc/gcc-8.3/0042-PR-debug-86964.patch | 94 +++
 2 files changed, 95 insertions(+)
 create mode 100644 meta/recipes-devtools/gcc/gcc-8.3/0042-PR-debug-86964.patch

diff --git a/meta/recipes-devtools/gcc/gcc-8.3.inc 
b/meta/recipes-devtools/gcc/gcc-8.3.inc
index fe9c7c3602..a6b772aadd 100644
--- a/meta/recipes-devtools/gcc/gcc-8.3.inc
+++ b/meta/recipes-devtools/gcc/gcc-8.3.inc
@@ -72,6 +72,7 @@ SRC_URI = "\
file://0039-riscv-Disable-multilib-for-OE.patch \
file://0040-powerpc-powerpc64-Add-support-for-musl-ldso.patch \

file://0041-Add-a-recursion-limit-to-libiberty-s-demangling-code.patch \
+   file://0042-PR-debug-86964.patch \
 "
 SRC_URI[md5sum] = "65b210b4bfe7e060051f799e0f994896"
 SRC_URI[sha256sum] = 
"64baadfe6cc0f4947a84cb12d7f0dfaf45bb58b7e92461639596c21e02d97d2c"
diff --git a/meta/recipes-devtools/gcc/gcc-8.3/0042-PR-debug-86964.patch 
b/meta/recipes-devtools/gcc/gcc-8.3/0042-PR-debug-86964.patch
new file mode 100644
index 00..d9b5d39b77
--- /dev/null
+++ b/meta/recipes-devtools/gcc/gcc-8.3/0042-PR-debug-86964.patch
@@ -0,0 +1,94 @@
+From beb921e1106b5bcbb0c6e2be84b241327e2ffc51 Mon Sep 17 00:00:00 2001
+From: law 
+Date: Mon, 25 Mar 2019 21:19:09 +
+Subject: [PATCH]   PR debug/86964  * dwarf2out.c
+ (premark_used_variables): New function.   (prune_unused_types_walk): Do
+ not mark not premarked external   variables.  (prune_unused_types):
+ Call premark_used_variables.
+
+   * gcc.dg/debug/dwarf2/pr86964.c: New testcase.
+
+git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@269925 
138bc75d-0d04-0410-961f-82ee72b054a4
+
+Upstream-Status: Backport
+Signed-off-by: Zhixiong Chi 
+---
+ gcc/ChangeLog   |  8 ++
+ gcc/dwarf2out.c | 32 +
+ 2 files changed, 40 insertions(+)
+
+diff --git a/gcc/ChangeLog b/gcc/ChangeLog
+index 2075480ca2b..cdce539ac6f 100644
+--- a/gcc/ChangeLog
 b/gcc/ChangeLog
+@@ -1,3 +1,11 @@
++2019-03-25  Johan Karlsson 
++
++  PR debug/86964
++  * dwarf2out.c (premark_used_variables): New function.
++  (prune_unused_types_walk): Do not mark not premarked external
++  variables.
++  (prune_unused_types): Call premark_used_variables.
++
+ 2019-02-22  Release Manager
+ 
+   * GCC 8.3.0 released.
+diff --git a/gcc/dwarf2out.c b/gcc/dwarf2out.c
+index ae8bdee9981..b9a624e1ac7 100644
+--- a/gcc/dwarf2out.c
 b/gcc/dwarf2out.c
+@@ -22658,6 +22658,21 @@ premark_types_used_by_global_vars (void)
+   ->traverse (NULL);
+ }
+ 
++/* Mark all variables used by the symtab as perennial.  */
++
++static void
++premark_used_variables (void)
++{
++  /* Mark DIEs in the symtab as used.  */
++  varpool_node *var;
++  FOR_EACH_VARIABLE (var)
++{
++  dw_die_ref die = lookup_decl_die (var->decl);
++  if (die)
++  die->die_perennial_p = 1;
++}
++}
++
+ /* Generate a DW_TAG_call_site DIE in function DECL under SUBR_DIE
+for CA_LOC call arg loc node.  */
+ 
+@@ -29264,6 +29279,19 @@ prune_unused_types_walk (dw_die_ref die)
+ 
+   return;
+ 
++case DW_TAG_variable:
++  if (flag_debug_only_used_symbols)
++  {
++if (die->die_perennial_p)
++  break;
++
++/* premark_used_variables marks external variables --- don't mark
++   them here.  */
++if (get_AT (die, DW_AT_external))
++  return;
++  }
++  /* FALLTHROUGH */
++
+ default:
+   /* Mark everything else.  */
+   break;
+@@ -29390,6 +29418,10 @@ prune_unused_types (void)
+   /* Mark types that are used in global variables.  */
+   premark_types_used_by_global_vars ();
+ 
++  /* Mark variables used in the symtab.  */
++  if (flag_debug_only_used_symbols)
++premark_used_variables ();
++
+   /* Set the mark on nodes that are actually used.  */
+   prune_unused_types_walk (comp_unit_die ());
+   for (node = limbo_die_list; node; node = node->next)
+-- 
+2.21.0
-- 
2.21.0

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

[OE-core] [PATCH] gdb: Let gdbserver be empty for riscv64

2019-05-28 Thread Khem Raj 
gdbserver does not yet build for riscv64, therefore
let the package be empty so we can build core-image-sato-sdk-ptest

Signed-off-by: Khem Raj 
---
 meta/recipes-devtools/gdb/gdb.inc | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/meta/recipes-devtools/gdb/gdb.inc 
b/meta/recipes-devtools/gdb/gdb.inc
index 52119a0aaa..0f10b41734 100644
--- a/meta/recipes-devtools/gdb/gdb.inc
+++ b/meta/recipes-devtools/gdb/gdb.inc
@@ -8,3 +8,6 @@ inherit gettext
 # cross-canadian must not see this
 PACKAGES =+ "gdbserver"
 FILES_gdbserver = "${bindir}/gdbserver"
+
+ALLOW_EMPTY_gdbserver_riscv64 = "1"
+
-- 
2.21.0

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

Re: [OE-core] [PATCH] make-mod-scripts: Add nostamp flag on configure task

2019-05-28 Thread Bai, Haiqing 
Comments below, thanks your review.

-Original Message-
From: Richard Purdie [mailto:richard.pur...@linuxfoundation.org] 
Sent: 2019年5月25日 1:29
To: Bai, Haiqing; openembedded-core@lists.openembedded.org
Cc: Bruce Ashfield
Subject: Re: [OE-core] [PATCH] make-mod-scripts: Add nostamp flag on configure 
task

On Fri, 2019-05-24 at 13:49 +0800, Haiqing Bai wrote:
> Error appears while building out of tree kernel module
> after recompiling the kernel:
> bitbake -c cleanall/cleansstate virtual/kernel
> bitbake -c cleanall/cleansstate hello-mod
> bitbake virtual/kernel
> bitbake hello-mod
> 
> ERROR: Kernel configuration is invalid.
>include/generated/autoconf.h or include/config/auto.conf are
> missing.
>Run 'make oldconfig && make prepare' on kernel src to fix it.
> error: 'struct pt_regs' has no member named 'ds'; did you mean 'dx'?
> 
> make-mod-scripts must be forced to rebuild in this case to generate
> config data in 'kernel-build-artifacts/include/config'
> 
> Signed-off-by: Haiqing Bai 
> ---
>  meta/recipes-kernel/make-mod-scripts/make-mod-scripts_1.0.bb | 2 ++
>  1 file changed, 2 insertions(+)
> 
> diff --git a/meta/recipes-kernel/make-mod-scripts/make-mod-
> scripts_1.0.bb b/meta/recipes-kernel/make-mod-scripts/make-mod-
> scripts_1.0.bb
> index 97c58c5233..f55104070d 100644
> --- a/meta/recipes-kernel/make-mod-scripts/make-mod-scripts_1.0.bb
> +++ b/meta/recipes-kernel/make-mod-scripts/make-mod-scripts_1.0.bb
> @@ -12,6 +12,8 @@ S = "${WORKDIR}"
>  do_configure[depends] += "virtual/kernel:do_shared_workdir openssl-
> native:do_populate_sysroot"
>  do_compile[depends] += "virtual/kernel:do_compile_kernelmodules"
>  
> +do_configure[nostamp] = "1"
> +
>  DEPENDS += "bc-native"
>  
>  EXTRA_OEMAKE = " HOSTCC="${BUILD_CC} ${BUILD_CFLAGS}
> ${BUILD_LDFLAGS}" HOSTCPP="${BUILD_CPP}""

This sounds like a really bad idea and will make anything depending on
it rebuild in every build.
[hqbai:  Actually package 'make-mod-scripts' is a building tool needed only by 
external modules,  if 'anything'   your mean here is these external  modules,  
then the answer is 'yes',
These external modules depend on 'make-mod-scripts.',   what's this package do 
is actually equal to  'make scripts'. 


We need to ensure that these clean commands are not cleaning things out
of the shared kernel directory that they don't own.
[hqbai: Since the shared directory is 
'kernel-build-artifacts/include/config/xxx', kernel is the owner of folder but 
not these files,   I think it does not make sense for kernel to keeps these 
stuff when do  clean/cleanall ]

Cheers,

Richard

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