1. yocto@lists.yoctoproject.org
  2. Messages
   Date   
Re: [meta-lts-mixins][dunfell/go PATCH 1/4] Initial commit: add license, readme and layer config.

Michael Halstead
 

Thank you for the ping. These branches are ready for you.


On Tue, Feb 1, 2022 at 6:23 AM Alexander Kanavin <alex.kanavin@...> wrote:
On Thu, 27 Jan 2022 at 21:06, Denys Dmytriyenko <denis@...> wrote:
On Thu, Jan 27, 2022 at 06:07:06PM +0100, Alexander Kanavin wrote:
> A question specifically to Denys, how can I actually get this into the
> mixin repo, and have commit rights to the branch? We've tested this quite
> well in private, and there are further enhancements coming up.

Michael,

Would it be possible to create 2 additional branches in the meta-lts-mixins
repository at https://git.yoctoproject.org/meta-lts-mixins/ called
"dunfell/go" and also "dunfell/docker" and give Alex push rights to them?

Please let us know, thanks a lot!

Ping, please :)

Alex


--
Michael Halstead
Linux Foundation / Yocto Project
Systems Operations Engineer
Issues setting SELinux file contexts during build #selinux

Ansh
 

Hi all,

I am currently working on enabling SELinux on an x86 system (Yocto version 2.4). I was able to successfully enable SELinux on the target but need to set SELinux file contexts during the build. I have inherited the selinux-image.bbclass in my image recipe and can confirm that it's executed during the build. But, when I boot up the image on target all the files have the wrong (or default) file contexts. For e.g. all files in /etc have system_u:object_r:root_t:s0 labels. When I run restorecon, the files get the correct labels. I have managed to narrow it down to the following two issues:

1. setfiles fails during the build but doesn't return any error or error msg causing the build to pass

I looked into the pseudo database table xattr to check if the xattrs are set during the build and found the table empty. So I modified the selinux-image.bbclass and added a setfattr to set xattr for a single file in /etc before it runs setfiles. After the build, I found one entry for the same file for which I was using the setfattr command in the xattr table of pseudo db and was also able to get the xattr using getfattr in the modified selinux-image.bbclass. So that means setfattr was working as expected but not setfiles. Next, I enabled some debug logs for pseudo and found the following that points to setfiles failing after it tries to read security.restorecon_last. Any pointer as to why it is trying to read security.restorecon_last xattr (even though we are not using -d option for setfiles) and fails if it doesn't find it?

27286: wrapper called: getxattr
27286: getxattr - signals blocked, obtaining lock
27286: <nil> + build/tmp/work/x86_ctm-poky-linux-musl/custom-image/1.0-r0/rootfs => <build/tmp/work/x86_ctm-poky-linux-musl/custom-image/1.0-r0/rootfs>
27286: base_path: <nil></>build/tmp/work/x86_ctm-poky-linux-musl/custom-image/1.0-r0/rootfs
27286: root_path [getxattr, 7008]: 'build/tmp/work/x86_ctm-poky-linux-musl/custom-image/1.0-r0/rootfs' from 'build/tmp/work/x86_ctm-poky-linux-musl/custom-image/1.0-r0/rootfs'
27286: getxattr(build/tmp/work/x86_ctm-poky-linux-musl/custom-image/1.0-r0/rootfs [fd -1], security.restorecon_last)
27286: getxattr, name 'security.restorecon_last'
27286: get-xattr security.restorecon_last -> build/tmp/work/x86_ctm-poky-linux-musl/custom-image/1.0-r0/rootfs (+buf) (040755): processing request [ino 146615528]
27286: sending request [ino 146615528]
27286: sending a message: ino 146615528
27286: msg type 3 (get-xattr), external path build/tmp/work/x86_ctm-poky-linux-musl/custom-image/1.0-r0/rootfs, mode 040755
27286: wrote 184 bytes
27286: sent!
27286: got header, type 4, pathlen 0
27286: got response type 4
27286: (27286) fail

 2. xattrs set during the build are not present on the target

As mentioned above, I modified to selinux-image.bbclass to set xattr for a single file in /etc. This works during the build since I can see the corresponding entry in pseudo db and also can get the set xattr using getfattr in the same selinux-image.bbclass. But when I boot up the image on target the xattr is replaced by (I am guessing) the default SELinux label of system_u:object_r:root_t:s0. I am using initramfs for packaging the root filesystem and I found that cpio ignores xattrs and also initramfs doesn't support xattrs. Does that mean I can't set the file contexts during the build because I am using initramfs and cpio?

