[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [lmi] Upgrading libxml2 and libxslt
From: |
Greg Chicares |
Subject: |
Re: [lmi] Upgrading libxml2 and libxslt |
Date: |
Fri, 15 Jul 2016 18:03:57 +0000 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Icedove/38.8.0 |
On 2016-07-14 16:04, Vadim Zeitlin wrote:
> On Thu, 14 Jul 2016 15:15:15 +0000 Greg Chicares <address@hidden> wrote:
[...]
> GC> > And if we really need to use libxml2 as a DLL, I see only two options:
> GC> >
> GC> > 1. Get and build zlib DLL ourselves too.
> GC> > 2. Use a custom makefile for libxml2 and link in (static) zlib into it.
> GC> >
> GC> > Neither is very appealing but I think (1) is better. Unless we're
> ready to
> GC> > live with a patch to libtool.
> GC>
> GC> How about:
> GC>
> GC> 3. Download an official build, and verify its md5sum
>
> I still prefer (1), but I agree that (3) should work too. The problem with
> it is that of consistency: if we use zlib binary, why not use one for
> libxml2 too? It's also a C library (i.e. doesn't suffer from C++ ABI
> problems), so why build one from sources and not the other? I'd prefer to
> build everything and could live with using binaries for everything, but
> mixing the two seems strange.
Yes, (1) would be best, but it's not trivial to build a shared library:
/tmp[0]$wget http://zlib.net/zlib-1.2.8.tar.gz
/tmp[0]$tar -xvf /cache_for_lmi/downloads/zlib-1.2.8.tar.gz
/tmp[0]$cd zlib-1.2.8
/tmp/zlib-1.2.8[0]$export PATH="/MinGW_/bin:${PATH}"
/tmp/zlib-1.2.8[0]$gcc -dumpversion
4.9.1
/tmp/zlib-1.2.8[0]$./configure
Checking for gcc...
Checking for shared library support...
No shared library support.
Building static library libz.a version 1.2.8 with gcc.
I also tried ideas like:
/tmp/zlib-1.2.8[0]$CC=/MinGW_/bin/gcc ./configure --enable-shared
/tmp/zlib-1.2.8[0]$CC=/MinGW_/bin/i686-w64-mingw32-gcc.exe ./configure
--enable-shared
but I still get "No shared library support". I can't understand what
'configure' is doing here, but perhaps you can spot the problem easily.
Searching the web, I find nothing more helpful than this:
http://blog.gmane.org/gmane.comp.gnu.mingw.user/month=20091201/page=13
| It's just a dozen or so of source files in a single folder, why not
| just try gcc -shared -o myzlib.dll -O2 *.c ?
Here is one alternative that seems to work:
/tmp/zlib-1.2.8[0]$make -f win32/Makefile.gcc
but if we do that, then the process presumably won't work under
GNU/Linux.
- Re: [lmi] Do we have zlib already?, Greg Chicares, 2016/07/12
- Re: [lmi] Do we have zlib already?, Greg Chicares, 2016/07/12
- [lmi] Upgrading libxml2 and libxslt [Was: Do we have zlib already?], Greg Chicares, 2016/07/13
- Re: [lmi] Upgrading libxml2 and libxslt, Vadim Zeitlin, 2016/07/13
- Re: [lmi] Upgrading libxml2 and libxslt, Greg Chicares, 2016/07/14
- Re: [lmi] Upgrading libxml2 and libxslt, Vadim Zeitlin, 2016/07/14
- Re: [lmi] Upgrading libxml2 and libxslt,
Greg Chicares <=
- Re: [lmi] Upgrading libxml2 and libxslt, Vadim Zeitlin, 2016/07/15
- Re: [lmi] Upgrading libxml2 and libxslt, Greg Chicares, 2016/07/15
- Re: [lmi] Upgrading libxml2 and libxslt, Greg Chicares, 2016/07/17
- [lmi] Building shared zlib [Was: Upgrading libxml2 and libxslt], Greg Chicares, 2016/07/15
- Re: [lmi] Building shared zlib, Vadim Zeitlin, 2016/07/15
- Re: [lmi] Building shared zlib, Greg Chicares, 2016/07/15