On Friday, March 27, 2020 at 1:34:54 PM UTC-5,
benjami...@gmail.com wrote:
On Friday, December 2, 2005 at 11:23:36 AM UTC+5:30, smiletolead wrote:
file libxml2.a gives the output:
libxml2.a: archive (big format)
while 'ar -t libxml2.a' gives the output:
libxml2.so.2
I wanted to have three libraries out of libxml2.a: libxml2.so,
libxml2.so.2 and libxml2.so.2.6.20. Libxml2.so and libxml2.so.2 are symbolic links and libxml2.so.2.6.20 is the actual library. I renamed libxml2.a as libxml2.so, because I am not clear with the naming
convention of .a files. That is, i don't know how to name the physical library and the symbolic links of .a libraries.
If I rename libxml2.a as libxml2.so I face one problem. There is a
software libxslt, which I am building from its source. It links with libxml2 library while building. But it is unable link with libxml2.so.
But it links properly with libxml2.a
Hi,
I am trying to build the library as well. Can you please tell what are compiler flags/options you used?
--enable-shared does not create a shared library for me
--enable-shared is a Libtool flag passed to configure.
By default on AIX, it will generate an AIX shared library - with a name like - libxml2.a
AIX also has System V compatibility libraries, libFOO.so, to make Libtool generate those, you'll need to have '-brtl' in your linker flags when you configure.
For C:
LDFLAGS="-brtl"
For C++:
LDFLAGS="-Wl,-brtl"
Libtool looks for the presence of this flag, and switches to creating a "libX.so" file instead
--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)