Thanks,
Ansh
Re: Build error:undefined reference to `stime' on Yocto Warrior

Sourabh Hegde
 

Hello @Khem,

Thanks for the quick response.

Can you please let me know where and how to include this patch in poky/meta?

Thanks in advance

On Wed, Feb 2, 2022, 21:19 Khem Raj <raj.khem@...> wrote:
you need something like this

https://patchwork.openembedded.org/patch/172282/

On Wed, Feb 2, 2022 at 11:43 AM Sourabh Hegde <hrsourabh011@...> wrote:
>
> Hello All,
>
> When I execute the bitbake for my custom image recipe I hit the below issue related to "qemu-native/3.1.1.1-r0/qemu-3.1.1.1/linux-user/syscall.c:7404: undefined reference to `stime'".
>
> DEBUG: Executing shell function do_compile
> NOTE: make -j 8 LD=ld  AR=ar OBJCOPY=objcopy LDFLAGS=-L/root/build-rauc/tmp-glibc/work/x86_64-linux/qemu-native/3.1.1.1-r0/recipe-sysroot-native/usr/lib                         -L/root/build-rauc/tmp-glibc/work/x86_64-linux/qemu-native/3.1.1.1-r0/recipe-sysroot-native/lib                         -Wl,--enable-new-dtags                         -Wl,-rpath-link,/root/build-rauc/tmp-glibc/work/x86_64-linux/qemu-native/3.1.1.1-r0/recipe-sysroot-native/usr/lib                         -Wl,-rpath-link,/root/build-rauc/tmp-glibc/work/x86_64-linux/qemu-native/3.1.1.1-r0/recipe-sysroot-native/lib                         -Wl,-rpath,/root/build-rauc/tmp-glibc/work/x86_64-linux/qemu-native/3.1.1.1-r0/recipe-sysroot-native/usr/lib                         -Wl,-rpath,/root/build-rauc/tmp-glibc/work/x86_64-linux/qemu-native/3.1.1.1-r0/recipe-sysroot-native/lib                         -Wl,-O1 -fuse-ld=bfd
>   LINK    i386-linux-user/qemu-i386
>   LINK    mipsel-linux-user/qemu-mipsel
>   LINK    arm-linux-user/qemu-arm
>   LINK    mips-linux-user/qemu-mips
>   LINK    ppc-linux-user/qemu-ppc
>   GEN     x86_64-linux-user/config-target.h
>   LINK    sh4-linux-user/qemu-sh4
>   CC      x86_64-linux-user/exec.o
>   CC      x86_64-linux-user/tcg/tcg.o
>   CC      x86_64-linux-user/tcg/tcg-op.o
> /root/build-rauc/tmp-glibc/hosttools/ld.bfd: linux-user/syscall.o: in function `do_syscall1':
> /root/build-rauc/tmp-glibc/work/x86_64-linux/qemu-native/3.1.1.1-r0/qemu-3.1.1.1/linux-user/syscall.c:7404: undefined reference to `stime'
> collect2: error: ld returned 1 exit status
> make[1]: *** [Makefile:199: qemu-arm] Error 1
> make: *** [Makefile:483: subdir-arm-linux-user] Error 2
> make: *** Waiting for unfinished jobs....
>   CC      x86_64-linux-user/tcg/tcg-op-vec.o
> /root/build-rauc/tmp-glibc/hosttools/ld.bfd: linux-user/syscall.o: in function `do_syscall1':
> /root/build-rauc/tmp-glibc/work/x86_64-linux/qemu-native/3.1.1.1-r0/qemu-3.1.1.1/linux-user/syscall.c:7404: undefined reference to `stime'
> collect2: error: ld returned 1 exit status
> make[1]: *** [Makefile:199: qemu-i386] Error 1
> make: *** [Makefile:483: subdir-i386-linux-user] Error 2
>   CC      x86_64-linux-user/tcg/tcg-op-gvec.o
> /root/build-rauc/tmp-glibc/hosttools/ld.bfd: linux-user/syscall.o: in function `do_syscall1':
> /root/build-rauc/tmp-glibc/work/x86_64-linux/qemu-native/3.1.1.1-r0/qemu-3.1.1.1/linux-user/syscall.c:7404: undefined reference to `stime'
> collect2: error: ld returned 1 exit status
> make[1]: *** [Makefile:199: qemu-sh4] Error 1
> make: *** [Makefile:483: subdir-sh4-linux-user] Error 2
>   CC      x86_64-linux-user/tcg/tcg-common.o
> /root/build-rauc/tmp-glibc/hosttools/ld.bfd: linux-user/syscall.o: in function `do_syscall1':
> /root/build-rauc/tmp-glibc/work/x86_64-linux/qemu-native/3.1.1.1-r0/qemu-3.1.1.1/linux-user/syscall.c:7404: undefined reference to `stime'
> collect2: error: ld returned 1 exit status
> make[1]: *** [Makefile:199: qemu-ppc] Error 1
> make: *** [Makefile:483: subdir-ppc-linux-user] Error 2
>   CC      x86_64-linux-user/tcg/optimize.o
> /root/build-rauc/tmp-glibc/hosttools/ld.bfd: linux-user/syscall.o: in function `do_syscall1':
> /root/build-rauc/tmp-glibc/work/x86_64-linux/qemu-native/3.1.1.1-r0/qemu-3.1.1.1/linux-user/syscall.c:7404: undefined reference to `stime'
> collect2: error: ld returned 1 exit status
> make[1]: *** [Makefile:199: qemu-mipsel] Error 1
> make: *** [Makefile:483: subdir-mipsel-linux-user] Error 2
>   CC      x86_64-linux-user/fpu/softfloat.o
> /root/build-rauc/tmp-glibc/hosttools/ld.bfd: linux-user/syscall.o: in function `do_syscall1':
> /root/build-rauc/tmp-glibc/work/x86_64-linux/qemu-native/3.1.1.1-r0/qemu-3.1.1.1/linux-user/syscall.c:7404: undefined reference to `stime'
> collect2: error: ld returned 1 exit status
> make[1]: *** [Makefile:199: qemu-mips] Error 1
> make: *** [Makefile:483: subdir-mips-linux-user] Error 2
>   CC      x86_64-linux-user/disas.o
>   GEN     x86_64-linux-user/gdbstub-xml.c
>   CC      x86_64-linux-user/gdbstub.o
>   CC      x86_64-linux-user/thunk.o
>   CC      x86_64-linux-user/accel/stubs/hax-stub.o
>   CC      x86_64-linux-user/accel/stubs/hvf-stub.o
>   CC      x86_64-linux-user/accel/stubs/whpx-stub.o
>   CC      x86_64-linux-user/accel/stubs/kvm-stub.o
>   CC      x86_64-linux-user/accel/tcg/tcg-runtime.o
>   CC      x86_64-linux-user/accel/tcg/tcg-runtime-gvec.o
>   CC      x86_64-linux-user/accel/tcg/cpu-exec.o
>   CC      x86_64-linux-user/accel/tcg/cpu-exec-common.o
>   CC      x86_64-linux-user/accel/tcg/translate-all.o
>   CC      x86_64-linux-user/accel/tcg/translator.o
>   CC      x86_64-linux-user/accel/tcg/user-exec.o
>   CC      x86_64-linux-user/accel/tcg/user-exec-stub.o
>   CC      x86_64-linux-user/linux-user/main.o
>   CC      x86_64-linux-user/linux-user/syscall.o
>   CC      x86_64-linux-user/linux-user/strace.o
>   CC      x86_64-linux-user/linux-user/mmap.o
>   CC      x86_64-linux-user/linux-user/signal.o
>   CC      x86_64-linux-user/linux-user/elfload.o
> In file included from /usr/include/string.h:495,
>                  from /root/build-rauc/tmp-glibc/work/x86_64-linux/qemu-native/3.1.1.1-r0/qemu-3.1.1.1/include/qemu/osdep.h:84,
>                  from /root/build-rauc/tmp-glibc/work/x86_64-linux/qemu-native/3.1.1.1-r0/qemu-3.1.1.1/linux-user/elfload.c:2:
> In function ‘strncpy’,
>     inlined from ‘fill_psinfo’ at /root/build-rauc/tmp-glibc/work/x86_64-linux/qemu-native/3.1.1.1-r0/qemu-3.1.1.1/linux-user/elfload.c:3158:12,
>     inlined from ‘fill_note_info’ at /root/build-rauc/tmp-glibc/work/x86_64-linux/qemu-native/3.1.1.1-r0/qemu-3.1.1.1/linux-user/elfload.c:3340:5,
>     inlined from ‘elf_core_dump’ at /root/build-rauc/tmp-glibc/work/x86_64-linux/qemu-native/3.1.1.1-r0/qemu-3.1.1.1/linux-user/elfload.c:3489:9:
> /usr/include/x86_64-linux-gnu/bits/string_fortified.h:106:10: warning: ‘__builtin_strncpy’ specified bound 16 equals destination size [-Wstringop-truncation]
>   106 |   return __builtin___strncpy_chk (__dest, __src, __len, __bos (__dest));
>       |          ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>   CC      x86_64-linux-user/linux-user/linuxload.o
>   CC      x86_64-linux-user/linux-user/uaccess.o
>   CC      x86_64-linux-user/linux-user/uname.o
>   CCAS    x86_64-linux-user/linux-user/safe-syscall.o
>   CC      x86_64-linux-user/linux-user/x86_64/signal.o
>   CC      x86_64-linux-user/linux-user/x86_64/cpu_loop.o
>   CC      x86_64-linux-user/linux-user/exit.o
>   CC      x86_64-linux-user/linux-user/fd-trans.o
>   CC      x86_64-linux-user/target/i386/helper.o
>   CC      x86_64-linux-user/target/i386/cpu.o
>   CC      x86_64-linux-user/target/i386/gdbstub.o
>   CC      x86_64-linux-user/target/i386/xsave_helper.o
>   CC      x86_64-linux-user/target/i386/translate.o
>   CC      x86_64-linux-user/target/i386/bpt_helper.o
>   CC      x86_64-linux-user/target/i386/cc_helper.o
>   CC      x86_64-linux-user/target/i386/excp_helper.o
>   CC      x86_64-linux-user/target/i386/fpu_helper.o
>   CC      x86_64-linux-user/target/i386/int_helper.o
>   CC      x86_64-linux-user/target/i386/mem_helper.o
>   CC      x86_64-linux-user/target/i386/misc_helper.o
>   CC      x86_64-linux-user/target/i386/mpx_helper.o
>   CC      x86_64-linux-user/target/i386/seg_helper.o
>   CC      x86_64-linux-user/target/i386/smm_helper.o
>   CC      x86_64-linux-user/target/i386/svm_helper.o
>   CC      x86_64-linux-user/target/i386/sev-stub.o
>   GEN     trace/generated-helpers.c
>   CC      x86_64-linux-user/trace/control-target.o
>   CC      x86_64-linux-user/gdbstub-xml.o
>   CC      x86_64-linux-user/trace/generated-helpers.o
>   LINK    x86_64-linux-user/qemu-x86_64
> ERROR: oe_runmake failed
> WARNING: exit code 1 from a shell command.
> ERROR: Function failed: do_compile (log file is located at /root/build-rauc/tmp-glibc/work/x86_64-linux/qemu-native/3.1.1.1-r0/temp/log.do_compile.5584)
>
>
> I am using "Warrior" version due to limitation from other meta-layers. I have read that above issue is fixed in newer versions of Yocto. But how can i fix this in Warrior? Is there any workaround?
>
> Can someone please help me resolve it?
>
> Your help will be much appreciated.
>
> Thanks in advance.
>
>
Re: Build error:undefined reference to `stime' on Yocto Warrior

Khem Raj
 

you need something like this

https://patchwork.openembedded.org/patch/172282/

On Wed, Feb 2, 2022 at 11:43 AM Sourabh Hegde <hrsourabh011@gmail.com> wrote:

Hello All,

When I execute the bitbake for my custom image recipe I hit the below issue related to "qemu-native/3.1.1.1-r0/qemu-3.1.1.1/linux-user/syscall.c:7404: undefined reference to `stime'".

