12963 2018-10-17 05:00:11 +0000 nativesdk-opkg prefixes all internal paths with $SDKPATH and won't work 2026-09-09 16:51:40 +0000 1 1 7 Build System, Metadata & Runtime OE-Core core unspecified x86 Multiple RESOLVED FIXED Medium+ normal 6.99 1 denis Harish.Sadineni alejandro.delcastillo liezhi.yang meta.mr.watcher meta.watcher randy.macleod richard.purdie tgamblin --- --- Don't know oldest_to_newest 81887 0 denis 2018-10-17 05:00:11 +0000 Built an SDK with opkg, installed and relocated it. When trying to use it to update a copy of rootfs at /tmp/sdk/rootfs (e.g. opkg -o /tmp/sdk/rootfs list), it silently fails. And strace shows that it tries to access following files/dirs: /tmp/sdk/rootfs///opt/poky/2.5+snapshot/sysroots/x86_64-pokysdk-linux/etc/opkg /tmp/sdk/rootfs///opt/poky/2.5+snapshot/sysroots/x86_64-pokysdk-linux/var/cache/opkg /tmp/sdk/rootfs////opt/poky/2.5+snapshot/sysroots/x86_64-pokysdk-linux/var/lib/opkg/info /tmp/sdk/rootfs////opt/poky/2.5+snapshot/sysroots/x86_64-pokysdk-linux/var/lib/opkg /tmp/sdk/rootfs////opt/poky/2.5+snapshot/sysroots/x86_64-pokysdk-linux/var/lib/opkg/status When it works, it should be: /tmp/sdk/rootfs/etc/opkg /tmp/sdk/rootfs/var/cache/opkg /tmp/sdk/rootfs/var/lib/opkg/info /tmp/sdk/rootfs/var/lib/opkg /tmp/sdk/rootfs/var/lib/opkg/status 83070 1 randy.macleod 2019-02-21 16:12:01 +0000 Chen, are you able to reproduce this problem? Moved to M3 and note that the deadline/goal is before the end of February. 83115 2 alejandro.delcastillo 2019-02-25 17:15:59 +0000 To make the SDK relocatable, the call that installs the SDK at /opt/poky/2.5+snapshot/sysroots/x86_64-pokysdk-linux/ should use an offline root (-o /opt/poky/2.5+snapshot/sysroots/x86_64-pokysdk-linux/) to have the opkg housekeeping files register files relative to /opt/poky/2.5+snapshot/sysroots/x86_64-pokysdk-linux. 83121 3 denis 2019-02-26 05:06:58 +0000 (In reply to comment #2) > To make the SDK relocatable, the call that installs the SDK at > /opt/poky/2.5+snapshot/sysroots/x86_64-pokysdk-linux/ should use an offline > root (-o /opt/poky/2.5+snapshot/sysroots/x86_64-pokysdk-linux/) to have the > opkg housekeeping files register files relative to > /opt/poky/2.5+snapshot/sysroots/x86_64-pokysdk-linux. I don't want to install/relocate SDK to /opt/poky/2.5+snapshot/sysroots/x86_64-pokysdk-linux/, but that path gets hardcoded to nativesdk-opkg binary. 83124 4 alejandro.delcastillo 2019-02-26 15:46:38 +0000 My comment was meant to be a hint for Chen: to make the SDK relocatable, the code that creates the SDK should use an offline root. 83387 5 denis 2019-04-01 01:50:35 +0000 Any updates? 87731 6 randy.macleod 2020-07-09 08:23:50 +0000 Robert nor Qi are able to work on this now. :( 94640 7 yoann.congal 2023-01-08 09:07:38 +0000 I've looked into this and it really looks like a hard limit on path length in the sqlite code. I guess we can do 2 things about this : - Setup an explicit error when this path length is used (saying we don't support this, sadly) - Trying to push an improvement to sqlite to remove this limitation 94641 8 yoann.congal 2023-01-08 09:09:54 +0000 (In reply to comment #7) > I've looked into this and it really looks like a hard limit on path length > in the sqlite code. I guess we can do 2 things about this : > - Setup an explicit error when this path length is used (saying we don't > support this, sadly) > - Trying to push an improvement to sqlite to remove this limitation Oh I this comment did not end up in the good bug... Sorry, please ignore. 96069 9 randy.macleod 2023-07-26 21:22:00 +0000 Bulk move of 64 bugs to 4.3 M3 after a quick review. If a bug is actually fixed, please add a commit link and resolve it. -- Randy for YP bug team. 96436 10 tgamblin 2023-09-14 15:44:49 +0000 Moved to M4. 97061 11 randy.macleod 2023-10-30 15:29:09 +0000 Bulk move to 5.0 M1. -- Randy 97692 12 randy.macleod 2023-12-21 23:28:33 +0000 Bulk move of 52 5.0-M1 bugs to M2. 98006 13 randy.macleod 2024-01-25 14:28:49 +0000 Bulk move of bugs owned by "unassigned" from 5.0-M2 to 5.0-M3. 98303 14 randy.macleod 2024-02-22 19:53:23 +0000 Bulk move of bugs from 5.0-M3 to 5.99. The bugs in this list are all unassigned and are ones that I consider to be nice to do some time but not essential track from milestone to milestone in 5.0 or 5.1. We agreed on this bug handling approach in the YP bug review on Feb 22, 2024. If you disagree, please move back to a 5.[012...]-M* milestone. 104581 15 randy.macleod 2026-03-11 15:22:59 +0000 I'm not sure if this is still a problem but after 6.0 is in good shape, we should check. 106657 16 Harish.Sadineni 2026-08-27 10:55:39 +0000 With latest master this issue is currently not occurring. 106757 17 Harish.Sadineni 2026-09-09 06:01:10 +0000 Verification Steps: Test on current oe-core/master: Added the following to local.conf: TOOLCHAIN_TARGET_TASK:append = " opkg" TOOLCHAIN_HOST_TASK:append = " nativesdk-opkg" PACKAGE_CLASSES = "package_ipk" SDKIMAGE_FEATURES:append = " package-management" Built and installed the SDK, then relocated it. Copied the target sysroot to /tmp/sdk/rootfs and ran: opkg -o /tmp/sdk/rootfs list This completed successfully. Sample output: acl-dbg - 2.4.0-r0 acl-dev - 2.4.0-r0 acl-src - 2.4.0-r0 base-files - 3.0.14-r0 ... To confirm which paths opkg was accessing, I traced the command: strace -f -e trace=file -o /tmp/opkg_strace.log opkg -o /tmp/sdk/rootfs list The strace log showed it correctly accessing: /tmp/sdk/rootfs/etc/opkg /tmp/sdk/rootfs/etc/opkg/arch.conf /tmp/sdk/rootfs/etc/opkg/opkg.conf /tmp/sdk/rootfs/var/lib/opkg/info /tmp/sdk/rootfs/var/lib/opkg /tmp/sdk/rootfs/var/lib/opkg/status Test on Dunfell (same steps): Repeating the identical procedure on Dunfell, the command failed silently, no output and no error. Tracing this with strace showed opkg instead accessing paths under the hardcoded SDK build path, rather than the relocated rootfs I specified: /tmp/sdk1/rootfs/usr/local/oe-sdk-hardcoded-buildpath/sysroots/x86_64-pokysdk-linux/etc/opkg /tmp/sdk1/rootfs/usr/local/oe-sdk-hardcoded-buildpath/sysroots/x86_64-pokysdk-linux/var/cache/opkg /tmp/sdk1/rootfs/usr/local/oe-sdk-hardcoded-buildpath/sysroots/x86_64-pokysdk-linux/var/lib/opkg/info /tmp/sdk1/rootfs/usr/local/oe-sdk-hardcoded-buildpath/sysroots/x86_64-pokysdk-linux/var/lib/opkg /tmp/sdk1/rootfs/usr/local/oe-sdk-hardcoded-buildpath/sysroots/x86_64-pokysdk-linux/var/lib/opkg/status 106758 18 Harish.Sadineni 2026-09-09 06:03:43 +0000 Closing this issue as Resolved, Since this issue is not anymore occurring on oe-core/master. 106769 19 denis 2026-09-09 16:51:40 +0000 Thank you for your due diligence.