<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<style type="text/css" style="display:none;"><!-- P {margin-top:0;margin-bottom:0;} --></style>
</head>
<body dir="ltr">
<div id="divtagdefaultwrapper" style="font-size:12pt;color:#000000;font-family:Calibri,Arial,Helvetica,sans-serif;" dir="ltr">
<br>
<div style="color: rgb(0, 0, 0);"><font size="2"><span style="font-size:10pt;">
<div class="PlainText">>> In 3eee8e99 sstate got changed to refuse absolute symlinks. Externalsrc<br>
<font size="2"><span style="font-size:10pt;">></span></font>> creates absolute symlinks for oe-logs and oe-workdir which causes<br>
<font size="2"><span style="font-size:10pt;">></span></font>> errors at do_populate_sysroot.<br>
<font size="2"><span style="font-size:10pt;">></span></font>> Changing symlinks to relative paths will make externalsrc comply with sstate<br>
<font size="2"><span style="font-size:10pt;">></span></font>> changesi and will avoid those errors.<br>
<font size="2"><span style="font-size:10pt;">></span></font><br>
<font size="2"><span style="font-size:10pt;">></span></font>This implies that you (or more precisely, the build system of whatever your
<br>
<font size="2"><span style="font-size:10pt;">></span></font>recipe is building) is installing these symlinks to ${D} from the source tree
<br>
<font size="2"><span style="font-size:10pt;">></span></font>-<font size="2"><span style="font-size:10pt;"></span></font> I would recommend avoiding that, since those symlinks are of no use on the
<br>
<font size="2"><span style="font-size:10pt;">></span></font>target or indeed the sysroot, and making them relative means they will
<br>
<font size="2"><span style="font-size:10pt;">></span></font>definitely be broken when moved elsewhere in any case.<br>
<font size="2"><span style="font-size:10pt;">></span></font><br>
<font size="2"><span style="font-size:10pt;">></span></font>Which recipe(s) are you experiencing this issue with? If they are custom ones,
<br>
<font size="2"><span style="font-size:10pt;">></span></font>how is what happens during do_install defined there?<br>
<br>
Hi Paul,<br>
<br>
Thanks for your reply. The problem occured after altering custom recipes with<br>
devtool. We worked on a native and on a nonnative recipe and got following<br>
messages:<br>
<font size="2"><span style="font-size:10pt;"></span></font><br>
<div>NOTE: api-gen-native: compiling from external source tree /home/erdmann/yocto/build/workspace/sources/api-gen-native<br>
ERROR: api-gen-native-1.0.0+git999-r0 do_populate_sysroot: sstate found an absolute path symlink /home/erdmann/yocto/build/tmp/work/x86_64-linux/api-gen-native/1.0.0+git999-r0/sysroot-destdir/home/erdmann/yocto/build/tmp/work/x86_64-linux/api-gen-native/1.0.0+git999-r0/recipe-sysroot-native/usr/lib/api-gen-native/oe-workdir
pointing at /home/erdmann/yocto/build/tmp/work/x86_64-linux/api-gen-native/1.0.0+git999-r0. Please replace this with a relative link.<br>
ERROR: api-gen-native-1.0.0+git999-r0 do_populate_sysroot: sstate found an absolute path symlink /home/erdmann/yocto/build/tmp/work/x86_64-linux/api-gen-native/1.0.0+git999-r0/sysroot-destdir/home/erdmann/yocto/build/tmp/work/x86_64-linux/api-gen-native/1.0.0+git999-r0/recipe-sysroot-native/usr/lib/api-gen-native/oe-logs
pointing at /home/erdmann/yocto/build/tmp/work/x86_64-linux/api-gen-native/1.0.0+git999-r0/temp. Please replace this with a relative link.</div>
<br>
I tried to double check and am quite conviced we did not try to install these<br>
symlinks. I hope these informations draw a more clear picture of the<br>
problem which lead to this attempt to fix this.<br>
<br>
Regards,<br>
<br>
Jens Erdmann<br>
<br>
</div>
</span></font></div>
</div>
</body>
</html>