DEBUG: Executing shell function do_compile
NOTE: make -j 8 LD=ld AR=ar OBJCOPY=objcopy LDFLAGS=-L/root/build-rauc/tmp-glibc/work/x86_64-linux/qemu-native/3.1.1.1-r0/recipe-sysroot-native/usr/lib -L/root/build-rauc/tmp-glibc/work/x86_64-linux/qemu-native/3.1.1.1-r0/recipe-sysroot-native/lib -Wl,--enable-new-dtags -Wl,-rpath-link,/root/build-rauc/tmp-glibc/work/x86_64-linux/qemu-native/3.1.1.1-r0/recipe-sysroot-native/usr/lib -Wl,-rpath-link,/root/build-rauc/tmp-glibc/work/x86_64-linux/qemu-native/3.1.1.1-r0/recipe-sysroot-native/lib -Wl,-rpath,/root/build-rauc/tmp-glibc/work/x86_64-linux/qemu-native/3.1.1.1-r0/recipe-sysroot-native/usr/lib -Wl,-rpath,/root/build-rauc/tmp-glibc/work/x86_64-linux/qemu-native/3.1.1.1-r0/recipe-sysroot-native/lib -Wl,-O1 -fuse-ld=bfd
LINK i386-linux-user/qemu-i386
LINK mipsel-linux-user/qemu-mipsel
LINK arm-linux-user/qemu-arm
LINK mips-linux-user/qemu-mips
LINK ppc-linux-user/qemu-ppc
GEN x86_64-linux-user/config-target.h
LINK sh4-linux-user/qemu-sh4
CC x86_64-linux-user/exec.o
CC x86_64-linux-user/tcg/tcg.o
CC x86_64-linux-user/tcg/tcg-op.o
/root/build-rauc/tmp-glibc/hosttools/ld.bfd: linux-user/syscall.o: in function `do_syscall1':
/root/build-rauc/tmp-glibc/work/x86_64-linux/qemu-native/3.1.1.1-r0/qemu-3.1.1.1/linux-user/syscall.c:7404: undefined reference to `stime'
collect2: error: ld returned 1 exit status
make[1]: *** [Makefile:199: qemu-arm] Error 1
make: *** [Makefile:483: subdir-arm-linux-user] Error 2
make: *** Waiting for unfinished jobs....
CC x86_64-linux-user/tcg/tcg-op-vec.o
/root/build-rauc/tmp-glibc/hosttools/ld.bfd: linux-user/syscall.o: in function `do_syscall1':
/root/build-rauc/tmp-glibc/work/x86_64-linux/qemu-native/3.1.1.1-r0/qemu-3.1.1.1/linux-user/syscall.c:7404: undefined reference to `stime'
collect2: error: ld returned 1 exit status
make[1]: *** [Makefile:199: qemu-i386] Error 1
make: *** [Makefile:483: subdir-i386-linux-user] Error 2
CC x86_64-linux-user/tcg/tcg-op-gvec.o
/root/build-rauc/tmp-glibc/hosttools/ld.bfd: linux-user/syscall.o: in function `do_syscall1':
/root/build-rauc/tmp-glibc/work/x86_64-linux/qemu-native/3.1.1.1-r0/qemu-3.1.1.1/linux-user/syscall.c:7404: undefined reference to `stime'
collect2: error: ld returned 1 exit status
make[1]: *** [Makefile:199: qemu-sh4] Error 1
make: *** [Makefile:483: subdir-sh4-linux-user] Error 2
CC x86_64-linux-user/tcg/tcg-common.o
/root/build-rauc/tmp-glibc/hosttools/ld.bfd: linux-user/syscall.o: in function `do_syscall1':
/root/build-rauc/tmp-glibc/work/x86_64-linux/qemu-native/3.1.1.1-r0/qemu-3.1.1.1/linux-user/syscall.c:7404: undefined reference to `stime'
collect2: error: ld returned 1 exit status
make[1]: *** [Makefile:199: qemu-ppc] Error 1
make: *** [Makefile:483: subdir-ppc-linux-user] Error 2
CC x86_64-linux-user/tcg/optimize.o
/root/build-rauc/tmp-glibc/hosttools/ld.bfd: linux-user/syscall.o: in function `do_syscall1':
/root/build-rauc/tmp-glibc/work/x86_64-linux/qemu-native/3.1.1.1-r0/qemu-3.1.1.1/linux-user/syscall.c:7404: undefined reference to `stime'
collect2: error: ld returned 1 exit status
make[1]: *** [Makefile:199: qemu-mipsel] Error 1
make: *** [Makefile:483: subdir-mipsel-linux-user] Error 2
CC x86_64-linux-user/fpu/softfloat.o
/root/build-rauc/tmp-glibc/hosttools/ld.bfd: linux-user/syscall.o: in function `do_syscall1':
/root/build-rauc/tmp-glibc/work/x86_64-linux/qemu-native/3.1.1.1-r0/qemu-3.1.1.1/linux-user/syscall.c:7404: undefined reference to `stime'
collect2: error: ld returned 1 exit status
make[1]: *** [Makefile:199: qemu-mips] Error 1
make: *** [Makefile:483: subdir-mips-linux-user] Error 2
CC x86_64-linux-user/disas.o
GEN x86_64-linux-user/gdbstub-xml.c
CC x86_64-linux-user/gdbstub.o
CC x86_64-linux-user/thunk.o
CC x86_64-linux-user/accel/stubs/hax-stub.o
CC x86_64-linux-user/accel/stubs/hvf-stub.o
CC x86_64-linux-user/accel/stubs/whpx-stub.o
CC x86_64-linux-user/accel/stubs/kvm-stub.o
CC x86_64-linux-user/accel/tcg/tcg-runtime.o
CC x86_64-linux-user/accel/tcg/tcg-runtime-gvec.o
CC x86_64-linux-user/accel/tcg/cpu-exec.o
CC x86_64-linux-user/accel/tcg/cpu-exec-common.o
CC x86_64-linux-user/accel/tcg/translate-all.o
CC x86_64-linux-user/accel/tcg/translator.o
CC x86_64-linux-user/accel/tcg/user-exec.o
CC x86_64-linux-user/accel/tcg/user-exec-stub.o
CC x86_64-linux-user/linux-user/main.o
CC x86_64-linux-user/linux-user/syscall.o
CC x86_64-linux-user/linux-user/strace.o
CC x86_64-linux-user/linux-user/mmap.o
CC x86_64-linux-user/linux-user/signal.o
CC x86_64-linux-user/linux-user/elfload.o
In file included from /usr/include/string.h:495,
from /root/build-rauc/tmp-glibc/work/x86_64-linux/qemu-native/3.1.1.1-r0/qemu-3.1.1.1/include/qemu/osdep.h:84,
from /root/build-rauc/tmp-glibc/work/x86_64-linux/qemu-native/3.1.1.1-r0/qemu-3.1.1.1/linux-user/elfload.c:2:
In function ‘strncpy’,
inlined from ‘fill_psinfo’ at /root/build-rauc/tmp-glibc/work/x86_64-linux/qemu-native/3.1.1.1-r0/qemu-3.1.1.1/linux-user/elfload.c:3158:12,
inlined from ‘fill_note_info’ at /root/build-rauc/tmp-glibc/work/x86_64-linux/qemu-native/3.1.1.1-r0/qemu-3.1.1.1/linux-user/elfload.c:3340:5,
inlined from ‘elf_core_dump’ at /root/build-rauc/tmp-glibc/work/x86_64-linux/qemu-native/3.1.1.1-r0/qemu-3.1.1.1/linux-user/elfload.c:3489:9:
/usr/include/x86_64-linux-gnu/bits/string_fortified.h:106:10: warning: ‘__builtin_strncpy’ specified bound 16 equals destination size [-Wstringop-truncation]
106 | return __builtin___strncpy_chk (__dest, __src, __len, __bos (__dest));
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
CC x86_64-linux-user/linux-user/linuxload.o
CC x86_64-linux-user/linux-user/uaccess.o
CC x86_64-linux-user/linux-user/uname.o
CCAS x86_64-linux-user/linux-user/safe-syscall.o
CC x86_64-linux-user/linux-user/x86_64/signal.o
CC x86_64-linux-user/linux-user/x86_64/cpu_loop.o
CC x86_64-linux-user/linux-user/exit.o
CC x86_64-linux-user/linux-user/fd-trans.o
CC x86_64-linux-user/target/i386/helper.o
CC x86_64-linux-user/target/i386/cpu.o
CC x86_64-linux-user/target/i386/gdbstub.o
CC x86_64-linux-user/target/i386/xsave_helper.o
CC x86_64-linux-user/target/i386/translate.o
CC x86_64-linux-user/target/i386/bpt_helper.o
CC x86_64-linux-user/target/i386/cc_helper.o
CC x86_64-linux-user/target/i386/excp_helper.o
CC x86_64-linux-user/target/i386/fpu_helper.o
CC x86_64-linux-user/target/i386/int_helper.o
CC x86_64-linux-user/target/i386/mem_helper.o
CC x86_64-linux-user/target/i386/misc_helper.o
CC x86_64-linux-user/target/i386/mpx_helper.o
CC x86_64-linux-user/target/i386/seg_helper.o
CC x86_64-linux-user/target/i386/smm_helper.o
CC x86_64-linux-user/target/i386/svm_helper.o
CC x86_64-linux-user/target/i386/sev-stub.o
GEN trace/generated-helpers.c
CC x86_64-linux-user/trace/control-target.o
CC x86_64-linux-user/gdbstub-xml.o
CC x86_64-linux-user/trace/generated-helpers.o
LINK x86_64-linux-user/qemu-x86_64
ERROR: oe_runmake failed
WARNING: exit code 1 from a shell command.
ERROR: Function failed: do_compile (log file is located at /root/build-rauc/tmp-glibc/work/x86_64-linux/qemu-native/3.1.1.1-r0/temp/log.do_compile.5584)


