Has anyone had success using Boost with the uClibc libraries? In particular, have you got Boost.Python to work? I am using the getting_started1.cpp example provided with Boost. I am using Boost 1.30.0, uClibc 0.9.20 and Python 2.2.3. Note that uClibc does not currently support a dlopen() called library calling a dlopen(). I have found that as long as the library is loaded with Python, I can get it to work. I am currently using the SSL version of the socket module, which is using SSL libraries linked against Python. I have tried 2 techniques so far, but both result in core dumps. 1. Compile Python against uClibc and force linking with libboost_python.so 2. Compile Pyhton against uClibc only. Build Boost application by linking against libboost_python.a so no external library is needed. It may be that the 2 libraries are simply not compatible at this stage. Does anyone have any ideas? David Abrahams has suggested low level debugging to work out what is causing the core dump, but if the problem lies deep within uClibc, then I have a problem. Regards, Jeff Gray
"codeazure"
I have tried 2 techniques so far, but both result in core dumps. 1. Compile Python against uClibc and force linking with libboost_python.so 2. Compile Pyhton against uClibc only. Build Boost application by linking against libboost_python.a so no external library is needed.
It may be that the 2 libraries are simply not compatible at this stage.
AFAIK, Boost.Python is not dependent on *any* details of the 'C' library underlying the system, so I can't imagine what kind of compatibility problem there might be. However, if uClibc has its own headers, and you have not built Python or Boost.Python against those headers (e.g. they've been using glibc headers instead), I can see how it would cause a major problem. -- Dave Abrahams Boost Consulting www.boost-consulting.com
participants (2)
-
codeazure
-
David Abrahams