We are writing SFCB providers in python, Since SFCB talks to only C++ providers we need to have an intermediate layer(cmpi-bindings, a python extension module) which can talk to SFCB and start the provider when needed.
The same cmpi layer is working completely fine (i.e. reading SFCB call and then running the python provider)when it is run on ESX 4.1, but on ESX 4.0 it fails to import python modules.
After some debugging I found that import datetime module is failing with the unresolved symbol (PyExc_IOError) errror. I tried to build those module with -XLinker --exportdynamic so that they look for the those unresolved symbol as suggested in Python interpreter embedded in the application fails to load native modules , but went in vain.
What are the options I can try next. ( since the same code base is working for 4.1 but not 4.0). Any pointers will be helpful