Created attachment 3761 [details] devtool modify log Steps to Repeat ================ * Build a stock eSDK for core-image-minimal $ bitbake core-image-minimal -c populate_sdk_ext * install the SDK on another host than the one that generated the SDK * source the eSDK environment * use devtool to modify a recipe (sdk)$ devtool modify openssh Attached is the full log. Further investigation with 'devtool -d modify --keep-temp openssh' (--keep-temp only available after commit 2338032) reveals that one of the scripts running behind the scene, uses paths from the build host. In particular, the script /home/vagrant/poky_sdk_i586/tmp/work/i586-poky-linux/openssh/7.4p1-r0/devtooltmp-0dew_vqb/workdir/recipe-sysroot/usr/bin/postinst-useradd-dbus declare a quite suspicious PSEUDO variable as: export PSEUDO="PSEUDO_PREFIX=/scratch/gizero/poky-master-build/tmp/sysroots-components/x86_64/pseudo-native/usr PSEUDO_LOCALSTATEDIR=/scratch/gizero/poky-master-build/tmp/work/i586-poky-linux/dbus/1.10.14-r0/pseudo/ PSEUDO_PASSWD=/home/vagrant/poky_sdk_i586/tmp/work/i586-poky-linux/openssh/7.4p1-r0/devtooltmp-0dew_vqb/workdir/recipe-sysroot:/scratch/gizero/poky-master-build/tmp/sysroots-components/x86_64/pseudo-native PSEUDO_NOSYMLINKEXP=1 PSEUDO_DISABLED=0 PSEUDO_LOCALSTATEDIR=/home/vagrant/poky_sdk_i586/tmp/work/i586-poky-linux/openssh/7.4p1-r0/devtooltmp-0dew_vqb/workdir/recipe-sysroot/var/pseudo /scratch/gizero/poky-master-build/tmp/sysroots-components/x86_64/pseudo-native/usr/bin/pseudo" Shouln't this be all relative to SDK path instead of build host ones?
I think this should be resolved by Peter's recent patchset: https://patchwork.openembedded.org/series/6598/
Peter's patchset worked for me here. Thanks Paul for pointing to it!
Peter's patches were merged to master (and pyro, post 2.3 release): http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=439bb8cc711799b45a7f14dc8bcb1d524d993ab2 http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=7b56a4327bdef25b99e1376fc30f03a8dba45885