Re: [OE-core] musl patches

On Mon, Apr 16, 2018 at 7:02 PM ChenQi wrote: > On 04/16/2018 07:05 PM, Andreas Müller wrote: > > Hi, > > > > I am not happy plastering patches around for musl. This gets even > > worse when I see patches like this [1]: Just wipe away security checks > > unconditionally -

Re: [OE-core] musl patches

On 04/16/2018 07:05 PM, Andreas Müller wrote: Hi, I am not happy plastering patches around for musl. This gets even worse when I see patches like this [1]: Just wipe away security checks unconditionally - the developers did introduce this check not just for fun I guess... I have seen this

Re: [OE-core] [OE-CORE][sumo][python3] Generated SDK missing sqlite3

Which commit are you using? https://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=4379b29e7eede727993ee68c9eba2bdebace5108 In any case, that one should've solved it. Alejandro From: openembedded-core-boun...@lists.openembedded.org [mailto:openembedded-core-boun...@lists.openembedded.org]

[OE-core] [PATCH V3] externalsrc.bbclass: introduce INHIBIT_SRCTREE_FILE_CHECKSUMS

From: Ming Liu It defaults to be '0', but it allows the developers to choose not add file-checksums to do_compile for the entire source tree, by setting to '1'. We need this because we have a huge project with 100G bytes source files, and we do not want them to be added to

Re: [OE-core] [PATCH V2] externalsrc.bbclass: introduce INHIBIT_SRCTREE_FILE_CHECKSUMES

Oops, will send a V3. 2018-04-17 2:34 GMT+02:00 Peter Kjellerstedt : > > -Original Message- > > From: openembedded-core-boun...@lists.openembedded.org > > [mailto:openembedded-core-boun...@lists.openembedded.org] On Behalf Of > > liu.min...@gmail.com > >

Re: [OE-core] [PATCH V2] externalsrc.bbclass: introduce INHIBIT_SRCTREE_FILE_CHECKSUMES

> -Original Message- > From: openembedded-core-boun...@lists.openembedded.org > [mailto:openembedded-core-boun...@lists.openembedded.org] On Behalf Of > liu.min...@gmail.com > Sent: den 17 april 2018 02:25 > To: openembedded-core@lists.openembedded.org > Cc: Ming Liu

[OE-core] [PATCH V2] externalsrc.bbclass: introduce INHIBIT_SRCTREE_FILE_CHECKSUMES

From: Ming Liu It defaults to be '0', but it allows the developers to choose not add file-checksums to do_compile for the entire source tree, by setting to '1'. We need this because we have a huge project with 100G bytes source files, and we do not want them to be added to

Re: [OE-core] [PATCH] externalsrc.bbclass: introduce INHIBIT_SRCTREE_FILE_CHECKSUMES

My mistake, that is a typo, will send the V2 soon. //Ming Liu 2018-04-16 23:22 GMT+02:00 Andre McCurdy : > On Mon, Apr 16, 2018 at 12:26 PM, wrote: > > From: Ming Liu > > > > It defaults to be '0', but it allows the developers

Re: [OE-core] [PATCH] externalsrc.bbclass: introduce INHIBIT_SRCTREE_FILE_CHECKSUMES

On Mon, Apr 16, 2018 at 12:26 PM, wrote: > From: Ming Liu > > It defaults to be '0', but it allows the developers to choose not add > file-checksums to do_compile for the entire source tree, by setting to > '1'. > > We need this because we have a huge

Re: [OE-core] [PATCH] package.bbclass: Add '-b' option to file call in isELF

> -Original Message- > From: openembedded-core-boun...@lists.openembedded.org > [mailto:openembedded-core-boun...@lists.openembedded.org] On Behalf Of > Mark Hatle > Sent: den 16 april 2018 17:34 > To: openembedded-core@lists.openembedded.org > Subject: [OE-core] [PATCH] package.bbclass:

[OE-core] [PATCH] recipes-kernel/linux: Enable NUMA Kconfig from DISTRO_FEATURES

If the user has set numa as a distro feature enable NUMA support in the kernel config. Signed-off-by: Alistair Francis --- meta/recipes-kernel/linux/files/numa.cfg | 4 meta/recipes-kernel/linux/linux-yocto.inc | 3 +++ 2 files changed, 7 insertions(+) create

[OE-core] [rocko][PATCH] package.bbclass: Add '-b' option to file call in isELF

The isELF function works by running: result = file if 'ELF' in result By default 'file' will prepend the result with the path name of the file that is being checked. This usually works fine, such as: $ file /home/foo/openembedded-core/meta/classes/package.bbclass

[OE-core] [pyro][PATCH] package.bbclass: Add '-b' option to file call in isELF

The isELF function works by running: result = file if 'ELF' in result By default 'file' will prepend the result with the path name of the file that is being checked. This usually works fine, such as: $ file /home/foo/openembedded-core/meta/classes/package.bbclass

[OE-core] [PATCH] externalsrc.bbclass: introduce INHIBIT_SRCTREE_FILE_CHECKSUMES

From: Ming Liu It defaults to be '0', but it allows the developers to choose not add file-checksums to do_compile for the entire source tree, by setting to '1'. We need this because we have a huge project with 100G bytes source files, and we do not want them to be added to

Re: [OE-core] [OE-CORE][sumo][python3] Generated SDK missing sqlite3

Adding python3-misc to the SDK seems to have solved the issue. I saw some commits about separating the two so perhaps this is a side effect? From: Davis, Michael Sent: Monday, April 16, 2018 11:04 AM To: 'openembedded-core@lists.openembedded.org' Subject: [OE-CORE][sumo][python3] Generated SDK

