[OE-core] [PATCH v2] udev-extraconf: Add systemd-mount to udev-extraconf/mount.sh

This patch fixs the problem that block devices unable to be formatted when systemd and udev-extraconf recipes added to rootfs. If we add systemd and udev-extraconf recipes to rootfs: VIRTUAL-RUNTIME_init_manager = "systemd" DISTRO_FEATURES_append = " systemd"

Re: [OE-core] [PATCH] udev-extraconf: Add systemd-mount to mount.sh

I am very sorry, this is my fault. My original idea is to modify udev-extraconf/mount.sh. And I will remake a patch. Sorry again. Please ignore this patch. On 2018年04月12日 09:35, Christopher Larson wrote: Why are you adding a new mount.sh at meta/recipes-core/udev/mount.sh rather than

Re: [OE-core] [PATCH] udev-extraconf: Add systemd-mount to mount.sh

Why are you adding a new mount.sh at meta/recipes-core/udev/mount.sh rather than updating the existing one at meta/recipes-core/udev/udev-extraconf/mount.sh? On Mon, Apr 9, 2018 at 12:28 AM, Hongzhi.Song wrote: > This patch fixs the problem that block devices unable

Re: [OE-core] [PATCH] image_types: use pigz to create .gz files

On Wed, Apr 11, 2018 at 6:19 PM, Denys Dmytriyenko wrote: > On Wed, Apr 11, 2018 at 05:07:38PM +0100, Burton, Ross wrote: >> Woud be interesting to see a benchmark of a full build from scratch >> with host gzip vs host pigz... > > Is pigz so widely used now to be available in

Re: [OE-core] [PATCH] udev-extraconf: Add systemd-mount to mount.sh

ping //Hongzhi On 2018年04月09日 15:28, Hongzhi.Song wrote: This patch fixs the problem that block devices unable to be formatted when systemd and udev-extraconf recipes added into rootfs. If we add systemd and udev-extraconf recipes into rootfs: VIRTUAL-RUNTIME_init_manager = "systemd"

Re: [OE-core] [PATCH] image_types: use pigz to create .gz files

On Wed, Apr 11, 2018 at 05:07:38PM +0100, Burton, Ross wrote: > Woud be interesting to see a benchmark of a full build from scratch > with host gzip vs host pigz... Is pigz so widely used now to be available in every Linux distro like gzip? > On 11 April 2018 at 17:03, Khem Raj

Re: [OE-core] [PATCH 00/38] Morty Next pull request

On Wed, 2018-04-11 at 17:07 +0200, Martin Jansa wrote: > I think I've found the reason why it was failing for me. > > glibc is now the only component in morty release which is using > TMPDIR/sysroots-components (normally used only after RSS): > oe-core$ git grep "\${STAGING_DIR}-components" >

Re: [OE-core] [PATCH] dropbear: update to 2018.76

For some reason I get this when building: WARNING: dropbear-2018.76-r0 do_patch: Some of the context lines in patches were ignored. This can lead to incorrectly applied patches. The context lines in the patches can be updated with devtool: devtool modify devtool finish

Re: [OE-core] [PATCH 2/2] weston: upgrade to 4.0.0

Yes, this is a bit of a known bug although I didn't actually file one until now: https://bugzilla.yoctoproject.org/show_bug.cgi?id=12674 Cheers, Paul On Wednesday, 11 April 2018 11:17:51 AM NZST Burton, Ross wrote: > Ah presumably this is because the U-S is after the scissors. Denys, > when

Re: [OE-core] [RFC][PATCH 4/5] libressl: add a recipe to support openssh

On Wed, Apr 11, 2018 at 3:03 AM, Alexander Kanavin wrote: > On 04/11/2018 11:38 AM, Andre McCurdy wrote: >> >> I played around with completely replacing openssl with libressl a year >> or so ago and it went fairly smoothly (at least as far as I tested). >> That

Re: [OE-core] [RFC][PATCH 3/5] openssl: update to 1.1.1