I am using "Warrior" version due to limitation from other meta-layers. I have read that above issue is fixed in newer versions of Yocto. But how can i fix this in Warrior? Is there any workaround?

Can someone please help me resolve it?

Your help will be much appreciated.

Thanks in advance.
Build error:undefined reference to `stime' on Yocto Warrior

Sourabh Hegde
 

Hello All,

When I execute the bitbake for my custom image recipe I hit the below issue related to "qemu-native/3.1.1.1-r0/qemu-3.1.1.1/linux-user/syscall.c:7404: undefined reference to `stime'".

DEBUG: Executing shell function do_compile
NOTE: make -j 8 LD=ld  AR=ar OBJCOPY=objcopy LDFLAGS=-L/root/build-rauc/tmp-glibc/work/x86_64-linux/qemu-native/3.1.1.1-r0/recipe-sysroot-native/usr/lib                         -L/root/build-rauc/tmp-glibc/work/x86_64-linux/qemu-native/3.1.1.1-r0/recipe-sysroot-native/lib                         -Wl,--enable-new-dtags                         -Wl,-rpath-link,/root/build-rauc/tmp-glibc/work/x86_64-linux/qemu-native/3.1.1.1-r0/recipe-sysroot-native/usr/lib                         -Wl,-rpath-link,/root/build-rauc/tmp-glibc/work/x86_64-linux/qemu-native/3.1.1.1-r0/recipe-sysroot-native/lib                         -Wl,-rpath,/root/build-rauc/tmp-glibc/work/x86_64-linux/qemu-native/3.1.1.1-r0/recipe-sysroot-native/usr/lib                         -Wl,-rpath,/root/build-rauc/tmp-glibc/work/x86_64-linux/qemu-native/3.1.1.1-r0/recipe-sysroot-native/lib                         -Wl,-O1 -fuse-ld=bfd
  LINK    i386-linux-user/qemu-i386
  LINK    mipsel-linux-user/qemu-mipsel
  LINK    arm-linux-user/qemu-arm
  LINK    mips-linux-user/qemu-mips
  LINK    ppc-linux-user/qemu-ppc
  GEN     x86_64-linux-user/config-target.h
  LINK    sh4-linux-user/qemu-sh4
  CC      x86_64-linux-user/exec.o
  CC      x86_64-linux-user/tcg/tcg.o
  CC      x86_64-linux-user/tcg/tcg-op.o
/root/build-rauc/tmp-glibc/hosttools/ld.bfd: linux-user/syscall.o: in function `do_syscall1':
/root/build-rauc/tmp-glibc/work/x86_64-linux/qemu-native/3.1.1.1-r0/qemu-3.1.1.1/linux-user/syscall.c:7404: undefined reference to `stime'
collect2: error: ld returned 1 exit status
make[1]: *** [Makefile:199: qemu-arm] Error 1
make: *** [Makefile:483: subdir-arm-linux-user] Error 2
make: *** Waiting for unfinished jobs....
  CC      x86_64-linux-user/tcg/tcg-op-vec.o
/root/build-rauc/tmp-glibc/hosttools/ld.bfd: linux-user/syscall.o: in function `do_syscall1':
/root/build-rauc/tmp-glibc/work/x86_64-linux/qemu-native/3.1.1.1-r0/qemu-3.1.1.1/linux-user/syscall.c:7404: undefined reference to `stime'
collect2: error: ld returned 1 exit status
make[1]: *** [Makefile:199: qemu-i386] Error 1
make: *** [Makefile:483: subdir-i386-linux-user] Error 2
  CC      x86_64-linux-user/tcg/tcg-op-gvec.o
/root/build-rauc/tmp-glibc/hosttools/ld.bfd: linux-user/syscall.o: in function `do_syscall1':
/root/build-rauc/tmp-glibc/work/x86_64-linux/qemu-native/3.1.1.1-r0/qemu-3.1.1.1/linux-user/syscall.c:7404: undefined reference to `stime'
collect2: error: ld returned 1 exit status
make[1]: *** [Makefile:199: qemu-sh4] Error 1
make: *** [Makefile:483: subdir-sh4-linux-user] Error 2
  CC      x86_64-linux-user/tcg/tcg-common.o
/root/build-rauc/tmp-glibc/hosttools/ld.bfd: linux-user/syscall.o: in function `do_syscall1':
/root/build-rauc/tmp-glibc/work/x86_64-linux/qemu-native/3.1.1.1-r0/qemu-3.1.1.1/linux-user/syscall.c:7404: undefined reference to `stime'
collect2: error: ld returned 1 exit status
make[1]: *** [Makefile:199: qemu-ppc] Error 1
make: *** [Makefile:483: subdir-ppc-linux-user] Error 2
  CC      x86_64-linux-user/tcg/optimize.o
/root/build-rauc/tmp-glibc/hosttools/ld.bfd: linux-user/syscall.o: in function `do_syscall1':
/root/build-rauc/tmp-glibc/work/x86_64-linux/qemu-native/3.1.1.1-r0/qemu-3.1.1.1/linux-user/syscall.c:7404: undefined reference to `stime'
collect2: error: ld returned 1 exit status
make[1]: *** [Makefile:199: qemu-mipsel] Error 1
make: *** [Makefile:483: subdir-mipsel-linux-user] Error 2
  CC      x86_64-linux-user/fpu/softfloat.o
