Re: Relocation of SDK

[Baurzhan Ismagulov <ibr@radix50.net>]

On Sat, Feb 20, 2021 at 09:31:34PM +0000, Daniel Machon wrote:
> I would argue, that a common development workflow would be to use the
> cross-toolchain provided by the SDK, and then chroot into the SDK to install
> dependencies (we have the possibility of installing multiarch packages).

I agree that chroot / nspawn / ... into the SDK is a useful feature and we
should keep it working.


> If you need to change the RPATH of any libraries (I came across this need
> when trying to make gdb available to the host), you can make RPATH relative
> using $ORIGIN.

We had tried that and it didn't work:

https://groups.google.com/g/isar-users/c/sjqTLpw4KTE/m/Ro9aLnGZAQAJ

So, the current way is to run the script to undo the relocations, chroot, then
create the relocations again. If you try this, please let us know whether it
works. IIRC, during the remove the script puts some replacement relocations
into the binaries, while the original binaries don't have any -- but that
should work.

Otherwise, one has probably to rebuild the SDK with updated SDK_PREINSTALL /
SDK_INSTALL. Not sure how that works for the existing packages not coming from
Debian.


With kind regards,
Baurzhan.