Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com Date: Thu, 15 Nov 2001 12:04:08 +0100 From: "Gerrit P. Haase" X-Mailer: The Bat! (v1.53t) Business Reply-To: "Gerrit P. Haase" Organization: convey Information Systems GmbH X-Priority: 3 (Normal) Message-ID: <1111745509.20011115120408@familiehaase.de> To: Peter Ring CC: cygwin AT cygwin DOT com Subject: Re: AW: libxml2.dll, libxslt.dll, problems with executables linke d to dll's In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Hallo Peter, 2001-11-15 11:59:48, du schriebst: > libxml2/libxslt builds out of the box for me. > I build from cvs sources. > I have not tried building with shared libraries. Yes, but I need them shared:( I get stackdumps e.g. for $ xsltproc -V and that is bad. > You need recent autoconf/automake/libtool though. > Canonical site > http://www.gnu.org/software/libtool/ > There's a number of libtool ports available: > Are there any advantages to any of these? Mine is build from unpatched 1.4.2 source, builds OOTB passes all tests, this version uses dlltool et al to build dll's in the old style, but it still works (sometimes). > Are there any advantages to building libtool from the 1.4.2 source? It should be no difference if you pick mine or build it yourself. The patched version may be a little bit easier to handle because some incompatibilities between the autotools which were adressed there. Gerrit -- convey Information Systems GmbH http://www.convey.de/ Vitalisstraße 326-328 Gerrit P. Haase D-50933 Köln gerrit DOT haase AT convey DOT de Fon: ++49 221 6903922 -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/