[OE-core] [OE-CORE][sumo][python3] Generated SDK missing sqlite3

Testing out the upcoming sumo release and ran into an issue. Whenever I attempt to generate an sdk-ext with sumo I get a failure about missing sqlite3. Traceback (most recent call last): File "/home/mdavis/core_sdk/sysroots/x86_64-pokysdk-linux/usr/bin/devtool", line 344, in ret = main()

[OE-core] Yocto Project Status April 16, 2018

Current Dev Position: YP 2.5 M4 final close out. Next Deadline: YP 2.5 M4 release is 4/27/18 SWAT Team Rotation: SWAT lead is currently: Tracy. SWAT team rotation: Tracy -> Stephano on April 20, 2018 SWAT team rotation: Stephano -> Maxin on April 27, 2018

[OE-core] [PATCH] package.bbclass: Add '-b' option to file call in isELF

The isELF function works by running: result = file if 'ELF' in result By default 'file' will prepend the result with the path name of the file that is being checked. This usually works fine, such as: $ file /home/foo/openembedded-core/meta/classes/package.bbclass

[OE-core] [PATCH v2 2/4] libcap: fix (base_)libdir usage

The recipe wants to install libs into base_libdir, but uses "basename $libdir" to derive that. That breaks in a multiarch setup. Use the proper variable and remove the inline python usage. Signed-off-by: Koen Kooi --- meta/recipes-support/libcap/libcap_2.25.bb | 2 +- 1

[OE-core] [PATCH v2 1/4] native bbclass: handle base_libdir as well

Native.bbclass needs to fixup both base_libdir and libdir to handle things like multiarch. This fixes wic and ext4.* image failures during do_rootfs where mkfs.ext4 can't find its libraries. Signed-off-by: Koen Kooi --- meta/classes/native.bbclass | 2 ++ 1 file changed,

[OE-core] [PATCH v2 3/4] bind: fix openSSL detection when using multiarch

In multiarch /usr/include and /usr/lib/ --- meta/recipes-connectivity/bind/bind_9.10.6.bb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/meta/recipes-connectivity/bind/bind_9.10.6.bb b/meta/recipes-connectivity/bind/bind_9.10.6.bb index 8b8835b..20c8d7b 100644 ---

[OE-core] [PATCH v2 4/4] python 2.7: fix multilib patch to accept multiarch style paths

Using 'basename' to strip the prefix fails when using multiarch style paths. Signed-off-by: Koen Kooi --- meta/recipes-devtools/python/python.inc| 6 ++ meta/recipes-devtools/python/python/multilib.patch | 2 +- 2 files changed, 7 insertions(+), 1

[OE-core] musl patches

Hi, I am not happy plastering patches around for musl. This gets even worse when I see patches like this [1]: Just wipe away security checks unconditionally - the developers did introduce this check not just for fun I guess... I have seen this already elsewhere so: musl maintainers please take

Re: [OE-core] [PATCH] run-postinsts: Replace pi_dir variable test

I'll drop it myself, but in the future note that PR bumps are not required. Ross On 14 April 2018 at 07:54, Niko Mauno wrote: > Since commit 5159ddcb62682e1b7e63a20a9218ea96e3fe10a2 string length test > performed against pi_dir has effectively never been able to succeed. > >

Re: [OE-core] dropping commerical flags in mpg123 and lame recipes

I *think* we're good to do this. If you could send a patch with a nice long commit message with sources and comparisons to other distros, then we can have a concrete patch to review and get further advice on. Ross On 15 April 2018 at 09:12, Carlos Rafael Giani wrote: >

Re: [OE-core] [PATCH] u-boot: Upgrade to 2018.03 release

On 04/16/2018 10:38 AM, yamada.masah...@socionext.com wrote: > Hi. > >> -Original Message- >> From: Martin Hundebøll [mailto:m...@prevas.dk] >> Sent: Wednesday, April 11, 2018 5:42 PM >> To: Yamada, Masahiro/山田 真弘 ; >> ma...@denx.de; raj.k...@gmail.com >>

[OE-core] [PATCH 3/4] gcc-runtime: Disable gcc version of libssp

libssp is implemented fully in glibc as well as in musl so we really do not need the gcc version of this library except may be for mingw, where we keep it enabled anyway gcc in OE is built with the knowledge that C library already provides libssp implementation, we should therefore not need the

[OE-core] [PATCH 4/4] libunwind: Drop adding libssp to linker flags

This is no longer needed as gcc provided libssp is not built Signed-off-by: Khem Raj --- meta/recipes-support/libunwind/libunwind.inc | 2 -- 1 file changed, 2 deletions(-) diff --git a/meta/recipes-support/libunwind/libunwind.inc

[OE-core] [PATCH 1/4] libssp-nonshared: Add recipe

libssp-nonshared is a minimal gcc runtime piece which is needed on non-glibc systems which do implement libssp APIs in libc Signed-off-by: Khem Raj --- meta/recipes-core/musl/libssp-nonshared.bb| 39 .../musl/libssp-nonshared/ssp-local.c | 45

[OE-core] [PATCH 2/4] musl: Depend on libssp-nonshared

libssp-nonshared is required on musl since it does not implement the gcc runtime piece of libssp, which actually it a gcc optimization to reach to __stack_chk_fail Signed-off-by: Khem Raj --- meta/recipes-core/musl/musl_git.bb | 3 ++- 1 file changed, 2 insertions(+), 1