-
Notifications
You must be signed in to change notification settings - Fork 312
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Swig error: Syntax error in input(3) with swig < 4.2 #400
Comments
Line 139 in 778502a
It's probably the "Remove some old SWIG workarounds" part of 755fe37. Older swig didn't understand Works for me with swig 4.2.1. Can you check the swig versions on the working/non-working systems? |
Versions I've tried:
|
Just learned pypi has swig. All failures are the same error.
|
After #390, I could make an edit to the README either saying we need swig 4.2, or remove mentioning SWIG completely, because |
Swig 4.2 is only ~1 year old, a bit too new to depend on based on the versions you're seeing. I'll add the |
What controls the version of swig that will be downloaded? |
I think the |
Right. With no version specified, it will download the latest available from pypi with is currently 4.3.0. (With the option of adding a constraint in the future. E.g. 4.4.0 breaks compatibility, so you can say |
That sounds easier. Let's wait until |
I was able to build successfully on master on the docker image
quay.io/pypa/manylinux_2_28_x86_64
(CentOS/Alma/RHEL 8 based), but imagepython:3.13
(Debian based) errors on one of the swig steps. Reverting to tagv0.11.1
fixed the problem.I also saw the same failures when building with VS2022 on Windows 11
This seems to have broken some where between commits 7940c9f (works) and 755fe37 (gets the error)
Version
Compile Error
Linux
Windows
Linux env
docker run -it --rm python:3.13 bash
Windows env
Same errors when using C++17
Using C++14 errored with:
So either my gcc is picky, or the README is out of date when it says says "A C++ compiler with C++14 support"
The text was updated successfully, but these errors were encountered: