Error compiling 1.0.6 from sources

[alexdrymonitis]

I'm trying to compile 1.0.6 from sources with python3 -m build --config-settings="--build-option=--use-jack" --config-settings="--build-option=--use-double" and I'm getting this error:

/usr/bin/ld:build/temp.linux-x86_64-cpython-311/src/engine/_pyo.cpython-311-x86_64-linux-gnu.def: file format not recognized; treating as linker script
/usr/bin/ld:build/temp.linux-x86_64-cpython-311/src/engine/_pyo.cpython-311-x86_64-linux-gnu.def:1: syntax error
collect2: error: ld returned 1 exit status
error: command '/usr/bin/x86_64-linux-gnu-gcc' failed with exit code 1

ERROR Backend subprocess exited when trying to invoke build_wheel

I have compiled 1.0.5 from sources with the same settings without errors. I'm on Debian 12 with Python3.11.

[belangeo]

Have you tried with --config-setting instead of --config-settings?

Also on Debian 12 / Python 3.11 here. Can you delete "build" and "dist" folders before compiling, just in case...

[alexdrymonitis]

Yes, using config-setting. I've edited the message with a couple more error lines there. Could it be there? I tried deleting the dist directory (there's no buid directory) but still get the same error. Is it the syntax error that's the culprit?

[belangeo]

gcc version?

I have 12.0.0-14 here.

[alexdrymonitis]

I have 12.2.0-14

[belangeo]

No "build" directory? Strange... Really looks like there something old lying around. Make sure that there are no "build", "dist", and "pyo.egg-info" before compiling.

[alexdrymonitis]

Still no dice. I removed both dist/ and pyo.egg-info/ and the error insists.

[belangeo]

I'm wondering, Any error about liblo in the compilation process, prior to the linking problem?

Debian bookworm comes with liblo-dev 0.31, but we need to install 0.32 (from trixie).

[alexdrymonitis]

There's no other error than the one I've posted. It's true I have 0.31-1. How do I install 0.32? But, since I don't get any other error, I guess it's not necessary. Would't hurt to try though.

[belangeo]

Yes, it's necessary... There are breaking changes in liblo 0.32, and Windows and MacOS already have this lib updated. I didn't want to conditionally support both version, so I increased the requirement for pyo. To install, I just add trixie repo in /etc/apt/sources.list.d/, install liblo-dev 0.32, and remove trixie from apt.

[belangeo]

You should absolutely not be able to build 1.0.6 with liblo-dev 0.31... I would throw away everything pyo related, and compile from a fresh repo, to be sure nothing is interfering.

[alexdrymonitis]

I've updated liblo-dev to 0.32-2, downloaded the source again from https://test.pypi.org/project/pyo/#files
Removed pyo.egg-info, but I'm still getting the same error.

[belangeo]

Oh, I didn't realized you were using the distributed sources (I thought sources as a git clone). I can also repro here with the source distribution from test.pypi... I suspect that it is because I uploaded the sdist build made on MacOS. If I use an sdist build on linux, it works as expected (you can try with the tar.gz attached here). I really don't understand because the sources should be exactly the same taken from whatever the system, but apparently not. I guess it would be better to upload the source distribution from linux, as this is the most expected platform it will be used on. Thanks for highlighting the issue!

pyo-1.0.6.tar.gz

[alexdrymonitis]

That worked! It worked for Python3.11. I then compiled Python3.13.2 and installed wxPython with pip, and then run python3 -m build --config-setting="--build-option=--use-jack" --config-setting="--build-option=--use-double" again (Python3.13.2 is now my default Python, so this command should invoke Python3.13.2, right?). It did build Pyo, but trying to import it, I get the No module named 'pyo' error. I tried this from my home directory, not Pyo's directory.

[belangeo]

Didi you install it? This command only builds a whl file, it must be installed with pip:

python3 -m pip install dist/pyo-1.0.6-cp313-cp313-linux_x86_64.whl

I should definitely add this step in the documentation!

[alexdrymonitis]

That did it! Yes, I think this has to go into the documentation! Thanks for the help!

[belangeo]

Done