summaryrefslogtreecommitdiffstats
path: root/bitbake
diff options
context:
space:
mode:
authorRichard Purdie <richard.purdie@linuxfoundation.org>2013-08-23 09:02:21 (GMT)
committerRichard Purdie <richard.purdie@linuxfoundation.org>2013-08-23 16:29:33 (GMT)
commit4273aa4287ecd36529f2d752c76ab8d09afc33c3 (patch)
treea77c6143793517c2d91a1951c80c0e9a188cc3a9 /bitbake
parent445e1e5b740618e5f04c0ef6515ab53f41ac35de (diff)
downloadpoky-4273aa4287ecd36529f2d752c76ab8d09afc33c3.tar.gz
sstate: Fix the relative symlink replacement code
ant reported on irc that the sstate absolute to relative symlink creation code wasn't working in klibc. He was correct although the level of breakage is rather surprising since it only worked for one level of symlink (usr/include) with everything else being broken. The reason is probably that nothing really uses absolute paths, we use relative paths where at all possible already. Nothing in the target sysroot should use absolute paths for a start. In this regard, the klibc-dev package is broken and needs fixing. It will currently break when building for one machine, then switching to another of the same TUNE_PKGARCH and installing from sstate but that is a separate issue. This patch fixes the symlink creation code by firstly passing in the correct value we need (where the symlink will end up) and seccondly, actually using it. I've also tweaked the debug message to contain appropriate information and got right of the double "//" value the existing code created in favour of the form './..' which looks neater. (From OE-Core rev: 9b05c65450526522d7358d0c0901b594de546748) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'bitbake')
0 files changed, 0 insertions, 0 deletions