When build a native-sdk on dora/poky/yocoto for an armv5 device the fowllowing host files are ending up in the arm sysroot ./opt/poky/1.5.1/sysroots/x86_64-pokysdk-linux/usr/bin/chsh ./opt/poky/1.5.1/sysroots/x86_64-pokysdk-linux/usr/bin/newgrp ./opt/poky/1.5.1/sysroots/x86_64-pokysdk-linux/usr/bin/passwd ./opt/poky/1.5.1/sysroots/x86_64-pokysdk-linux/usr/bin/opkg ./opt/poky/1.5.1/sysroots/x86_64-pokysdk-linux/usr/bin/chfn ./opt/poky/1.5.1/sysroots/x86_64-pokysdk-linux/usr/bin/groups ./opt/poky/1.5.1/sysroots/x86_64-pokysdk-linux/usr/sbin ./opt/poky/1.5.1/sysroots/x86_64-pokysdk-linux/usr/sbin/chpasswd ./opt/poky/1.5.1/sysroots/x86_64-pokysdk-linux/bin ./opt/poky/1.5.1/sysroots/x86_64-pokysdk-linux/bin/su ./opt/poky/1.5.1/sysroots/x86_64-pokysdk-linux/bin/login ./opt/poky/1.5.1/sysroots/x86_64-pokysdk-linux/etc ./opt/poky/1.5.1/sysroots/x86_64-pokysdk-linux/etc/rcS.d ./opt/poky/1.5.1/sysroots/x86_64-pokysdk-linux/etc/rcS.d/S98run-postinsts ./opt/poky/1.5.1/sysroots/x86_64-pokysdk-linux/sbin ./opt/poky/1.5.1/sysroots/x86_64-pokysdk-linux/sbin/vigr ./opt/poky/1.5.1/sysroots/x86_64-pokysdk-linux/sbin/vipw
How/Why is this a problem ? Size constraints ?
Your ARM5 sysroot should be at location: ./opt/poky/1.5.1/sysroots/*.arm.*-poky-linux/... What you are referencing above is the "nativesdk" sysroot, which should contain only x86_64 binaries. i.e. the cross-compiler and friends.
Hi, sorry I cut and pasted from my email to the mailinglist and omitted the parent dir this gives a better view whats wrong /opt/poky/1.5.1/sysroots# find | grep x86 | less ./armv5te-poky-linux-gnueabi/opt/poky/1.5.1/sysroots/x86_64-pokysdk-linux ./armv5te-poky-linux-gnueabi/opt/poky/1.5.1/sysroots/x86_64-pokysdk-linux/usr ./armv5te-poky-linux-gnueabi/opt/poky/1.5.1/sysroots/x86_64-pokysdk-linux/usr/bin ./armv5te-poky-linux-gnueabi/opt/poky/1.5.1/sysroots/x86_64-pokysdk-linux/usr/bin/chsh ./armv5te-poky-linux-gnueabi/opt/poky/1.5.1/sysroots/x86_64-pokysdk-linux/usr/bin/newgrp ./armv5te-poky-linux-gnueabi/opt/poky/1.5.1/sysroots/x86_64-pokysdk-linux/usr/bin/passwd ./armv5te-poky-linux-gnueabi/opt/poky/1.5.1/sysroots/x86_64-pokysdk-linux/usr/bin/opkg ./armv5te-poky-linux-gnueabi/opt/poky/1.5.1/sysroots/x86_64-pokysdk-linux/usr/bin/chfn ./armv5te-poky-linux-gnueabi/opt/poky/1.5.1/sysroots/x86_64-pokysdk-linux/usr/bin/groups ./armv5te-poky-linux-gnueabi/opt/poky/1.5.1/sysroots/x86_64-pokysdk-linux/usr/sbin ./armv5te-poky-linux-gnueabi/opt/poky/1.5.1/sysroots/x86_64-pokysdk-linux/usr/sbin/chpasswd ./armv5te-poky-linux-gnueabi/opt/poky/1.5.1/sysroots/x86_64-pokysdk-linux/bin ./armv5te-poky-linux-gnueabi/opt/poky/1.5.1/sysroots/x86_64-pokysdk-linux/bin/su ./armv5te-poky-linux-gnueabi/opt/poky/1.5.1/sysroots/x86_64-pokysdk-linux/bin/login ./armv5te-poky-linux-gnueabi/opt/poky/1.5.1/sysroots/x86_64-pokysdk-linux/etc ./armv5te-poky-linux-gnueabi/opt/poky/1.5.1/sysroots/x86_64-pokysdk-linux/etc/rcS.d ./armv5te-poky-linux-gnueabi/opt/poky/1.5.1/sysroots/x86_64-pokysdk-linux/etc/rcS.d/S98run-postinsts ./armv5te-poky-linux-gnueabi/opt/poky/1.5.1/sysroots/x86_64-pokysdk-linux/sbin ./armv5te-poky-linux-gnueabi/opt/poky/1.5.1/sysroots/x86_64-pokysdk-linux/sbin/vigr ./armv5te-poky-linux-gnueabi/opt/poky/1.5.1/sysroots/x86_64-pokysdk-linux/sbin/vipw
This is by design: meta/recipes-core/packagegroups$ cat nativesdk-packagegroup-sdk-host.bb | grep shadow nativesdk-shadow \ The nativesdk-shadow utils are included so the SDK can be used for running image postinstalls. If you don't watch this, you can remove that item from the packagegroup.
(In reply to comment #4) > The nativesdk-shadow utils are included so the SDK can be used for running > image postinstalls. > > If you don't watch this, you can remove that item from the packagegroup. The issue is not that nativesdk-shadow is present but the way it is packaged. /opt/poky/1.5.1/sysroots/armv5te-poky-linux-gnueabi/opt/poky/1.5.1/sysroots/x86_64-pokysdk-linux/usr/sbin/chpasswd the path is really odd. Is that really by design? Who will use/consume these binaries?