/root/build-rauc/tmp-glibc/hosttools/ld.bfd: linux-user/syscall.o: in function `do_syscall1':
/root/build-rauc/tmp-glibc/work/x86_64-linux/qemu-native/3.1.1.1-r0/qemu-3.1.1.1/linux-user/syscall.c:7404: undefined reference to `stime'
collect2: error: ld returned 1 exit status
make[1]: *** [Makefile:199: qemu-mips] Error 1
make: *** [Makefile:483: subdir-mips-linux-user] Error 2
  CC      x86_64-linux-user/disas.o
  GEN     x86_64-linux-user/gdbstub-xml.c
  CC      x86_64-linux-user/gdbstub.o
  CC      x86_64-linux-user/thunk.o
  CC      x86_64-linux-user/accel/stubs/hax-stub.o
  CC      x86_64-linux-user/accel/stubs/hvf-stub.o
  CC      x86_64-linux-user/accel/stubs/whpx-stub.o
  CC      x86_64-linux-user/accel/stubs/kvm-stub.o
  CC      x86_64-linux-user/accel/tcg/tcg-runtime.o
  CC      x86_64-linux-user/accel/tcg/tcg-runtime-gvec.o
  CC      x86_64-linux-user/accel/tcg/cpu-exec.o
  CC      x86_64-linux-user/accel/tcg/cpu-exec-common.o
  CC      x86_64-linux-user/accel/tcg/translate-all.o
  CC      x86_64-linux-user/accel/tcg/translator.o
  CC      x86_64-linux-user/accel/tcg/user-exec.o
  CC      x86_64-linux-user/accel/tcg/user-exec-stub.o
  CC      x86_64-linux-user/linux-user/main.o
  CC      x86_64-linux-user/linux-user/syscall.o
  CC      x86_64-linux-user/linux-user/strace.o
  CC      x86_64-linux-user/linux-user/mmap.o
  CC      x86_64-linux-user/linux-user/signal.o
  CC      x86_64-linux-user/linux-user/elfload.o
In file included from /usr/include/string.h:495,
                 from /root/build-rauc/tmp-glibc/work/x86_64-linux/qemu-native/3.1.1.1-r0/qemu-3.1.1.1/include/qemu/osdep.h:84,
                 from /root/build-rauc/tmp-glibc/work/x86_64-linux/qemu-native/3.1.1.1-r0/qemu-3.1.1.1/linux-user/elfload.c:2:
In function ‘strncpy’,
    inlined from ‘fill_psinfo’ at /root/build-rauc/tmp-glibc/work/x86_64-linux/qemu-native/3.1.1.1-r0/qemu-3.1.1.1/linux-user/elfload.c:3158:12,
    inlined from ‘fill_note_info’ at /root/build-rauc/tmp-glibc/work/x86_64-linux/qemu-native/3.1.1.1-r0/qemu-3.1.1.1/linux-user/elfload.c:3340:5,
    inlined from ‘elf_core_dump’ at /root/build-rauc/tmp-glibc/work/x86_64-linux/qemu-native/3.1.1.1-r0/qemu-3.1.1.1/linux-user/elfload.c:3489:9:
/usr/include/x86_64-linux-gnu/bits/string_fortified.h:106:10: warning: ‘__builtin_strncpy’ specified bound 16 equals destination size [-Wstringop-truncation]
  106 |   return __builtin___strncpy_chk (__dest, __src, __len, __bos (__dest));
      |          ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  CC      x86_64-linux-user/linux-user/linuxload.o
  CC      x86_64-linux-user/linux-user/uaccess.o
  CC      x86_64-linux-user/linux-user/uname.o
  CCAS    x86_64-linux-user/linux-user/safe-syscall.o
  CC      x86_64-linux-user/linux-user/x86_64/signal.o
  CC      x86_64-linux-user/linux-user/x86_64/cpu_loop.o
  CC      x86_64-linux-user/linux-user/exit.o
  CC      x86_64-linux-user/linux-user/fd-trans.o
  CC      x86_64-linux-user/target/i386/helper.o
  CC      x86_64-linux-user/target/i386/cpu.o
  CC      x86_64-linux-user/target/i386/gdbstub.o
  CC      x86_64-linux-user/target/i386/xsave_helper.o
  CC      x86_64-linux-user/target/i386/translate.o
  CC      x86_64-linux-user/target/i386/bpt_helper.o
  CC      x86_64-linux-user/target/i386/cc_helper.o
  CC      x86_64-linux-user/target/i386/excp_helper.o
  CC      x86_64-linux-user/target/i386/fpu_helper.o
  CC      x86_64-linux-user/target/i386/int_helper.o
  CC      x86_64-linux-user/target/i386/mem_helper.o
  CC      x86_64-linux-user/target/i386/misc_helper.o
  CC      x86_64-linux-user/target/i386/mpx_helper.o
  CC      x86_64-linux-user/target/i386/seg_helper.o
  CC      x86_64-linux-user/target/i386/smm_helper.o
  CC      x86_64-linux-user/target/i386/svm_helper.o
  CC      x86_64-linux-user/target/i386/sev-stub.o
  GEN     trace/generated-helpers.c
  CC      x86_64-linux-user/trace/control-target.o
  CC      x86_64-linux-user/gdbstub-xml.o
  CC      x86_64-linux-user/trace/generated-helpers.o
  LINK    x86_64-linux-user/qemu-x86_64
ERROR: oe_runmake failed
WARNING: exit code 1 from a shell command.
ERROR: Function failed: do_compile (log file is located at /root/build-rauc/tmp-glibc/work/x86_64-linux/qemu-native/3.1.1.1-r0/temp/log.do_compile.5584)


I am using "Warrior" version due to limitation from other meta-layers. I have read that above issue is fixed in newer versions of Yocto. But how can i fix this in Warrior? Is there any workaround?

Can someone please help me resolve it?

Your help will be much appreciated.

Thanks in advance.
IGC build issue with devtoolset-8 (GNU 8.3.1)

Monsees, Steven C (US)
 

 

I am building zeus with basic OpenCL support for centos 7.x, and using GNU 8.3.1 compiler and see the following Error when IGC is built, I see the same error when building with GNU 5.3.1…

 

Is this a known issue, is a patch available ?

Any ideas why I might be seeing this ?

 

cpp.o -MF IGC/Compiler/CMakeFiles/Compiler.dir/CISACodeGen/DebugInfo.cpp.o.d -o IGC/Compiler/CMakeFiles/Compiler.dir/CISACodeGen/DebugInfo.cpp.o -c /disk0/scratch/yocto_user/yocto/workspace_zeus/builds/sbcb-default/tmp/work/x86_64-linux/intel-graphics-compiler-native/1.0.11-r0/git/IGC/Compiler/CISACodeGen/DebugInfo.cpp

| In file included from /usr/include/sys/stat.h:106,

|                  from /disk0/scratch/yocto_user/yocto/workspace_zeus/builds/sbcb-default/tmp/work/x86_64-linux/intel-graphics-compiler-native/1.0.11-r0/git/IGC/../3d/common/iStdLib/File.h:47,

|                  from /disk0/scratch/yocto_user/yocto/workspace_zeus/builds/sbcb-default/tmp/work/x86_64-linux/intel-graphics-compiler-native/1.0.11-r0/git/IGC/Compiler/CISACodeGen/DebugInfo.hpp:42,

|                  from /disk0/scratch/yocto_user/yocto/workspace_zeus/builds/sbcb-default/tmp/work/x86_64-linux/intel-graphics-compiler-native/1.0.11-r0/git/IGC/Compiler/CISACodeGen/DebugInfo.cpp:26:

