shared-libraries

I want to install lxml module in my unix system, and it doesn't work. the problem is failed to reference symbol: Python 2.6.4 (r264:75706, Sep 12 2010, 18:46:30) [C] on sunos5 Type "help", "copyright", "credits" or "license" for more information. >>> from lxml import etree Traceback (most recent call last): File "<stdin>", line 1, in <module> ImportError: ld.so.1: isapython2.6: fatal: relocation error: file lxml/etree.so: symbol __xmlStructuredErrorContext: referenced symbol not found however, the output of ldd command is: $ ldd lxml/etree.so libxslt.so.1 => /usr/lib/libxslt.so.1 libexslt.so.0

I am creating a shared library from a static library for which I do not have the source code. Many Stack Overflow questions provide answers on how to do that: gcc -shared -o libxxx.so -Wl,--whole-archive libxxx.a -Wl,--no-whole-archive However, some public functions of the static library are included as hidden functions in the shared library: $ nm --defined-only libxxx.a | grep __intel_cpu_indicator_init 0000000000000000 T __intel_cpu_indicator_init $ nm libxxx.so | grep __intel_cpu_indicator_init 00000000030bb160 t __intel_cpu_indicator_init The __intel_cpu_indicator_init symbol went from

I have been using libicu to detect charset in my node app that runs inside of docker, ubuntu. this is done through the module node-icu-charset-detector that uses the libicu-dev package, which I install prior to the npm package. It all worked fine but I suddently get the error module.js:356 Module._extensions[extension](this, filename); ^ Error: libicui18n.so.52: cannot open shared object file: No such file or directory at Module.load (module.js:356:32) at Function.Module._load (module.js:312:12) at Module.require (module.js:364:17) at require (module.js:380:17) at Object.<anonymous> (/app/node

I'm compiling C++ static library with g++ and using the -fPIC option. I must use the -fPIC option because eventually this library will be linked with other static libraries to form a dynamic library. When I test the static library locally, it works completely fine when I don't include the -fPIC option. But as soon as I compile the library with -fPIC, I receive a segmentation fault error at run-time when calling one of the functions. What reasons could including -fPIC to compile a static library cause a segementation fault at run-time? A dynamic library is supposed to be loaded at run-time and