aboutsummaryrefslogtreecommitdiffstats
path: root/meta/recipes-core/dropbear
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:49:26 +0000
commit0f4112016bac07f0294f2a4d0fde4659c0fed2d2 (patch)
tree9cfdc66e73849c94846ae28ed51d64ce42eda9e9 /meta/recipes-core/dropbear
parent6e46664085fa49bc204fc944ca23ed6383e2ec51 (diff)
downloadopenembedded-core-contrib-0f4112016bac07f0294f2a4d0fde4659c0fed2d2.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. Signed-off-by: Jason Wessel <jason.wessel@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta/recipes-core/dropbear')
0 files changed, 0 insertions, 0 deletions