| /usr/include/bits/stat.h:106:31: error: expected unqualified-id before ‘[’ token

|      __syscall_slong_t __unused[3];

|                                ^

| /usr/include/bits/stat.h:164:31: error: expected unqualified-id before ‘[’ token

|      __syscall_slong_t __unused[3];

|             

 

I am using bitbake –k, and everything else builds correctly, and no other components references this…

 

If I modify the header like so:

 

/usr/include/bits>diff stat.h stat.h_HOLD

106c106,108

<     __syscall_slong_t __unused[3];

---

>     __syscall_slong_t __unused1;

>     __syscall_slong_t __unused2;

>     __syscall_slong_t __unused3;

164c166,168

<     __syscall_slong_t __unused[3];

---

>     __syscall_slong_t __unused1;

>     __syscall_slong_t __unused2;

>     __syscall_slong_t __unused3;

08:29 smonsees@yix465383 /usr/include/bits>

 

IGC builds clean, and test show it appears to working correctly…

 

I really shouldn’t be modifying the header, and would like to know what the real issue issue is…

 

Thanks,

Steve
Re: Fetch private gitlab repo using ssh with Yocto recipe #bitbake

Nicolas Jeker
 

On Mon, 2022-01-31 at 02:54 -0800, Sourabh Hegde wrote:
Hello @Nicolas @Erik @Khem,
Hi!

Update from my side:

After following some discussion from other posts, I added "config"
file.
I think you're starting to mix various things together, you should
maybe try to not do everything at the same time. I added comments about
what is wrong with your config, but depending on your build
environment, the ssh config is maybe not the best choice.

~/.ssh/config:

Host git.example.com
HostName git.example.com
User git
PreferredAuthentications publickey
IdentityFile ~/.ssh/id_ed25519.pub
# LogLevel DEBUG3
You need to specify the private key with IdentityFile, not the public
key.

Then I did "eval `ssh-agent -s`"

Then doing "ssh-add ~/.ssh/id_ed25519.pub" results in:
Same here, you should be doing "ssh-add ~/.ssh/id_ed25519" (without the
.pub).

@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@         WARNING: UNPROTECTED PRIVATE KEY FILE!          @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
Permissions 0644 for '/root/.ssh/id_ed25519.pub' are too open.
It is required that your private key files are NOT accessible by
others.
This private key will be ignored.

Whereas the permissions are set as:

ls -l -a ~/.ssh

-rw-r--r-- 1 root root  157 Jan 31 10:48 config
-rw------- 1 root root  464 Jan 20 15:26 id_ed25519
-rw-r--r-- 1 root root  109 Jan 20 15:26 id_ed25519.pub
-rw-r--r-- 1 root root  888 Jan 26 08:43 known_hosts
Well, the permissions on id_ed25519 are correct, but you added the
public key as private key in your config / in your ssh-add command,
which doesn't have the required permissions for private keys (because
it's not).

"ssh-agent" is running

ssh-agent
SSH_AUTH_SOCK=/tmp/ssh-lcft54A4nriC/agent.2833; export SSH_AUTH_SOCK;
SSH_AGENT_PID=2834; export SSH_AGENT_PID;
echo Agent pid 2834;

After doing these changes, when I try to "ssh -v git.example.com" to
test the connection before running bitbake, I get

OpenSSH_8.2p1 Ubuntu-4ubuntu0.4, OpenSSL 1.1.1f  31 Mar 2020
debug1: Reading configuration data /root/.ssh/config
debug1: /root/.ssh/config line 1: Applying options for
git.example.com
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 19: include
/etc/ssh/ssh_config.d/*.conf matched no files
debug1: /etc/ssh/ssh_config line 21: Applying options for *
debug1: Connecting to git.example.com [116.203.241.xxx] port 22.
debug1: connect to address 116.203.241.xxx port 22: Connection
refused
ssh: connect to host git.example.com port 22: Connection refused

I don't understand what is the issue here.

@Nicolas Can you please let me know where and how to run below
commands? Do I need to run them every time before fetching from
gitlab?
  -v $SSH_AUTH_SOCK:/ssh.socket \
  -e SSH_AUTH_SOCK=/ssh.socket \
I think you should explain your build environment a bit better, as I
can just guess what you're doing. You should add these parameters when
starting your docker container. For example I use something along these
lines:

docker run -ti --rm -v ~/development/oe-build:/workdir -v
$SSH_AUTH_SOCK:$SSH_AUTH_SOCK -e SSH_AUTH_SOCK="$SSH_AUTH_SOCK"
crops/poky --workdir=/workdir

If you're forwarding the ssh agent like this, you don't need a key or
config file at all, only known_hosts.


On the other hand, if you're using e.g. GitLab pipelines with docker,
you should not do it like mentioned above, but follow their guide [1].

[1]:
https://docs.gitlab.com/ee/ci/ssh_keys/index.html#ssh-keys-when-using-the-docker-executor

And also I already have "known_hosts" file with matching entries for
key/agent pair.

Can you please let me know how to make this working?

Your help will be much appreciated.

Thanks in advance.
Yocto Project Status WW05`22

Stephen Jolley
 

Current Dev Position: YP 3.5 M3

Next Deadline: 21th Feb. 2022 YP 3.5 M3 build

 

Next Team Meetings:

 

Key Status/Updates:

  • YP 3.5 M2 has passed QA with one bug highlighted (14708). Due to vacations in Asia the release, if approved, will be made next week.
  • YP 3.1.14 is ready for QA but the release will also be delayed until next week.
  • A new Patchwork is available at https://patchwork.yoctoproject.org/. This new system is running the up to date mainline code and will receive regular updates. The previous unmaintained fork remains up at https://patchwork.openembedded.org/ to preserve history. We are seeking help updating PatchTest to run with the new version.

Everyone can now sign up for an account on the new system. Patchwork project maintainers please email mhalstead@... to have your access restored.

  • Upstream glibc are now planning to remove prelink support in 2.36. I think we will still want to remove prelink from OE-Core before our next release though, particularly as it is an LTS.
  • An email proposing inclusive language changes for bitbake and OE-Core has been sent to the community for review. The aim is to implement this before M3.
  • We are seeing networking issues during image testing on the centos8/stream8 workers, possibly due to recent changes in the distro. Help with debugging this welcome.
  • We have also realized there is an issue with hash equivalence where the current mechanism will not account for different headers inside the sysroot added through indirect dependencies (e.g. linux-libc-headers via glibc). This means something like rtcwake in util-linux which uses rtc.h can have differing debug symbols due to differing line numbers yet otherwise be identical. There is a potential fix with downsides in master-next.
  • CVE metrics are still under control for master with pending patches accounted for (thanks Ross!) but work still remains on the various stable branches which have high counts.
  • Intermittent issues continue to be at record high levels and help is very much welcome in trying to resolve them. You can see the list of failures we’re continuing to see by searching for the “AB-INT” tag in bugzilla: https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=AB-INT

In particular, we’re struggling to understand the intermittent network issue with external hosts we’re seeing very occasionally.

 

Ways to contribute:

 

YP 3.5 Milestone Dates:

  • YP 3.5 M2 is out of QA
  • YP 3.5 M3 build date 2022/02/21
  • YP 3.5 M3 Release date 2022/03/04
  • YP 3.5 M4 build date 2022/04/04
  • YP 3.5 M4 Release date 2022/04/29

 

Upcoming dot releases:

  • YP 3.1.14 is built
  • YP 3.1.14 Release date 2022/02/04
  • YP 3.4.2 build date 2022/02/07
  • YP 3.4.2 Release date 2022/02/18
  • YP 3.3.5 build date 2022/02/14
  • YP 3.3.5 Release date 2022/02/25
  • YP 3.1.15 build date 2022/03/14
  • YP 3.1.15 Release date 2022/03/25
  • YP 3.4.3 build date 2022/03/21
  • YP 3.4.3 Release date 2022/04/01
  • YP 3.3.6 build date 2022/03/28
  • YP 3.3.6 Release date 2022/04/08
  • YP 3.1.16 build date 2022/04/25
  • YP 3.1.16 Release date 2022/05/06

 

Tracking Metrics:

 

The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:

https://wiki.yoctoproject.org/wiki/TSC

 

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!]

 

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

(    Cell:                (208) 244-4460

* Email:              sjolley.yp.pm@...

 
Re: [meta-lts-mixins][dunfell/go PATCH 1/4] Initial commit: add license, readme and layer config.

Alexander Kanavin
 

On Thu, 27 Jan 2022 at 21:06, Denys Dmytriyenko <denis@...> wrote:
On Thu, Jan 27, 2022 at 06:07:06PM +0100, Alexander Kanavin wrote:
> A question specifically to Denys, how can I actually get this into the
> mixin repo, and have commit rights to the branch? We've tested this quite
> well in private, and there are further enhancements coming up.

Michael,

Would it be possible to create 2 additional branches in the meta-lts-mixins
repository at https://git.yoctoproject.org/meta-lts-mixins/ called
"dunfell/go" and also "dunfell/docker" and give Alex push rights to them?

Please let us know, thanks a lot!

Ping, please :)

Alex
Re: Additional hardening options

Robert Berger
 

Hi,

This[1] is what I usually add as well to the security flags.

With respect to the "default" flags I had some fun with the SDK and -D_FORTIFY_SOURCE=2 and -fstack-protector-strong.

I guess they do have some performance impact as well, but I did not do very thorough research.

Also, I did not confirm it yet but suspect that some of those flags might be the reason for "debuginfod gdb: *** stack smashing detected ***: terminated".[2]

[1] https://gitlab.com/meta-layers/meta-resy/-/blob/master/conf/distro/include/more_security_flags.inc

[2] https://bugzilla.yoctoproject.org/show_bug.cgi?id=14570

Regards,

Robert
Re: Additional hardening options

Richard Purdie
 

On Wed, 2022-01-26 at 14:39 +1300, Paul Eggleton wrote:
Hi folks

I've been looking into a couple of compiler flags for hardening that I think we
might want to consider enabling by default in security-flags.inc:


1) -fstack-clash-protection

This option was introduced to gcc 8.x and provides protection against the
stack clash vulnerability:

https://securingsoftware.blogspot.com/2017/12/stack-clash-vulnerability.html

It has been enabled in some Linux distributions already (e.g. Ubuntu, Fedora).


2) -z noexecstack (or alternative mitigations)

gcc will enable an executable stack under a few different circumstances - see
here for details

https://wiki.gentoo.org/wiki/Hardened/GNU_stack_quickstart

I've written a check that we could add to insane.bbclass that warns/errors on
binaries with an executable stack. Does this seem reasonable to have?
The other possibility is we add -Wl,-z,noexecstack to LDFLAGS and then see
what breaks, but unfortunately issues are likely only going to show up when
the program crashes at runtime, and also it will stop the aforementioned check
from working.


Any opinions?
These seem like reasonable things to do, are there any downsides to them?

I'd be happy to test some patches, see if they do cause issues...

Cheers,

Richard
M+ & H bugs with Milestone Movements WW05

Stephen Jolley
 

All,

YP M+ or high bugs which moved to a new milestone in WW05 are listed below:

Priority

Bug ID

Short Description

Changer

Owner

Was

Became

Medium+

12368

persistent bitbake server does not re-parse if previous build was ctrl+C'd

richard.purdie@...

richard.purdie@...

3.5 M2

3.5 M3

 

12723

mysql requires unicode and char length filtering

david.reyna@...

david.reyna@...

3.5 M2

3.5 M3

 

13103

[Bug][QA 2.7 M1 rc1][Toaster] "Recipes" table  and  "machines" table are not getting populated after clicking on imported layer as well as after clicking Machines Tab on project page

david.reyna@...

david.reyna@...

3.5 M2

3.5 M3

 

13123

package.PackageTests.test_gdb_hardlink_debug failed

randy.macleod@...

randy.macleod@...

3.5 M2

3.5 M3

 

13278

If git protocol doesn't work, you get a tar.gz clone from PREMIRROR which has git protocol origin

richard.purdie@...

richard.purdie@...

3.5 M2

3.5 M3

 

13424

devupstream doesn't work with mutilib

richard.purdie@...

richard.purdie@...

3.5 M2

3.5 M3

 

13599

Enhancement: Detect variables that shouldn't be defined in image scope, but in global (distro) scope

richard.purdie@...

richard.purdie@...

3.5 M2

3.5 M3

 

13888

Toaster is not starting for Django-3

david.reyna@...

david.reyna@...

3.5 M2

3.5 M3

 

13908

segfault in mb-wm on qemux86-64 intermittently

randy.macleod@...

ross@...

3.5 M2

3.5 M3

 

14085

Toaster UI should know when bitbake crashed

david.reyna@...

david.reyna@...

3.5 M2

3.5 M3

 

14156

fetch/gitsm: submodules are fetched as mirrored and not working as expected

richard.purdie@...

richard.purdie@...

3.5 M2

3.5 M3

 

14163

AB-INT PTEST ARM: libevent arm ptest intermittent failure

randy.macleod@...

ross@...

3.5 M2

3.5 M3

 

14165

AB-INT PTEST: strace ptest intermittent failure in qual_fault-syscall.test

randy.macleod@...

randy.macleod@...

3.5 M2

3.5 M3

 

14311

AB-INT PTEST: valgrind drd/tests ptest intermittent failure

randy.macleod@...

yf3yu@...

3.5 M2

3.5 M3

 

14381

AB-INT PTEST ARM: openssl ptest intermittent failure

randy.macleod@...

ross@...

3.5 M2

3.5 M3

 

14385

mode of sstate files created under pseudo

richard.purdie@...

richard.purdie@...

3.5 M2

3.5 M3

 

14388

AB-INT PTEST: valgrind failed  helgrind/tests/hg05_race2

randy.macleod@...

randy.macleod@...

3.5 M2

3.5 M3

 

14486

qemu rootfs copy is taking too much time

randy.macleod@...

randy.macleod@...

3.5 M2

3.5 M3

 

14522

qemuppc doesn't shutdown within timeout (serial console issues)

randy.macleod@...

sakib.sajal@...

3.5 M2

3.5 M3

 

14560

AB-INT PTEST ARM: tcl timer.test failure

randy.macleod@...

ross@...

3.5 M2

3.5 M4

 

14556

Running dates tests in systemd images causes loss of networking

randy.macleod@...

ross@...

3.5 M2

3.5 M4

 

14564

parselogs.ParseLogsTest.test_parselogs udev failure

randy.macleod@...

trevor.gamblin@...

3.5 M2

3.5 M3

 

14596

AB-INT PTEST ARM: strace ptest intermittent failure in strace-T.test

randy.macleod@...

ross@...

3.5 M2

3.5 M3

 

14611

qemuarm64 testimage Target didn't reach login banner

randy.macleod@...

randy.macleod@...

3.5 M2

3.5 M4

 

14620

QA error not seen when reusing SSTATE

richard.purdie@...

richard.purdie@...

3.5 M2

3.5 M3

 

14655

AB-INT: SDK preparation failure: SState: cannot test file://[...]

randy.macleod@...

mhalstead@...

3.5 M2

3.5 M3

 

14656

a wine server seems to be running, but I cannot connect to itcore-image-mingw-sdktest do_testsdk failure:

randy.macleod@...

JPEWhacker@...

3.5 M2

3.5 M4

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

(    Cell:                (208) 244-4460

* Email:              sjolley.yp.pm@...

 
Enhancements/Bugs closed WW05!

Stephen Jolley
 

All,

 

The below were the owners of enhancements or bugs closed during the last week!

Who

Count

mhalstead@...

1

trevor.gamblin@...

1

randy.macleod@...

1

richard.purdie@...

1

Grand Total

4

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

(    Cell:                (208) 244-4460

* Email:              sjolley.yp.pm@...

 
Current high bug count owners for Yocto Project 3.5

Stephen Jolley
 

All,

 

Below is the list as of top 44 bug owners as of the end of WW05 of who have open medium or higher bugs and enhancements against YP 3.5.   There are 62 possible work days left until the final release candidates for YP 3.5 needs to be released.

Who

Count

ross@...

38

michael.opdenacker@...

35

randy.macleod@...

25

david.reyna@...

22

bruce.ashfield@...

17

sakib.sajal@...

13

tim.orling@...

13

trevor.gamblin@...

12

richard.purdie@...

10

mhalstead@...

9

kai.kang@...

7

bluelightning@...

6

saul.wold@...

6

JPEWhacker@...

4

hongxu.jia@...

4

chee.yang.lee@...

4

Qi.Chen@...

3

jon.mason@...

3

alejandro@...

3

kiran.surendran@...

2

alexandre.belloni@...

2

pokylinux@...

2

raj.khem@...

2

mshah@...

2

pgowda.cve@...

2

shachar@...

1

yf3yu@...

1

open.source@...

1

mark.hatle@...

1

nicolas.dechesne@...

1

yoctoproject@...

1

john.kaldas.enpj@...

1

jay.shen.teoh@...

1

kexin.hao@...

1

akuster808@...

1

thomas.perrot@...

1

Martin.Jansa@...

1

liezhi.yang@...

1

aehs29@...

1

TicoTimo@...

1

matthewzmd@...

1

mingli.yu@...

1

yi.zhao@...

1

mostthingsweb@...

1

Grand Total

265

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

(    Cell:                (208) 244-4460

* Email:              sjolley.yp.pm@...

 
Yocto Project Newcomer & Unassigned Bugs - Help Needed

Stephen Jolley
 

All,

 

The triage team is starting to try and collect up and classify bugs which a newcomer to the project would be able to work on in a way which means people can find them. They're being listed on the triage page under the appropriate heading:

https://wiki.yoctoproject.org/wiki/Bug_Triage#Newcomer_Bugs  Also please review: https://www.openembedded.org/wiki/How_to_submit_a_patch_to_OpenEmbedded and how to create a bugzilla account at: https://bugzilla.yoctoproject.org/createaccount.cgi

The idea is these bugs should be straight forward for a person to help work on who doesn't have deep experience with the project.  If anyone can help, please take ownership of the bug and send patches!  If anyone needs help/advice there are people on irc who can likely do so, or some of the more experienced contributors will likely be happy to help too.

 

Also, the triage team meets weekly and does its best to handle the bugs reported into the Bugzilla. The number of people attending that meeting has fallen, as have the number of people available to help fix bugs. One of the things we hear users report is they don't know how to help. We (the triage team) are therefore going to start reporting out the currently 398 unassigned or newcomer bugs.

 

We're hoping people may be able to spare some time now and again to help out with these.  Bugs are split into two types, "true bugs" where things don't work as they should and "enhancements" which are features we'd want to add to the system.  There are also roughly four different "priority" classes right now,  “3.5, “3.6”, "3.99" and "Future", the more pressing/urgent issues being in "3.4" and then “3.5”.

 

Please review this link and if a bug is something you would be able to help with either take ownership of the bug, or send me (sjolley.yp.pm@...) an e-mail with the bug number you would like and I will assign it to you (please make sure you have a Bugzilla account).  The list is at: https://wiki.yoctoproject.org/wiki/Bug_Triage_Archive#Unassigned_or_Newcomer_Bugs

 

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

(    Cell:                (208) 244-4460

* Email:              sjolley.yp.pm@...

 
Yocto Project Status WW05`22

Stephen Jolley
 

Current Dev Position: YP 3.5 M3

Next Deadline: 21th Feb. 2022 YP 3.5 M3 build

 

Next Team Meetings:

 

Key Status/Updates:

  • YP 3.5 M2 has passed QA with one bug highlighted (14708). Due to vacations in Asia the release, if approved, will be made next week.
  • YP 3.1.14 is ready for QA but the release will also be delayed until next week.
  • Upstream glibc are now planning to remove prelink support in 2.36. I think we will still want to remove prelink from OE-Core before our next release though, particularly as it is an LTS.
  • An email proposing inclusive language changes for bitbake and OE-Core has been sent to the community for review. The aim is to implement this before M3.
  • We are seeing networking issues during image testing on the centos8/stream8 workers, possibly due to recent changes in the distro. Help with debugging this welcome.
  • We have also realized there is an issue with hash equivalence where the current mechanism will not account for different headers inside the sysroot added through indirect dependencies (e.g. linux-libc-headers via glibc). This means something like rtcwake in util-linux which uses rtc.h can have differing debug symbols due to differing line numbers yet otherwise be identical. There is a potential fix with downsides in master-next.
  • CVE metrics are still under control for master with pending patches accounted for (thanks Ross!) but work still remains on the various stable branches which have high counts.
  • Intermittent issues continue to be at record high levels and help is very much welcome in trying to resolve them. You can see the list of failures we’re continuing to see by searching for the “AB-INT” tag in bugzilla: https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=AB-INT

In particular, we’re struggling to understand the intermittent network issue with external hosts we’re seeing very occasionally.

 

Ways to contribute:

 

YP 3.5 Milestone Dates:

  • YP 3.5 M2 is out of QA
  • YP 3.5 M3 build date 2022/02/21
  • YP 3.5 M3 Release date 2022/03/04
  • YP 3.5 M4 build date 2022/04/04
  • YP 3.5 M4 Release date 2022/04/29

 

Upcoming dot releases:

  • YP 3.1.14 is built
  • YP 3.1.14 Release date 2022/02/04
  • YP 3.4.2 build date 2022/02/07
  • YP 3.4.2 Release date 2022/02/18
  • YP 3.3.5 build date 2022/02/14
  • YP 3.3.5 Release date 2022/02/25
  • YP 3.1.15 build date 2022/03/14
  • YP 3.1.15 Release date 2022/03/25
  • YP 3.4.3 build date 2022/03/21
  • YP 3.4.3 Release date 2022/04/01
  • YP 3.3.6 build date 2022/03/28
  • YP 3.3.6 Release date 2022/04/08
  • YP 3.1.16 build date 2022/04/25
  • YP 3.1.16 Release date 2022/05/06

 

Tracking Metrics:

 

The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:

https://wiki.yoctoproject.org/wiki/TSC

 

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!]

 

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

(    Cell:                (208) 244-4460

* Email:              sjolley.yp.pm@...

 
Reminder: Yocto Project Technical Team Meeting @ Monthly from 8am on the first Tuesday (PDT)

Stephen Jolley
 

All,

 

Just a reminder we will hold the monthly Yocto Project Technical Meeting at 8am PST tomorrow. (2/1) 

 

Yocto Project Technical Team Meeting: We encourage people attending the meeting to logon and announce themselves on the Yocto Project IRC chancel during the meeting (optional):

Yocto IRC: https://web.libera.chat/#yocto 

Wiki: https://www.yoctoproject.org/public-virtual-meetings/

 

When            Monthly from 8am to 9am on the first Tuesday Pacific Time

Where           Zoom Meeting: https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09

 

We are tracking the minutes at: https://docs.google.com/document/d/1ly8nyhO14kDNnFcW2QskANXW3ZT7QwKC5wWVDg9dDH4/edit?pli=1 Please request access if you want to assist in editing them.  The world should have view access.

 

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

(    Cell:                (208) 244-4460

* Email:              sjolley.yp.pm@...

 
QA notification for completed autobuilder build (yocto-3.1.14.rc1)

Richard Purdie
 

A build flagged for QA (yocto-3.1.14.rc1) was completed on the autobuilder and
is available at:


https://autobuilder.yocto.io/pub/releases/yocto-3.1.14.rc1


Build hash information:

bitbake: be6ecc160ac4a8d9715257b9b955363cecc081ea
meta-agl: 7a644d636237459c54128a71d083cb6f9e1b8e60
meta-arm: ce535dfb96de4d2529f091d7d85a7172c626001c
meta-aws: 9979cfa676105cb68cfadfdaeabf044d7c919319
meta-gplv2: 60b251c25ba87e946a0ca4cdc8d17b1cb09292ac
meta-intel: 87984115eb6ed1a4c17204629dcb100f6b76fe82
meta-mingw: 524de686205b5d6736661d4532f5f98fee8589b7
meta-openembedded: ab9fca485e13f6f2f9761e1d2810f87c2e4f060a
oecore: f3be01483b01c88f8c4ba24ca73ccf1bcc33665c
poky: bba323389749ec3e306509f8fb12649f031be152



This is an automated message from the Yocto Project Autobuilder
Git: git://git.yoctoproject.org/yocto-autobuilder2
Email: richard.purdie@linuxfoundation.org
Re: How to prevent auto start of matchbox-terminal at boot?

Dave Beal
 

Thanks, Alex!  That was it.  The script that started the matchbox-terminal is /usr/bin/mini-x-session.  I just edited this file and commented out the terminal line and another line that was setting my display to an incorrect resolution.
Where setup KCONF_AUDIT_LEVEL value

Mauro Ziliani
 

Hi all.

The KCONF_AUDIT_LEVEL variable must be setup in a .conf file or I can change it in a recipe?


I try to understand why my file defconfig is not used my kernel configurator


MZ
1061 - 1080 of 57064