[OE-core] [PATCH 1/1] nativesdk-coreutils: a lot of warnings fixed

When we create nativesdk-coreutils, a lot of warnings appear,it show many files can't find. Because in the coreutils recipe, it didn't contain the do_install for the nativesdk, so when the alternative system check the files in the following process, it can't find the files. So we should add the

[OE-core] [PATCH 0/1] nativesdk-coreutils: a lot of warnings fixed

The following changes since commit 0f62b3e5344f63deca43091fa7909448d4f87279: quilt: fix ptest faildiff.test failed (2016-03-14 21:24:00 -0400) are available in the git repository at: git://git.openembedded.org/openembedded-core-contrib dengke/nativesdk-coreutils_many_warnings_fixed

[OE-core] [PATCH V2 1/1] sysstat: add configuration file in tmpfiles.d

In sysvinit, we create /var/log/sa via populate-volatiles.sh script and /etc/default/volatile/99_sysstat configuration file. In systemd, we need to create a corresponding configuration file under /etc/tmpfiles.d in order to create /var/log/sa. Signed-off-by: Chen Qi ---

[OE-core] [PATCH V2 0/1] sysstat: add configuration file in tmpfiles.d

Changes since V1: Rebased against latest master. The following changes since commit 300f858ba07c938427ccd05a3d7220027a03d461: local.conf.sample: Disable prelink by default (2016-03-13 22:08:55 +) are available in the git repository at:

Re: [OE-core] [PATCH 02/24] python3-native: use the previous version of python-config script

On Tue, Mar 15, 2016 at 11:29 PM, wrote: >>> This is because python3-config does not contain the version within >>> itself, >>> it reports the version of the python interpreter that it is run with. So >>> NOTABUG. >> >> If its supposed to report the version of

Re: [OE-core] [PATCH 02/24] python3-native: use the previous version of python-config script

>> This is because python3-config does not contain the version within >> itself, >> it reports the version of the python interpreter that it is run with. So >> NOTABUG. > > If its supposed to report the version of python pack its coming with > and not the interpreter its run with > then how do you

Re: [OE-core] [PATCH 02/24] python3-native: use the previous version of python-config script

On Tue, Mar 15, 2016 at 8:59 AM, Alexander Kanavin wrote: > On 03/10/2016 11:24 PM, Andreas Müller wrote: > >> This one seems to report host's python3 version: >> >> [superandy@localhost sysroots]$ >> x86_64-linux/usr/bin/python3-native/python3-config --ldflags

[OE-core] [PATCH 6/6] oe-buildenv-internal: Some clean up

* Consistent indentation (four spaces) * Use [ -z ...] and [ -n ... ] where possible * Unset temporary variables * Use $(...) instead of `...` * Avoid an unnecessary call to expr Signed-off-by: Peter Kjellerstedt --- scripts/oe-buildenv-internal | 46

[OE-core] [PATCH 5/6] oe-buildenv-internal: Add variables individually to BB_ENV_EXTRAWHITE

Instead of adding all variables to BB_ENV_EXTRAWHITE as one, treat them separately and add them one by one as needed. Signed-off-by: Peter Kjellerstedt --- scripts/oe-buildenv-internal | 26 +- 1 file changed, 21 insertions(+), 5 deletions(-)

[OE-core] [PATCH 1/6] oe-init-build-env*: Allow $OEROOT to be predefined

The current implementation of oe-init-build-env and oe-init-build-env-memres requires that they are sourced from the directory that will be known as $OEROOT. This makes it hard to write a wrapper script with the same name as the original OE script which, e.g., sources the original OE script from a

[OE-core] [PATCH 4/6] oe-buildenv-internal: Add paths to $PATH individually

Instead of assuming that the path to the scripts directory always is in $PATH directly before the bitbake directory, treat them as separate paths and add them individually to $PATH. Signed-off-by: Peter Kjellerstedt --- scripts/oe-buildenv-internal | 11 ---

