[yocto] owner and group of sysroots changed to nobdoy #bitbake #kirkstone

2023-07-21 Thread yong . 9 . wang
Hi,  experts

I'm moving my bb recipe to kirkstone but met a problem which causing ssh 
operation in bb recipe failed.  after some investigation I found out that the 
owner and group of the sysroots accessing in the bb recipes were all changed to 
nobody.  below is the shell commands run in the bb recipes and error log.  So 
I'm curious how this owner and group changed and how to fix it?

> 
> 
> 
> check_gerrit_authentication() {
> 
> 
> 
> ls -ld /*
> 
> 
> 
> if ! ssh -o BatchMode=yes -p 29418 gerrit-essl2.int.net.nokia.com gerrit
> version; then
> 
> 
> 
> bberror "SSH connection to Gerrit failed.\n\n\
> 
> 
> 
> Please check that your public key is installed and Gerrit host is in your
> known_hosts file.\n\
> 
> 
> 
> To check the connection:\n\
> 
> 
> 
> $ ssh -p 29418 gerrit-essl2.int.net.nokia.com\n"
> 
> 
> 
> exit 1
> 
> 
> 
> fi
> 
> 
> 
> }
> 
> 

and the output :

> 
> 
> 
> DEBUG: Executing shell function check_gerrit_authentication
> 
> 
> 
> lrwxrwxrwx   1 nobody nobody       7 Jan 28  2020 /bin -> usr/bin
> 
> 
> 
> dr-xr-xr-x   2 nobody nobody       6 Jan 28  2020 /boot
> 
> 
> 
> drwxr-xr-x   5 nobody nobody     360 Jul 21 07:44 /dev
> 
> 
> 
> drwxr-xr-x   1 *nobody nobody* 139 Jul 21 07:44 /etc
> 
> 
> 
> drwxr-xr-x   1 nobody nobody      21 Jul 21 07:44 /home
> 
> 
> 
> drwxr-xr-x   4 nobody nobody      33 Jul 21 07:44 /host
> 
> 
> 
> lrwxrwxrwx   1 nobody nobody       7 Jan 28  2020 /lib -> usr/lib
> 
> 
> 
> lrwxrwxrwx   1 nobody nobody       9 Jan 28  2020 /lib64 -> usr/lib64
> 
> 
> 
> drwx--   2 nobody nobody       6 Apr 27  2021 /lost+found
> 
> 
> 
> drwxr-xr-x  10 nobody nobody    4096 Jun 11 01:56 /make-4.3
> 
> 
> 
> -rw-r--r--   1 nobody nobody 2317073 Jan 19  2020 /make-4.3.tar.gz
> 
> 
> 
> drwxr-xr-x   2 nobody nobody       6 Jan 28  2020 /media
> 
> 
> 
> drwxr-xr-x   2 nobody nobody       6 Jan 28  2020 /mnt
> 
> 
> 
> drwxr-xr-x   1 nobody nobody      22 Jun  1 07:08 /opt
> 
> 
> 
> dr-xr-xr-x 314 nobody nobody       0 Jul 21 07:44 /proc
> 
> 
> 
> dr-xr-x---   1 nobody nobody      58 Jun  1 07:08 /root
> 
> 
> 
> drwxr-xr-x   1 nobody nobody      22 Jun  1 07:08 /run
> 
> 
> 
> lrwxrwxrwx   1 nobody nobody       8 Jan 28  2020 /sbin -> usr/sbin
> 
> 
> 
> drwxr-xr-x   1 nobody nobody      27 Jun 11 01:56 /scripts
> 
> 
> 
> drwxr-xr-x   2 nobody nobody       6 Jan 28  2020 /srv
> 
> 
> 
> dr-xr-xr-x  12 nobody nobody       0 Jul 21 08:18 /sys
> 
> 
> 
> drwxrwxrwt   2 nobody nobody      40 Jul 21 07:44 /tmp
> 
> 
> 
> drwxr-xr-x   1 nobody nobody      45 Apr 27  2021 /usr
> 
> 
> 
> drwxr-xr-x   1 nobody nobody      30 Jun 11 01:56 /var
> 
> 
> 
> -rw-r--r--   1 nobody nobody      16 Jun 11 01:55 /VERSION
> 
> 
> 
> *Bad owner or permissions on /etc/ssh/ssh_config.d/50-redhat.conf^M*
> 
> 
> 
> ERROR: SSH connection to Gerrit failed.
> 
> 
> 
> 

Best Regards
Yong

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#60631): https://lists.yoctoproject.org/g/yocto/message/60631
Mute This Topic: https://lists.yoctoproject.org/mt/100291025/21656
Mute #bitbake:https://lists.yoctoproject.org/g/yocto/mutehashtag/bitbake
Mute #kirkstone:https://lists.yoctoproject.org/g/yocto/mutehashtag/kirkstone
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [yocto] File magic/sdk relocation

2023-07-21 Thread Oleksandr Hnatiuk via lists.yoctoproject.org
On Mon, Jun 19, 2023 at 08:27 PM, Alexander Kanavin wrote:

> 
> On closer look, it should even say:
> export MAGIC="\$OECORE_NATIVE_SYSROOT/usr/share/misc/magic.mgc"

Hi Alexander,

We have submitted the patch[1] which fixes the build for our case but doesn't 
change the contents of file.sh which is a separate issue.
You suggested changing MAGIC to 
"\$OECORE_NATIVE_SYSROOT/usr/share/misc/magic.mgc".
We can also get the same result with "${datadir}/misc/magic.mgc" which is what 
was used for create_cmdline_wrapper in this recipe.
Which one is preferred?

[1] see "[PATCH] file: return wrapper to fix builds when file is in 
buildtools-tarball" in openembedded-core

Regards,
Oleksandr

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#60630): https://lists.yoctoproject.org/g/yocto/message/60630
Mute This Topic: https://lists.yoctoproject.org/mt/99626082/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [yocto] [meta-raspberrypi][PATCH] rpi-libcamera-apps: fix Illegal Instruction

2023-07-21 Thread Andrei Gherzan
Hi,

On Thu, Jul 20, 2023 at 7:30 PM Vivien Didelot 
wrote:

> With armv8-neon being enforced for all ARM based machines, running
> any libcamera app on raspberrypi (e.g. Raspberry Pi B Rev 2) results
> in Illegal Instruction.
>
> To fix this, defaults to TARGET_ARCH for non-aarch64 machines.
>
> Signed-off-by: Vivien Didelot 
> ---
>  recipes-multimedia/libcamera-apps/rpi-libcamera-apps_git.bb | 1 -
>  1 file changed, 1 deletion(-)
>
> diff --git a/recipes-multimedia/libcamera-apps/rpi-libcamera-apps_git.bb
> b/recipes-multimedia/libcamera-apps/rpi-libcamera-apps_git.bb
> index 062ded9..3460065 100644
> --- a/recipes-multimedia/libcamera-apps/rpi-libcamera-apps_git.bb
> +++ b/recipes-multimedia/libcamera-apps/rpi-libcamera-apps_git.bb
> @@ -30,7 +30,6 @@ EXTRA_OECMAKE = "\
>
>  LIBCAMERA_ARCH = "${TARGET_ARCH}"
>  LIBCAMERA_ARCH:aarch64 = "arm64"
> -LIBCAMERA_ARCH:arm = "armv8-neon"
>  EXTRA_OECMAKE += "-DENABLE_COMPILE_FLAGS_FOR_TARGET=${LIBCAMERA_ARCH}"
>

Thanks for this. It looks good. Would you be able to send it as an MR in
Github so we can CI it as well?

Andrei

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#60629): https://lists.yoctoproject.org/g/yocto/message/60629
Mute This Topic: https://lists.yoctoproject.org/mt/100273523/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



[linux-yocto][yocto-kernel-cache yocto-6.1][PATCH 1/1] nxp-imx8: Enable IMX_OCOTP and IMX_OCOTP_SCU

2023-07-21 Thread Xiaolei Wang via lists.yoctoproject.org
Fec mac addr exists in nvmem and needs to be read by SCU,
so there is a dependency between fec and IMX_OCOTP,
if IMX_OCOTP is disable, this may cause fec loading delay

Signed-off-by: Xiaolei Wang 
---
 bsp/nxp-imx8/nxp-imx8.cfg | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/bsp/nxp-imx8/nxp-imx8.cfg b/bsp/nxp-imx8/nxp-imx8.cfg
index b116ae2d..3bd84d73 100644
--- a/bsp/nxp-imx8/nxp-imx8.cfg
+++ b/bsp/nxp-imx8/nxp-imx8.cfg
@@ -556,6 +556,9 @@ CONFIG_IMX8QXP_ADC=y
 CONFIG_IMX93_ADC=y
 CONFIG_IIO=y
 
+CONFIG_NVMEM_IMX_OCOTP=y
+CONFIG_NVMEM_IMX_OCOTP_SCU=y
+
 #
 # Inertial measurement units
 
-- 
2.25.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#12884): 
https://lists.yoctoproject.org/g/linux-yocto/message/12884
Mute This Topic: https://lists.yoctoproject.org/mt/100273794/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



[yocto] [meta-raspberrypi][PATCH] rpi-libcamera-apps: fix Illegal Instruction

2023-07-21 Thread Vivien Didelot
With armv8-neon being enforced for all ARM based machines, running
any libcamera app on raspberrypi (e.g. Raspberry Pi B Rev 2) results
in Illegal Instruction.

To fix this, defaults to TARGET_ARCH for non-aarch64 machines.

Signed-off-by: Vivien Didelot 
---
 recipes-multimedia/libcamera-apps/rpi-libcamera-apps_git.bb | 1 -
 1 file changed, 1 deletion(-)

diff --git a/recipes-multimedia/libcamera-apps/rpi-libcamera-apps_git.bb 
b/recipes-multimedia/libcamera-apps/rpi-libcamera-apps_git.bb
index 062ded9..3460065 100644
--- a/recipes-multimedia/libcamera-apps/rpi-libcamera-apps_git.bb
+++ b/recipes-multimedia/libcamera-apps/rpi-libcamera-apps_git.bb
@@ -30,7 +30,6 @@ EXTRA_OECMAKE = "\
 
 LIBCAMERA_ARCH = "${TARGET_ARCH}"
 LIBCAMERA_ARCH:aarch64 = "arm64"
-LIBCAMERA_ARCH:arm = "armv8-neon"
 EXTRA_OECMAKE += "-DENABLE_COMPILE_FLAGS_FOR_TARGET=${LIBCAMERA_ARCH}"
 
 PACKAGECONFIG[x11] = "-DENABLE_X11=1,-DENABLE_X11=0"
-- 
2.41.0


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#60628): https://lists.yoctoproject.org/g/yocto/message/60628
Mute This Topic: https://lists.yoctoproject.org/mt/100273523/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



[yocto] [meta-security][PATCH] dm-verity-image-initramfs: Allow compressed image types

2023-07-21 Thread Stephan Wurm
Using  in the depends variable does not work for
compressed image types like squashfs-zst, as the resulting task
dependency still contains the incompatible dash. Replacing the dash by
an underscore resolves this issue.

Signed-off-by: Stephan Wurm 
---
 recipes-core/images/dm-verity-image-initramfs.bb | 9 -
 1 file changed, 8 insertions(+), 1 deletion(-)

diff --git a/recipes-core/images/dm-verity-image-initramfs.bb 
b/recipes-core/images/dm-verity-image-initramfs.bb
index 187aeae..78f7b49 100644
--- a/recipes-core/images/dm-verity-image-initramfs.bb
+++ b/recipes-core/images/dm-verity-image-initramfs.bb
@@ -19,7 +19,14 @@ IMAGE_FEATURES = ""
 IMAGE_LINGUAS = ""
 
 # Can we somehow inspect reverse dependencies to avoid these variables?
-do_image[depends] += "${DM_VERITY_IMAGE}:do_image_${DM_VERITY_IMAGE_TYPE}"
+python __anonymous() {
+verity_image = d.getVar('DM_VERITY_IMAGE')
+verity_type = d.getVar('DM_VERITY_IMAGE_TYPE')
+
+if verity_image and verity_type:
+dep = ' %s:do_image_%s' % (verity_image, verity_type.replace('-', '_'))
+d.appendVarFlag('do_image', 'depends', dep)
+}
 
 # Ensure dm-verity.env is updated also when rebuilding DM_VERITY_IMAGE
 do_image[nostamp] = "1"
-- 
2.34.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#60627): https://lists.yoctoproject.org/g/yocto/message/60627
Mute This Topic: https://lists.yoctoproject.org/mt/99618767/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [yocto] Missing pam_winbind.so while adding Samba(4.10.10-r0)

2023-07-21 Thread Yi Zhao


On 7/21/23 13:06, Poornesh G ( India - Bangalore ) wrote:

Greeetings !

I am trying to include "samba" into my yocto build . I can able to see 
*"pam_winbind.so 
"*  
in 
*"/build/tmp/work/cortexa7t2hf-neon-poky-linux-gnueabi/samba/4.10.10-r0/image/lib/security"* 
folder.
But when I try to include samba into my image , it is absent in my 
Rootfile system . I am adding in "local.conf" file as below :

*
#To enable SAMBA*
*IMAGE_INSTALL_append = " samba samba-client cifs-utils  samba-ad-dc 
samba-base samba-common"

*



It is in package pam-pluginwinbind.  Please install this package.


//Yi


*

*Can anyone help me out to make pam_winbind.so 
 
as a part of my image .


Thanks in advance.




-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#60626): https://lists.yoctoproject.org/g/yocto/message/60626
Mute This Topic: https://lists.yoctoproject.org/mt/100271459/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-