Re: Can't open compiled [pyo~] object
Alexandros Drymonitis <[email protected]>
| Newsgroups | gmane.comp.multimedia.puredata.general |
|---|---|
| Message-ID | <[email protected]> |
On 7/15/25 18:13, IOhannes m zmölnig via Pd-list wrote: > Am 14. Juli 2025 19:16:41 MESZ schrieb Alexandros Drymonitis <[email protected]>: >> Your Makefile works (I guess you're not surprised :). > not really. sometimes I test the stuff I'm posting :-) > > >>> having said that, I've compiled the external with python3.13 (Debian/trixie/sid), but... >> I wanted to build it for Python3.13 too, but I couldn't find the libpython3.13.so file on my system. I'm on Debian 12 and compiled Python3.13 myself. Any idea where this is? > usually self-compiled thingies go into `/usr/local` if you run `make install`. > > but this really depends on the actual build system and what you*really* did. it's nigh impossible to tell from here. I asked Python's forum and was told that the trick was to build with `./configure --enable-shared`. Indeed, now I have a libpython3.13.so.1.0 in /usr/local/lib. I tried to build the object now with Python3.13, following your instructions (your Makefile and with `make PY_LIBS="-lpython3.13"` or `make PYTHON=python3-embed`). The object builds but when I load it I get this error: ``` /home/alex/Documents/Pd/externals/pyo~/pyo~.pd_linux:libpython3.13.so.1.0: cannot open shared object file: No such file or directory ``` How can I link libpython3.13.so.1.0 to the object? --- [email protected] - the Pure Data mailinglist https://lists.iem.at/hyperkitty/list/[email protected]/message/CTSH44NMLLBO3NX352WUNXWGMYRKFLNM/ To unsubscribe send an email to [email protected] mailing list UNSUBSCRIBE and account-management -> https://lists.iem.at/