On Wed, Apr 11, 2018 at 3:09 AM, Alexander Kanavin wrote: > On 04/11/2018 12:20 AM, Andre McCurdy wrote: >>> >>> -#| engines/afalg/e_afalg.c: In function 'eventfd': >>> -#| engines/afalg/e_afalg.c:110:20: error: '__NR_eventfd' undeclared >>> (first use in this

[OE-core] [PATCH v2 2/2] weston: upgrade to 4.0.0

From: Denys Dmytriyenko Official announcement: https://lists.freedesktop.org/archives/wayland-devel/2018-April/037768.html Dropped previously backported fix-missing-header.patch and weston-gl-renderer-Set-pitch-correctly-for-subsampled-textures.patch Refresh remaining local

[OE-core] [PATCH] scripts/test-dependencies.sh: remove

* with RSS used in pyro this script isn't very useful anymore * RSS makes sure that the dependencies are almost always deterministic the only case known to me where dependencies are different based on what was already built in TMPDIR are runtime dependencies resolved by shlibs code in

Re: [OE-core] [PATCH] image_types: use pigz to create .gz files

Woud be interesting to see a benchmark of a full build from scratch with host gzip vs host pigz... On 11 April 2018 at 17:03, Khem Raj wrote: > On Wed, Apr 11, 2018 at 6:36 AM, Burton, Ross wrote: >> Wouldn't that introduce a fun circular dependency if

Re: [OE-core] [PATCH] image_types: use pigz to create .gz files

On Wed, Apr 11, 2018 at 6:36 AM, Burton, Ross wrote: > Wouldn't that introduce a fun circular dependency if pigz-native needs > to be built? > interesting idea certainly, if it ends up with improvements in build time, we could add pigz to host dependencies. > Ross > > On

Re: [OE-core] [PATCH] distro: default: Change Go default version to 1.9

On Wed, Apr 11, 2018 at 7:32 AM, Otavio Salvador wrote: > For the time being, there is a serious bug[1] in Go 1.10 when it comes to > use the shared runtime support which cases problems in multiple projects. > > 1. https://github.com/golang/go/issues/24640 > > It is

Re: [OE-core] [PATCH 1/1] python-xcbgen_1.12: improve reproducibility

This would solve the .pyc timestamps problem. However, from reproducibility point of view, it is a bit more desirable to use python-native, as - in principle - different host Python versions can produce different compiled code as well. So it is not the timestamps only.

Re: [OE-core] [PATCH 00/38] Morty Next pull request

I think I've found the reason why it was failing for me. glibc is now the only component in morty release which is using TMPDIR/sysroots-components (normally used only after RSS): oe-core$ git grep "\${STAGING_DIR}-components" meta/recipes-core/glibc/glibc-locale.inc:LOCALETREESRC =

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

