On 6/1/20 4:37 AM, Honggang LI wrote:
On Sun, May 31, 2020 at 10:30:32AM -0700, Gordon Messmer wrote:
> On 5/31/20 1:24 AM, Honggang LI wrote:
>> As you see, "-lpython3.9" or "-lpython3.9d" library must be
provided to
>> the linker. Otherwise, a lot of "undefined reference to xxx" error
>> messages show up.
>
>
> I'd guess that you're seeing "undefined reference" when you use ldd
on the
> so, and that's expected. That's the wrong way to test the object, though.
> Instead, install that module and import it from a python3 shell. Do you get
We have to compile/build the module before we can import it from a
python3 shell. The problem is how to compile the modules without pass
"-lpython3.9" or "-lpython3.9d" to the linker (/usr/bin/ld).
Just FWIW, "-z defs" linker flag (typically "-Wl,-z,defs" in build
logs
where invoked through compiler) is one potential cause for getting
errors for this.
Ran into that myself with rpm's python module - I had it in my build
settings from whatever long forgotten experiment and suddenly started
failing when Python 3.9 changed the linkage expectations (via pkg-config)
- Panu -