Re: dlopen("python3912.unit.so”), failed: “libpython3.9.so.1.0 cannot open shared object file: No such file or directory

[Ariel Goyeneche]

Thanks Andrew. This did the trick:
> I think --lib-path is supposed to point to a directory, not a file. Try
> —lib-path=/bin/miniconda39/lib


Thanks
AG

> On 1 Nov 2022, at 20:07, Andrew Clayton <andrew at digital-domain.net> wrote:
> 
> On Tue, 1 Nov 2022 19:23:17 +0100
> Ariel Goyeneche <agoyeneche at gmail.com> wrote:
> 
>> 	configure. python —config=/bin/miniconda39/python3.9-config —module=python3912 —lib-path=/bin/miniconda39/lib/libpython3.9.so
> 
> I think --lib-path is supposed to point to a directory, not a file. Try
> —lib-path=/bin/miniconda39/lib
> 
>> 	make
>> 
>> Note that /bin/miniconda39/lib/libpython3.9.so exists and it is a symlink to /bin/miniconda39/lib/libpython3.9.so.1.0
> 
> [...]
> 
>> When I am trying to start unitd I have the following error in the log file
>> 	dlopen("/bin/unit-1.28.0/build/python3912.unit.so”), failed: “libpython3.9.so.1.0 cannot open shared object file: No such file or directory”
>> 
>> Can you please help me to understand what the problem may be here?
> 
> If fixing --lib-path doesn't help, you could also try something like
> when starting unit
> 
>  LD_LIBRARY_PATH=/bin/miniconda39/lib /path/to/unitd ...
> 
> Cheers,
> Andrew