On 04/11/2018 04:47 PM, Burton, Ross wrote: > On 9 April 2018 at 00:02, Marek Vasut wrote: >> This upgrades the U-Boot from 2018.01 to 2018.03 release and drops >> patches accepted upstream, getting the patch count to zero. > > Are you proposing this for 2.5/Sumo (breaking the

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

On 9 April 2018 at 00:02, Marek Vasut wrote: > This upgrades the U-Boot from 2018.01 to 2018.03 release and drops > patches accepted upstream, getting the patch count to zero. Are you proposing this for 2.5/Sumo (breaking the freeze) or is it fine to sit in master-next until 2.5

[OE-core] [PATCH] distro: default: Change Go default version to 1.9

For the time being, there is a serious bug[1] in Go 1.10 when it comes to use the shared runtime support which cases problems in multiple projects. 1. https://github.com/golang/go/issues/24640 It is still unclear if the problem arises from a bug inside the compiler itself or it makes a real

Re: [OE-core] [PATCH] image_types: use pigz to create .gz files

Wouldn't that introduce a fun circular dependency if pigz-native needs to be built? Ross On 11 April 2018 at 11:53, Martin Jansa wrote: > What about using pigz for sstate-cache archives? > > On Tue, Apr 10, 2018 at 4:35 PM, Ross Burton wrote: >>

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

Hi, On 2018-04-11 04:28, yamada.masah...@socionext.com wrote: Hi. I had to patch up our own u-boot recipe as shown in the attached patch to make v2018.03 compile for qemu-x86. The thing is that the build of pylibfdt became unconditional since 15b97f5c5e ('pylibfdt: move pylibfdt to

Re: [OE-core] [PATCH] image_types: use pigz to create .gz files

What about using pigz for sstate-cache archives? On Tue, Apr 10, 2018 at 4:35 PM, Ross Burton wrote: > Since pigz is no longer a drop-in replacement for gzip (oe-core 1624b7b) > the > image creation has been using gzip instead of pigz, despite still > depending on >

Re: [OE-core] [RFC][PATCH 3/5] openssl: update to 1.1.1

On 04/11/2018 12:20 AM, Andre McCurdy wrote: -#| engines/afalg/e_afalg.c: In function 'eventfd': -#| engines/afalg/e_afalg.c:110:20: error: '__NR_eventfd' undeclared (first use in this function) -#| return syscall(__NR_eventfd, n); -#| ^~~~ -EXTRA_OECONF_aarch64

Re: [OE-core] [RFC][PATCH 4/5] libressl: add a recipe to support openssh

On 04/11/2018 11:38 AM, Andre McCurdy wrote: I played around with completely replacing openssl with libressl a year or so ago and it went fairly smoothly (at least as far as I tested). That was with libressl 2.4.2 and my recipe built with autotools rather than cmake though. Did you try to build

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

> Op 9 apr. 2018, om 18:36 heeft Richard Purdie > het volgende geschreven: > > On Mon, 2018-04-09 at 13:56 +0200, Koen Kooi wrote: >> In multiarch /usr/include and /usr/lib/> level anymore. This change will pass a correct includedir, but a >> wrong libdir,

Re: [OE-core] [RFC][PATCH 4/5] libressl: add a recipe to support openssh

On Tue, Apr 10, 2018 at 5:07 AM, Alexander Kanavin wrote: > After reading through this: > > https://github.com/openssh/openssh-portable/pull/48 > > and this thread: > > https://lists.mindrot.org/pipermail/openssh-unix-dev/2017-October/036344.html > > I've

[OE-core] [PATCH 0/1] valgrind: fix the shared object issue while prelink ptest

The following changes since commit 0a0d01adddf6b4abc91f3fda93055da061f82a5d: license.bbclass: be a bit more strict when searching ${PN}-${LICENSE_PACKAGE_SUFFIX} in packages (2018-04-10 09:10:36 +0100) are available in the git repository at: git://git.pokylinux.org/poky-contrib

[OE-core] [PATCH 1/1] valgrind: fix the shared object issue while prelink ptest

From: Zhixiong Chi If valgrind-ptest is installed, we will get the some prelink error like below at do_image: .../usr/sbin/prelink: /usr/lib64/valgrind/ptest/memcheck/tests/wrap7:\ Could not find one of the dependencies: \ .../usr/sbin//prelink-rtld: error \

[OE-core] [PATCH 1/2] patch: fix CVE-2018-6951

From: Jackie Huang * CVE detail: https://nvd.nist.gov/vuln/detail/CVE-2018-6951 * upstream tracking: http://savannah.gnu.org/bugs/?53132 * Fix segfault with mangled rename patch - src/pch.c (intuit_diff_type): Ensure that two filenames are specified for

[OE-core] [PATCH 2/2] patch: fix CVE-2018-1000156

From: Jackie Huang * CVE detail: https://nvd.nist.gov/vuln/detail/CVE-2018-1000156 * upstream tracking: https://savannah.gnu.org/bugs/index.php?53566 * Fix arbitrary command execution in ed-style patches: - src/pch.c (do_ed_script): Write ed script to a temporary

[OE-core] [PATCH 0/2] patch: fix CVE-2018-6951 and CVE-2018-1000156

From: Jackie Huang These are also needed for previous releases, so I think they should be backported to the branch for 2.5 and 2.4 as well. -- The following changes since commit 29f65bda6d2c9fea4adb125c4857ee64f9312b9f: nativesdk-glibc: Split glibc and libcrypt to