On Mon, Mar 21, 2022 at 04:46:55PM -0400, Mark Phippard wrote: > On Mon, Mar 21, 2022 at 4:31 PM Stefan Sperling <s...@elego.de> wrote: > > This might be a swig problem? Perhaps the version of swig and the > > version of python don't work well together? Not sure. > > HACKING implies I should use the version that the clean room > environment installs and not what the OS installs so I ran: > > ./configure --with-swig=/opt/svnrm/prefix > > This could be an example where the docs are just not explicit enough > and I was overthinking. Now that I think about it maybe the problem is > that this is not found when I run the tests. Perhaps I should use the > OS SWIG for building and testing? Makes me wonder how the clean room > version is ever used though?
While the clean-room env includes swig, it does not include python. So python comes from the system. And, as far as I understand, python is complaining about a syntax error in the code generated by swig. I would try to find out whether the clean-room swig expects a particular range of python versions. Maybe you can use a corresponding version of python in your docker image. What might also help is upgrading swig to a newer version. If upgrading tools in the clean-room env fixes such problems then we should upgrade them.
