summaryrefslogtreecommitdiffstats
path: root/README.hardware
diff options
context:
space:
mode:
authorJason Wessel <jason.wessel@windriver.com>2013-01-19 09:18:50 -0600
committerRichard Purdie <richard.purdie@linuxfoundation.org>2013-01-20 12:58:58 +0000
commit63ccf6242064055e280ffd05a4726f89de6b9b98 (patch)
tree139b03db6bdd4786c95288d3741b715fb92ec7bf /README.hardware
parent116fb4a72f352623b22a0c1a1a1500085f5918d3 (diff)
downloadpoky-63ccf6242064055e280ffd05a4726f89de6b9b98.tar.gz
populate_sdk_base.bbclass: Work around bugs with gnu tar < 1.24
The gnu tar versions less than 1.24 pose a problem with the SDK extraction. A typical SDK will have hard links. The SDK is created with a newer version of tar but extracted with the host version of tar which may be much older. The specific defect is that older version of gnu tar do not properly handle the "--strip-components=" argument when processing hard links and the paths do not get properly truncated and hooked up with the corresponding real file payloads. This leads to errors like the following during the SDK install: tar: sysroots/qemux86-yocto-linux/usr/bin/getconf: Cannot hard link to `./opt/yocto/SDK-qemux86/sysroots/qemux86-yocto-linux/usr/bin/POSIX_V6_ILP32_OFFBIG': No such file or directory The simple way to work around the problem is to just not save the path information that is going to get chopped off anyway. This has the added benefit that it saves a small amount of space in the tar archive as well. (From OE-Core rev: 0f4112016bac07f0294f2a4d0fde4659c0fed2d2) Signed-off-by: Jason Wessel <jason.wessel@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'README.hardware')
0 files changed, 0 insertions, 0 deletions