I think my last post clears up the issue. An interface change was made in
python 2.5 that broke swig prior to 1.3.30. So I think its simply a problem
that openpkg includes python 2.5 and swig 1.3.29. I downloaded swig 1.3.31,
updated the swig.spec file, build the package and everything works. You
most likely run in to this sort of version creep problem in current all the
time, as it is a fast moving target. For the stable branch, it would be
worth considering an update to swig for the sake of inter-package
compatibility.
-thanks
Well, I guess Debian's SWIG is a different version than OpenPKG's SWIG
and OpenPKG's SWIG seems to generate C++ code which our GCC dislikes.
Look at the line GCC complains about: the generated code certainly has a
difference there (or at the place of a variable declaration in case the
line GCC complains about uses a variable). But in any way, I think you
have to report this to either the Python and/or the SWIG guys, as only
those will be able to really help...
Ralf S. Engelschall
[EMAIL PROTECTED]
www.engelschall.com
______________________________________________________________________
The OpenPKG Project www.openpkg.org
User Communication List openpkg-users@openpkg.org
