openembedded-core.git/scripts/runqemu-extract-sdk, branch pyro Mirror of openembedded-core oe-find-native-sysroot: work with RSS 2017-04-13T09:52:54+00:00 Robert Yang liezhi.yang@windriver.com 2017-04-12T21:29:12+00:00 e2f6d937bd897083779507ecb9ecd15513b35f1f The generic STAGING_DIR_NATIVE is gone since RSS, so when find OECORE_NATIVE_SYSROOT, the user has to specify which recipe's STAGING_DIR_NATIVE will be used as OECORE_NATIVE_SYSROOT. * The usage is changed from ". oe-find-native-sysroot" to ". oe-find-native-sysroot <recipe>". * The oe-run-native's usage has changed from "oe-run-native tool" to "oe-run-native native-recipe tool". Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 
The generic STAGING_DIR_NATIVE is gone since RSS, so when find
OECORE_NATIVE_SYSROOT, the user has to specify which recipe's
STAGING_DIR_NATIVE will be used as OECORE_NATIVE_SYSROOT.

* The usage is changed from ". oe-find-native-sysroot" to
  ". oe-find-native-sysroot <recipe>".
* The oe-run-native's usage has changed from
  "oe-run-native tool" to "oe-run-native native-recipe tool".

Signed-off-by: Robert Yang <liezhi.yang@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
runqemu-extract-sdk: normalize paths to improve output 2014-07-03T16:38:45+00:00 Chen Qi Qi.Chen@windriver.com 2014-07-03T03:02:21+00:00 c85f5ec502fecb1ff63f8e795a0da5fc92eca0c1 Previously, we would have output like below from runqemu-extract-sdk. Creating directory /home/chenqi/poky/build-systemd/./nfs-root Normalize paths for runqemu-extract-sdk so that we have output like below. Creating directory /home/chenqi/poky/build-systemd/nfs-root Signed-off-by: Chen Qi <Qi.Chen@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 
Previously, we would have output like below from runqemu-extract-sdk.

    Creating directory /home/chenqi/poky/build-systemd/./nfs-root

Normalize paths for runqemu-extract-sdk so that we have output like below.

    Creating directory /home/chenqi/poky/build-systemd/nfs-root

Signed-off-by: Chen Qi <Qi.Chen@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
runqemu-extract-sdk: add --numeric-owner option to tar command 2013-10-26T14:53:24+00:00 Chen Qi qi.chen@windriver.com 2013-10-21T02:42:29+00:00 acce6ff1a77cfd29e3868faa89b120becb58bbbf If the same username exists on both target and the build host, but the uids differ, and we start target via NFS, then the uid for the user will be incorrect on target. For example, if postfix's uid on host is 119 and on target is 1024, then if we start target via NFS, the uid for postfix will be 119. The root cause is that when we use runqemu-extract-sdk to generate the NFS rootfs for later use, the tar command will respect the username instead of uid. So if PSEUDO_PASSWD environment is not set correctly, the host /etc/passwd will be used, resulting in wrong uids. The situation for gid is completely analogous to that of uid. It's almost impossible for the runqemu-extract-sdk to guess the correct location of the needed password file merely based on the target tarball name. This patch solves this problem by adding the '--numeric-owner' option to the tar command so that the uid/gid will be used when extracting the tarball using runqemu-extract-sdk. In this situation, we'll always get the correct uid/gid after extracting the tarball. [YOCTO #5364] Signed-off-by: Chen Qi <Qi.Chen@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> 
If the same username exists on both target and the build host, but
the uids differ, and we start target via NFS, then the uid for the
user will be incorrect on target.

For example, if postfix's uid on host is 119 and on target is 1024,
then if we start target via NFS, the uid for postfix will be 119.

The root cause is that when we use runqemu-extract-sdk to generate
the NFS rootfs for later use, the tar command will respect the username
instead of uid. So if PSEUDO_PASSWD environment is not set correctly,
the host /etc/passwd will be used, resulting in wrong uids.

The situation for gid is completely analogous to that of uid.

It's almost impossible for the runqemu-extract-sdk to guess the correct
location of the needed password file merely based on the target tarball
name.

This patch solves this problem by adding the '--numeric-owner' option
to the tar command so that the uid/gid will be used when extracting the
tarball using runqemu-extract-sdk. In this situation, we'll always get
the correct uid/gid after extracting the tarball.

[YOCTO #5364]

Signed-off-by: Chen Qi <Qi.Chen@windriver.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
runqemu-export-rootfs and friends: don't put pseudo db in target fs 2012-08-28T15:03:41+00:00 Peter Seebach peter.seebach@windriver.com 2012-08-27T18:32:30+00:00 aa5d6bd006d3b4eede21d8987451876ed3385ab8 In a few places, we have scripts which use <rootfs>/var/pseudo for the pseudo state directory controlling a given filesystem. This seems possibly risky because it means that stuff running under qemu or whatnot could wipe out the data being used to handle that rootfs. Move this to: <rootfs>/../$(basename_rootfs).pseudo_state to avoid problems. This also solves at least one case (not directly hit by yocto's tree) wherein you could end up trying to remove a rootfs while pseudo was using a database inside that rootfs, and thus the remove would fail. Signed-off-by: Peter Seebach <peter.seebach@windriver.com> 
In a few places, we have scripts which use <rootfs>/var/pseudo for
the pseudo state directory controlling a given filesystem. This
seems possibly risky because it means that stuff running under
qemu or whatnot could wipe out the data being used to handle that
rootfs. Move this to:
  <rootfs>/../$(basename_rootfs).pseudo_state
to avoid problems.

This also solves at least one case (not directly hit by yocto's
tree) wherein you could end up trying to remove a rootfs while
pseudo was using a database inside that rootfs, and thus the
remove would fail.

Signed-off-by: Peter Seebach <peter.seebach@windriver.com>
scripts: Show sensible warning messages if expected binaries don't exist 2011-09-02T13:20:32+00:00 Richard Purdie richard.purdie@linuxfoundation.org 2011-09-01T21:04:48+00:00 6b5706d1f9ce7a3fd4d8f819ff8f3fd789665647 [YOCTO #1438] Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 
[YOCTO #1438]

Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Further cleanup of various poky references 2011-04-21T11:26:25+00:00 Richard Purdie richard.purdie@linuxfoundation.org 2011-04-21T11:26:25+00:00 fe73ea8c510877fe4e3c117985e8f3d0b79ddf1b Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
runqemu-extra-sdk: Update function usage to clearly reflect its meaning 2011-04-21T10:46:14+00:00 Richard Purdie richard.purdie@linuxfoundation.org 2011-04-21T10:46:14+00:00 04c1d218ffb775d25c0eaefa3558bab250bb3b4b Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Rename ~/.poky-sdk/ temp workdir to ~/.runqemu-sdk/ 2011-04-21T10:44:08+00:00 Richard Purdie richard.purdie@linuxfoundation.org 2011-04-21T10:44:08+00:00 69a0bfb8d7203db1c477dc28974287fda35d1a50 Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Rename the remaining poky-* scripts to oe-* or runqemu-* 2011-04-20T22:46:46+00:00 Richard Purdie richard.purdie@linuxfoundation.org 2011-04-20T22:24:51+00:00 877b3d84597fcfc3abf5aa332019d412f2717896 Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>