Comment 2 for bug 86685
Revision history for this message
| Antonio Censi (accensi) wrote Re: neo_cgi.so: undefined symbol: Py_InitModule4 | #2 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
I have made a compile from source in Feisty environment with Python 2.5.
IMHO, the build process is buggy, just compiling and linking againt python2.4 libs and copying the .so file (just one file - neo_cgi.so) both to python2.5 and 2.5 SitePackages dirs. This can be confirmed by other short tests: all packages in python2.4 have just external references to Py_InitModule4, and in python2.5 there are only references to Py_InitModule4_64, except for the neo_cgi.so.
Perhaps the solution adopted has no side-effects in 32bit land, although it not correct too.
Build process result is attached. I think that the bug should be changed to confirmed, at least. I do not know if it affects upstream, as this solution of having python2.5 and python2.4 at the same time is a temporarily solution for Ubuntu, or it will be adopted by Debian too.