On 05/25/2018 11:34 AM, Andre McCurdy wrote:
On Thu, May 24, 2018 at 7:48 PM, Robert Yang wrote:
From: Jackie Huang
root login is disabled by default for openssh and we can
enable it through IMAGE_FEATURES 'debug-tweaks' or
On Thu, May 24, 2018 at 05:38:22PM -0400, Trevor Woerner wrote:
> On Thu, May 24, 2018 at 4:39 PM, Daniel Díaz wrote:
>
> > Patches are still fresh as the meadows.
> >
>
> meaning ?
I think it means that he didn't test it very well, because just renaming
the file
> -Original Message-
> From: openembedded-core-boun...@lists.openembedded.org
> [mailto:openembedded-core-boun...@lists.openembedded.org] On Behalf Of
> Alejandro Enedino Hernandez Samaniego
> Sent: Wednesday, May 23, 2018 4:09 PM
> To: openembedded-core@lists.openembedded.org
> Subject:
On Thu, May 24, 2018, 22:10 Yue Tao wrote:
> The waf is localed at ${S}/buildtools/bin/, not ${S}. Update the
> subsrcdir to look for the right path. The WARNINGs below can be fixed
> by the fix.
>
> WARNING: lib32-libtalloc-2.1.9-r0 do_configure: Unable to execute waf
>
On Thu, May 24, 2018 at 7:48 PM, Robert Yang wrote:
> From: Jackie Huang
>
> root login is disabled by default for openssh and we can
> enable it through IMAGE_FEATURES 'debug-tweaks' or
> 'allow-empty-password', so change to the same
The waf is localed at ${S}/buildtools/bin/, not ${S}. Update the
subsrcdir to look for the right path. The WARNINGs below can be fixed
by the fix.
WARNING: lib32-libtalloc-2.1.9-r0 do_configure: Unable to execute waf
--version, exit code 127. Assuming waf version without bindir/libdir support.
On 05/25/2018 10:48 AM, Robert Yang wrote:
Hi RP and Ross,
These are part of our local patches, most of them have been sent before, but
didn't get reply, would you please help to review and merge/reject them? Thank
you very much, All of them are good changes from my side.
// Robert
The
Qi said that this one can be covered by the fix:
commit 2d3e09949732ed48c8c9a328d9ab6ebbf6889b13
Author: Juro Bystricky
Date: Tue Feb 27 12:19:26 2018 -0800
dbus-test_1.12.2: various fixes
So I dropped it from the PULL.
// Robert
On 05/25/2018 10:48 AM,
Qi said that this one can be covered by the fix:
commit 2d3e09949732ed48c8c9a328d9ab6ebbf6889b13
Author: Juro Bystricky
Date: Tue Feb 27 12:19:26 2018 -0800
dbus-test_1.12.2: various fixes
So I dropped it from the PULL.
// Robert
On 05/25/2018 10:48 AM,
The following changes since commit d886fa118c930d0e551f2a0ed02b35d08617f746:
bitbake: bitbake-user-manual: Updated copyright year on title page to 2018
(2018-05-24 17:17:25 +0100)
are available in the git repository at:
git://git.pokylinux.org/poky-contrib ChenQi/buildtools-libnss-nis
Recent glibc change removed libnss-nis module from glibc and a new
recipe libnss-nis.bb was added.
After this change, we need to make sure nativesdk-libnss-nis is also
included in buildtools-tarball, otherwise, we may encounter the following
error when using 'tar' command from buildtools-tarball.
From: Jackie Huang
On other distros like ubuntu/centos, libnss-db usually provides:
- The libraries
- The Makefile to create database
(in /var/db for centos, /var/lib/misc/ for ubuntu)
- The makedb command (it's in glibc-common for centos7)
What we had is:
- The
From: Ovidiu Panait
When SDK is not installed in the default location, openssl will not be
able to find the the openssl.cnf config file:
"WARNING: can't open config file: /usr/lib/ssl/openssl.cnf"
To fix this, we need to provide the environment variable
From: Ovidiu Panait
When installing the SDK to a non-default path, running "rpm --showrc" from the
sdk will produce the following error:
error: Unable to open
/opt/windriver/wrlinux-small/10.17.41/sysroots/x86_64-wrlinuxsdk-linux/usr/lib/rpm/rpmrc
for reading: No
From: Catalin Enache
After installing an image from an iso, booting the system using
the legacy boots makes the grub prompt wait for an enter.
This is not desirable since many of this devices are embedded
devices that should start by them self without user entry.
From: Li Wang
Add option "-p" to specify fixed port number
Signed-off-by: Li Wang
Signed-off-by: Hongxu Jia
Signed-off-by: Yi Zhao
---
.../rpcbind_add_option_to_fix_port_number.patch| 130
From: Kai Kang
When set MULTILIBS with two or more items, such as for mips64:
MULTILIBS ?= "multilib:lib32 multilib:libn32"
It expands dependency once in mutlib.bbclass, and expand again in
toolchain-scripts.bbclass which causes error:
| ERROR: Nothing PROVIDES
From: Chen Qi
Add ESDK_MANIFEST_EXCLUDES to enable excluding items in sdk-conf-manifest.
By default, files under conf/ are all added to sdk-conf-manifest, as the
manifest file is set to 'conf/*'.
However, there are situations where some configuration files under conf/
From: Kai Kang
Update shadow to change ownership of /var/spool/mail from root:root to
root:mail and permission from 0755 to 0775 just as in most popular
distributions such as fedora and debian(It also set setgid bit in debian
but we don't need it).
Signed-off-by: Kai
Fixed when powerpc64:
$ bitbake -ctestsdk
[snip]
checking whether printf supports %p... configure: error: cannot run test
program while cross compiling
See `config.log' for more details.
test_cvs (oeqa.sdk.buildcvs.BuildCvsTest) ... FAIL
[snip]
The cvs_cv_func_printf_ptr is already in
From: Jackie Huang
root login is disabled by default for openssh and we can
enable it through IMAGE_FEATURES 'debug-tweaks' or
'allow-empty-password', so change to the same default
behavior for dropbear.
Signed-off-by: Jackie Huang
---
From: Jackie Huang
"allow root login" should not be bundled in ssh_allow_empty_password,
because some distro may want only one of "allow root login" and "allow
empty password", so split it out into ssh_allow_root_login and add new
imagefeature allow-root-login so they
From: Shan Hai
The chkconfig fails to list the xinetd service because the xinetd
lacks Init Script Actions in it, add the actions to fix it.
Signed-off-by: Shan Hai
Signed-off-by: Mingli Yu
---
It is helpful when exclude a lot of layers. It uses python re, and
supports multiple patterns (separated by space).
Signed-off-by: Robert Yang
---
meta/lib/oe/copy_buildsystem.py | 18 ++
1 file changed, 18 insertions(+)
diff --git
From: "Yadi.hu"
If CONFIG_KLOGD is not enabled, then the related service file should
not be installed, The error message is below:
Cannot add dependency job for unit busybox-klogd.service,
ignoring: Unit busybox-klogd.service failed to load:
No such file or
From: Li Wang
* Correct the command location in ptest scripts such as
update the line "#!/bin/awk -f" to "#!/usr/bin/awk -f" in the
file /usr/lib64/gawk/ptest/test/fcall_exit2.awk belongs
to package gawk-ptest and the line "#!/usr/local/bin/gawk -f"
to
From: Yuanjie Huang
Since libtool sysroot is not set when compiling sanitizers, the libtool
does no prefix the dependency path correctly. Fix it, so that programs
can link to sanitizer libraries without error.
Signed-off-by: Yuanjie Huang
From: Kai Kang
It fails to run some dbus-ptest cases that some symbols cannot be found:
| ./test/test-bus: relocation error: ./test/test-bus: symbol
| _dbus_threads_init_debug, version LIBDBUS_PRIVATE_1.10.10 not defined
| in file libdbus-1.so.3 with link time reference
From: Kai Kang
Sync x11 related configure options with dbus and replace EXTRA_OECONF_X
with PACKAGECONFIG for dbus-test.
Remove configure for native as well that no such native package.
Signed-off-by: Kai Kang
---
From: Hu
Fix below errors while pam is enabled on target:
root@qemux86:~# newusers
newusers: PAM: Authentication failure
root@qemux86:~# chpasswd
chpasswd: PAM: Authentication failure
The configs copied from "chgpasswd" which command works with pam.
From: Yue Tao
Check the status before start it to avoid duplicates.
Signed-off-by: Yue Tao
Signed-off-by: Robert Yang
Signed-off-by: Jeff Polk
---
Usually, the debugfs' (-dbg.tar.*) work follow is:
1) Install regular rootfs to dir_foo
2) Install debugfs (-dbg.tar.*) to the same dir_foo
So we need allow install debugfs on rootfs.
Signed-off-by: Robert Yang
---
scripts/runqemu-extract-sdk | 4 +++-
1 file
From: Mark Hatle
When displaying the buildcfg for the end user, add in processing
of the multilib variants. Only the items that are not the same as
the DEFAULTTUNE are displayed.
I.e.:
Build Configuration:
BB_VERSION= "1.19.0"
BUILD_SYS =
From: Jian Liu
When using cross compiler to build the package "lsof" on a host,
the value of LSOF_CCV in version.h genegrated by the Makefile
is the version of the compiler on the host while it should be
the version of cross compiler.
On Ubuntu host before fixed:
From: Mingli Yu
* add libselinux to PACKAGECONFIG for at
Signed-off-by: Mingli Yu
Signed-off-by: Robert Yang
---
meta/recipes-extended/at/at_3.1.20.bb | 6 ++
1 file changed, 6 insertions(+)
diff --git
Hi RP and Ross,
These are part of our local patches, most of them have been sent before, but
didn't get reply, would you please help to review and merge/reject them? Thank
you very much, All of them are good changes from my side.
// Robert
The following changes since commit
This patch has been obsolete since 2005:
https://github.com/mkj/dropbear/commit/736f370dce614b717193f45d084e9e009de723ce
Signed-off-by: Andre McCurdy
---
meta/recipes-core/dropbear/dropbear.inc | 1 -
.../dropbear/dropbear/0004-fix-2kb-keys.patch
On Thu, May 24, 2018 at 8:20 PM, Alistair Francis
wrote:
> On Thu, May 24, 2018 at 4:30 PM, Alistair Francis
> wrote:
> > On Thu, May 24, 2018 at 5:27 AM, Bruce Ashfield
> > wrote:
> >>
> >>
> >> On Thu, May 24, 2018 at 5:45
On Thu, May 24, 2018 at 4:30 PM, Alistair Francis wrote:
> On Thu, May 24, 2018 at 5:27 AM, Bruce Ashfield
> wrote:
>>
>>
>> On Thu, May 24, 2018 at 5:45 AM, Anuj Mittal wrote:
>>>
>>> On 05/03/2018 04:49 AM, Alistair
"The cpio_safer_name_suffix function in util.c in cpio 2.11 allows
remote attackers to cause a denial of service (out-of-bounds write)
via a crafted cpio file."
https://nvd.nist.gov/vuln/detail/CVE-2016-2037
Note that there appear to be two versions of this fix. The original
patch posted to
Merge contents of cpio_v2.inc into the only recipe which uses it.
Signed-off-by: Andre McCurdy
---
meta/recipes-extended/cpio/cpio_2.12.bb | 40 --
meta/recipes-extended/cpio/cpio_v2.inc | 43 -
2 files changed,
Signed-off-by: Andre McCurdy
---
meta/recipes-extended/cpio/cpio_2.12.bb | 2 --
1 file changed, 2 deletions(-)
diff --git a/meta/recipes-extended/cpio/cpio_2.12.bb
b/meta/recipes-extended/cpio/cpio_2.12.bb
index 0b83e9b..19ad69b 100644
---
On Thu, May 24, 2018 at 7:30 PM, Alistair Francis
wrote:
> On Thu, May 24, 2018 at 5:27 AM, Bruce Ashfield
> wrote:
> >
> >
> > On Thu, May 24, 2018 at 5:45 AM, Anuj Mittal
> wrote:
> >>
> >> On 05/03/2018 04:49 AM,
On Thu, May 24, 2018 at 5:27 AM, Bruce Ashfield
wrote:
>
>
> On Thu, May 24, 2018 at 5:45 AM, Anuj Mittal wrote:
>>
>> On 05/03/2018 04:49 AM, Alistair Francis wrote:
>> > +KERNEL_FEATURES_append = " ${@bb.utils.contains('MACHINE_FEATURES',
>> >
Yes, it builds fine with current master.
Ross
On 23 May 2018 at 18:35, Bruce Ashfield wrote:
> On 05/23/2018 07:10 AM, Burton, Ross wrote:
>>
>> qemuppc is failing with this:
>>
>> crypto/aes_generic.o: In function `crypto_aes_expand_key':
>>
On Thu, May 24, 2018 at 2:27 PM, Kamel Hacene wrote:
> When BUILD_REPRODUCIBLE_BINARIES is set, run cpio command with the
> --reproducible flag and set the timestamp of the created /init file to
> REPRODUCIBLE_TIMESTAMP_ROOTFS in accordance with
On Thu, May 24, 2018 at 4:39 PM, Daniel Díaz wrote:
> Patches are still fresh as the meadows.
>
meaning ?
--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
When BUILD_REPRODUCIBLE_BINARIES is set, run cpio command with the
--reproducible flag and set the timestamp of the created /init file to
REPRODUCIBLE_TIMESTAMP_ROOTFS in accordance with reproducible_final_image_task
in image.bbclass.
Signed-off-by: Kamel Hacene
---
kamel.hac...@smile.fr --
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
Patches are still fresh as the meadows.
Signed-off-by: Daniel Díaz
---
meta/recipes-extended/ltp/{ltp_20180118.bb => ltp_20180515.bb} | 0
1 file changed, 0 insertions(+), 0 deletions(-)
rename meta/recipes-extended/ltp/{ltp_20180118.bb => ltp_20180515.bb} (100%)
diff
Busybox readlink behaves diferently that coreutils readlink:
root@qt5122:~# touch /tmp/this_file_exist
root@qt5122:~# busybox readlink -f /tmp/this_file_exist
/tmp/this_file_exist
root@qt5122:~# readlink -f /tmp/this_file_exist
/tmp/this_file_exist
root@qt5122:~# readlink -f
Thanks to everyone for making this such a great community.
Thanks especially to Armin and Khem (and all past and future maintainers of
meta-openembedded!!) for allowing the project to keep moving forward.
--
___
Openembedded-core mailing list
Even older kernels than 4.4 might need even more files to be copied first,
with 3.16 kernel I'm seeing:
FLAGS: * new build flags or prefix
Makefile:358: scripts/Kbuild.include: No such file or directory
Makefile:614: arch/arm/Makefile: No such file or directory
/bin/bash:
i2cget, i2cset, i2cdump and i2cdetect may also be provided by Busybox
when CONFIG_I2CGET, CONFIG_I2CSET, CONFIG_I2CDUMP and CONFIG_I2CDETECT
are enabled respectively.
Busybox has a priority of 50.
Prior to the patch building core-image-minimal with
IMAGE_INSTALL_append = " busybox"
> That leaves only few issues in our internal components and strange failure
> with perf which fails to include various header files:
> perf/1.0-r9/perf-1.0/tools/perf/util/include/asm/byteorder.h:2:10: fatal
> error: ../../../../include/uapi/linux/swab.h: No such file or directory
>
* perf is failing to build for me since this oe-core commit:
commit 9b38c824961fc9dce51bda95c25dac91a69fc64f
Author: Hongxu Jia
Date: Tue Apr 24 11:33:47 2018 +0800
perf: make a copy of kernel source to perf workdir
the problem is that perf sources in
Otherwise, there would be a failure at image creation time; avoid
that by postponing to first boot explicitly.
Signed-off-by: Alexander Kanavin
---
meta/recipes-core/systemd/systemd_237.bb | 10 +++---
meta/recipes-core/udev/eudev_3.2.5.bb| 8 ++--
On Thu, May 24, 2018 at 5:45 AM, Anuj Mittal wrote:
> On 05/03/2018 04:49 AM, Alistair Francis wrote:
> > +KERNEL_FEATURES_append = " ${@bb.utils.contains('MACHINE_FEATURES',
> 'numa', 'features/numa/numa.scc', '', d)}"
>
> Isn't this enough to pull in the required
On 05/03/2018 04:49 AM, Alistair Francis wrote:
> +KERNEL_FEATURES_append = " ${@bb.utils.contains('MACHINE_FEATURES', 'numa',
> 'features/numa/numa.scc', '', d)}"
Isn't this enough to pull in the required configuration from
Previously a warning was printed regardless of context and nature
of the failure.
Now, the following is considered when a failure happens:
1) whether we are installing packages into a target image, or populating
a SDK with host or target packages.
2) whether the failure was due to qemu not
This helps in particular when executing nativesdk- postinsts; previously
they were attempted only with target qemu, and this obivously failed.
This could be solved by properly mapping the binary to be run to the
best available qemu variant for the binary architecture, but that
would be a lot more
Previously the library paths were passed down from recipes, and if
said recipes were allarch, and library paths were something else
than /lib and /usr/lib (multilib, x32, etc.), things broke down.
Signed-off-by: Alexander Kanavin
---
This has the following benefits:
- consistent with how the other caches are created into target rootfs
- only runs once per package manager transaction, instead of once per every
immodule package
- correctly postpones to first boot if qemu is not working; from postinst itself
this would've
Sumo release provides a transition period so that deferrals to first boot
via 'exit 1' can be converted to pkg_postinst_ontarget(). For the next release
however, postinst script failures should be treated as such.
[YOCTO #12607]
Signed-off-by: Alexander Kanavin
This was undocumented, and it's better to just always enable
full debug output, as this allows immediate generation of logs
with full diagnostics when things go not as expected.
Also, change the output of dnf from note to debug level; this
does not affect what is written to log file, but does
On 05/24/2018 05:19 AM, changqing...@windriver.com wrote:
udev-hwdb/pixbufcache/gio-module-cache/fontcache uses qemu usermode by default,
but some architecture such as Intel skylake does not support qemu usermode,
this can
lead to a build warning as below:
warning:
On 05/24/2018 05:18 AM, changqing...@windriver.com wrote:
in update_font_cache, it runs:
qemuwrapper -L $D -E LD_LIBRARY_PATH=$D/${libdir}:$D/${base_libdir} -E
${fontconfigcacheenv} $D${bindir}/fc-cache --sysroot=$D --system-only
qemuwrapper sets LD_LIBRARY_PATH=$D/${libdir}:$D/${base_libdir}
67 matches
Mail list logo