[OE-core] [PATCH 3/6] oe-init-build-env*: Remove unnecessary differences between the scripts

While at it, also fix: * consistent indentation (four spaces) * unset temporary variables * use $(...) instead of `...` Signed-off-by: Peter Kjellerstedt --- oe-init-build-env| 21 ++--- oe-init-build-env-memres | 30

[OE-core] [PATCH 0/6] Improve oe-init-build-env/-memres

I started looking at the oe-init-build-env (and oe-init-build-env-memres) scripts since I wanted to add support for specifying $OEROOT from the outside. This is because we want to wrap those scripts with our own while keeping the official names (so anyone reading the official Poky documentation

[OE-core] [PATCH 2/6] oe-init-build-env*: Update/correct comment about specifying arguments

Signed-off-by: Peter Kjellerstedt --- oe-init-build-env| 8 oe-init-build-env-memres | 8 2 files changed, 8 insertions(+), 8 deletions(-) diff --git a/oe-init-build-env b/oe-init-build-env index f511b57..baab827 100755 ---

Re: [OE-core] [PATCH 02/24] python3-native: use the previous version of python-config script

On Tue, Mar 15, 2016 at 4:59 PM, Alexander Kanavin wrote: > On 03/10/2016 11:24 PM, Andreas Müller wrote: > >> This one seems to report host's python3 version: >> >> [superandy@localhost sysroots]$ >> x86_64-linux/usr/bin/python3-native/python3-config --ldflags

Re: [OE-core] [oe-commits] Alexander Kanavin : remake: update to 4.1+dbg-1.1

On Tue, 2016-03-15 at 17:48 +0200, Alexander Kanavin wrote: > On 03/10/2016 11:01 PM, Richard Purdie wrote: > > > > Fails to build after make was built. Shouldn't it be at least > > > blacklisted > > > by default so that potential user will need to explicitly decide > > > between > > > make and

Re: [OE-core] [PATCH 02/24] python3-native: use the previous version of python-config script

On 03/10/2016 11:24 PM, Andreas Müller wrote: This one seems to report host's python3 version: [superandy@localhost sysroots]$ x86_64-linux/usr/bin/python3-native/python3-config --ldflags -lpython3.4m -lpthread -ldl -lutil -lm -Xlinker -export-dynamic We are at 3.5 This is because

Re: [OE-core] [oe-commits] Alexander Kanavin : remake: update to 4.1+dbg-1.1

On 03/10/2016 11:01 PM, Richard Purdie wrote: Fails to build after make was built. Shouldn't it be at least blacklisted by default so that potential user will need to explicitly decide between make and remake (and unmerge the other one from sysroot first)? I think (but can't remember for

Re: [OE-core] [PATCH] eudev: split eudev-hwdb from eudev

On 03/15/2016 07:32 AM, Burton, Ross wrote: On 14 March 2016 at 23:09, Alejandro Hernandez > wrote: + ${@qemu_run_binary(d, '$D', '${base_bindir}/udevadm')} hwdb --update \ +--root $D

Re: [OE-core] [PATCH] eudev: split eudev-hwdb from eudev

On 14 March 2016 at 23:09, Alejandro Hernandez < alejandro.hernan...@linux.intel.com> wrote: > +${@qemu_run_binary(d, '$D', '${base_bindir}/udevadm')} hwdb > --update \ > +--root $D > udevadm is at ${bindir} with eudev, which means this script delays until first boot. I've

[OE-core] [PATCH] image.bbclass: track ROOTFS_POSTUNINSTALL_COMMAND in do_rootfs vardeps

The list of variables influencing do_rootfs was not updated when introducing ROOTFS_POSTUNINSTALL_COMMAND. As a result, making changes in commands listed there or the variables they depend on did not trigger a re-run of do_rootfs. Signed-off-by: Patrick Ohly ---

Re: [OE-core] [PATCH] libsdl: Only enable X11 support when the DISTRO supports it

On Tue, 2016-03-15 at 08:01 -0300, Otavio Salvador wrote: > On Mon, Mar 14, 2016 at 6:26 PM, Burton, Ross > wrote: > > > > On 14 March 2016 at 21:23, Otavio Salvador > > wrote: > > > > > > Do you mind to explain to me why? > > > > > > I

Re: [OE-core] [PATCH] libsdl: Only enable X11 support when the DISTRO supports it

On Mon, Mar 14, 2016 at 6:26 PM, Burton, Ross wrote: > > On 14 March 2016 at 21:23, Otavio Salvador > wrote: >> >> Do you mind to explain to me why? >> >> I would like to try to see your view on this. > > > libsdl is a good example to be

Re: [OE-core] Problems with perl 5.22

On 03/10/2016 04:54 PM, Jens Rehsack wrote: Am 10.03.2016 um 06:13 schrieb Gary Thomas : I'm working on a package (amanda - the Advanced Maryland Archiving system) that is written heavily in perl with swig interfaces to C. This code ran great until the update to perl 5.22;

[OE-core] [PATCH V2 1/1] openssl: don't move libcrypto to base_libdir

For now, if 'openssl' is enabled for ntp, ntp would still be built without openssl & libcrypto. This is because that ntp thinks openssl and libcrypto locates under the same directory. This patch removes the codes of moving libcrypto to base_libdir. Signed-off-by: Chen Qi

[OE-core] [PATCH V2 0/1] openssl: don't move libcrypto to base_libdir

Changes since V1: Rebased against latest master The following changes since commit 300f858ba07c938427ccd05a3d7220027a03d461: local.conf.sample: Disable prelink by default (2016-03-13 22:08:55 +) are available in the git repository at:

[OE-core] [PATCH 2/2] xcb-util-image: Fix build with clang

Signed-off-by: Khem Raj --- .../xorg-lib/xcb-util-image/clang.patch| 24 ++ .../xorg-lib/xcb-util-image_0.4.0.bb | 5 - 2 files changed, 28 insertions(+), 1 deletion(-) create mode 100644

[OE-core] [PATCH 1/2] musl: Update to get mips64 port

mips64 port is now available on top of 1.1.14 this updates brings it to OE Copyright file changed due to mips64 attribution being added http://git.musl-libc.org/cgit/musl/commit/COPYRIGHT?id=589aefa5b061647e8b9ad9bca3aaa8dc6222460a Signed-off-by: Khem Raj ---

Re: [OE-core] [PATCH 1/1] coreutils: fix reporting 'unknown' by `uname -p' and `uname -i'

ping ... On 10/29/2015 03:54 PM, Chen Qi wrote: This patch make `uname -p' and `uname -i' not reporting 'unknown'. It refers a to Fedora's way to do this. The coreutils upstream rejects to accept this patch, blaming the 'unknown' result to the kernel not providing enough information. As on

Re: [OE-core] [PATCH 1/1] toolchain-script: use immediate expansion for TOOLCHAIN_CONFIGSITE_NOCACHE

ping On 10/30/2015 03:50 PM, Chen Qi wrote: Use immediate expansion for the assignment to avoid other classes modifying variables like HOST_ARCH which changes the result. This happens in the meta-environment recipe. It inherits cross-canadian which changes HOST_ARCH from TARGET_ARCH to

[OE-core] [PATCH V2 1/1] dhcp: enable gentle shutdown

For now, `systemctl stop dhcpd' cannot stop dhcpd correctly, the SIGTERM signal would time out, causing a SIGKILL signal sent to dhcpd. Patch site.h to enable gentle shutdown to so that dhcpd could be stopped by SIGTERM. Signed-off-by: Chen Qi ---

[OE-core] [PATCH V2 0/1] dhcp: enable gentle shutdown

Changes since V1: Rebased against latest master. The following changes since commit 300f858ba07c938427ccd05a3d7220027a03d461: local.conf.sample: Disable prelink by default (2016-03-13 22:08:55 +) are available in the git repository at: