Closed christian-vorhemus closed 9 months ago
@christian-vorhemus you might have to first run /usr/lib/rpm/mariner/gen-ld-script.sh
to generate /usr/src/mariner/BUILD/module_info.ld
. This should get you past the no such file or directory
error.
Indeed, that fixes the issue! Thanks @elsaco! Just out of curiosity, do you know why it is designed that way? Why is there a script to generate a linker script?
Thanks for bringing up the issue! Upon further investigation, it looks like build flags that only make sense in our build environment are leaking out via Python's sysconfig
module.
I've opened up #1824 as a fix for our 2.0 branch. Once merged, I will backport this to our 1.0 branch when time permits.
And to answer your other question- we generate a linker script at build-time to insert distro/package information into ELF objects. This ensures the provenance of a package is included in a core dump. This is part of a cross-distro effort, and you can find out more about it here.
this appears fixed per the last comment, closing
I'm using Azure Percept November Service Release (2111) which is using the following Mariner version in their latest update:
When I try to install the this Python module running
sudo pip3 install ./azure-percept-py/
I getThe same seems to be true for other Python modules that require compilation + linking like
sudo pip3 install psutil
:I'm not sure where
module_info.ld
is coming from and why Python requires this linker script but it worked in previous versions of Mariner (unfortunately I don't have the number of the working version).