| Summary: |
[Dropbear] dropbear.inc creates an absolute systemlink, even though Yocto only allows relative syslinks |
| Product: |
[Build System, Metadata & Runtime] OE-Core
|
Reporter: |
Erik <erik.burghardt> |
| Component: |
core | Assignee: |
Unassigned <unassigned> |
| Status: |
RESOLVED
NOTABUG
|
QA Contact: |
|
| Severity: |
critical
|
|
|
| Priority: |
Medium+
|
CC: |
meta.mr.watcher, meta.watcher, tgamblin, zyckk4
|
| Version: |
4.0.1 | |
|
| Target Milestone: |
0.0.0 | |
|
| Hardware: |
Other | |
|
| OS: |
arm | |
|
| Whiteboard: |
|
|
OS type for building Yocto:
|
---
|
Type of Regression:
|
---
|
|
Verified:
|
|
Documentation change:
|
No (bug/feature does not impact docs)
|
This bug can be found in poky/meta/recipes-core/dropbear/dropbear.inc in kirkstone-4.0.12. It was only tested on this version It can still be found in scarthgap, even though in another file: poky/meta/recipes-core/dropbear/dropbear_2022.83.bb. The bug appears in the following way: 1. You import dropbear-native:do_populate_sysroot somewhere like in this .bbclass: do_image_qemu_disk[depends] = " \ gptfdisk-native:do_populate_sysroot \ e2fsprogs-native:do_populate_sysroot \ virtual/fakeroot-native:do_populate_sysroot \ dropbear-native:do_populate_sysroot \ " 2. This calls dropbear.inc 3. In dropbear.inc, there are the following lines: ln -s ${sbindir}/dropbearmulti ${D}${bindir}/$i and ln -s ./dropbearmulti ${D}${sbindir}/$i Both lines create syslinks with absolute paths. 4. This leads to the following error, when building: ERROR: dropbear-native-2020.81-r0 do_populate_sysroot: sstate found an absolute path symlink /home/yocto/build/tmp/work/x86_64-linux/dropbear-native/2020.81-r0/sysroot-destdir/home/yocto/build/tmp/work/x86_64-linux/dropbear-native/2020.81-r0/recipe-sysroot-native/usr/bin/dbclient pointing at /home/yocto/build/tmp/work/x86_64-linux/dropbear-native/2020.81-r0/recipe-sysroot-native/usr/sbin/dropbearmulti. Please replace this with a relative link. 5. An important fact: When you build this the first time, it will give this error. If you then build it again without changes, the build will succeed, so it seems something that makes the second build happy is cached in the first build. You can force the build to error again by running "bitbake -c cleanall dropbear-native"