Open GoogleCodeExporter opened 9 years ago
I am using Macports Python 2.6.6 with Macports Swig
Original comment by TimWJone...@gmail.com
on 22 Jun 2011 at 2:14
And I made a typo: that title should read "OSX" not "OSC".
Original comment by TimWJone...@gmail.com
on 22 Jun 2011 at 2:15
The old SWIG version is most definitely the issue. Please upgrade and let me
know your results.
Original comment by sir...@gmail.com
on 22 Jun 2011 at 2:20
Thanks for the fast reply!
Macports Swig is 2.0.4, which is the most recent version. However I'll try
installing it from the normal download and see if that helps.
Original comment by TimWJone...@gmail.com
on 22 Jun 2011 at 2:28
Sorry, perhaps I did dismiss your issue a bit too quickly. SWIG 2.0.4, as you
say, is the most recent version. However, I have tested that version on win32
with no issue (and just re-tested to make sure).
I can't understand how SWIG's parsing algorithms could differ on each platform.
Original comment by sir...@gmail.com
on 22 Jun 2011 at 2:47
FWIW: I was able to route around this problem by switching from MacPorts to
system python.
Original comment by TimWJone...@gmail.com
on 25 Jun 2011 at 6:01
Can you tell me if the SWIG the two versions executed were different? Or were
there different command line arguments passed to SWIG in MacPorts Python versus
System Python? A full build log from each would be helpful.
Original comment by sir...@gmail.com
on 25 Jun 2011 at 3:05
I'm running Swig 1.3.31. I didn't save the build log so am not sure what flags
were used.
Original comment by TimWJone...@gmail.com
on 25 Jun 2011 at 6:34
I thought you meant you were using SWIG 2.0.4? If not, some 1.3.x versions are
known to cause this syntax error issue, and that would make this a duplicate of
issue 40, as you mentioned.
Original comment by sir...@gmail.com
on 25 Jun 2011 at 6:42
Original issue reported on code.google.com by
TimWJone...@gmail.com
on 22 Jun 2011 at 2:12