On Sat, Sep 03, 2005 at 04:12:43PM +0200, Domenico Andreoli wrote:
> On Fri, Sep 02, 2005 at 04:04:27AM -0700, Steve Langasek wrote:
> > On Fri, Sep 02, 2005 at 12:24:18PM +0200, Domenico Andreoli wrote:
> > > > > - libcurl3 (GnuTLS, soname: libcurl.so.3)
> > > > So the libcurl3 in
On Fri, Sep 02, 2005 at 04:04:27AM -0700, Steve Langasek wrote:
> On Fri, Sep 02, 2005 at 12:24:18PM +0200, Domenico Andreoli wrote:
> > > > - libcurl3 (GnuTLS, soname: libcurl.so.3)
>
> > > So the libcurl3 in sarge and etch will have ABI incompatibilities?
>
> > at the release ti
On Sep 02, Paul TBBle Hampson <[EMAIL PROTECTED]> wrote:
> If I've understood correctly, it is because curl expects the client program
> or library to -lgnutls or -lopenssl and therefore provide the SSL symbols
> to match the symbols which that build of the .so file is expecting.
I hope not, this
On Fri, Sep 02, 2005 at 04:04:27AM -0700, Steve Langasek wrote:
> On Fri, Sep 02, 2005 at 12:24:18PM +0200, Domenico Andreoli wrote:
> > >> - libcurl3 (GnuTLS, soname: libcurl.so.3)
> But no one has yet answered my question: *why* are there ABI differences
> between the gnutls and op
On Fri, Sep 02, 2005 at 12:24:18PM +0200, Domenico Andreoli wrote:
> > > - libcurl3 (GnuTLS, soname: libcurl.so.3)
> > So the libcurl3 in sarge and etch will have ABI incompatibilities?
> at the release time of etch this problem will regard only
> external software. this kind of i
On Fri, Sep 02, 2005 at 11:56:13AM +0200, Adeodato Simó wrote:
> * Domenico Andreoli [Fri, 02 Sep 2005 11:16:28 +0200]:
>
> > - libcurl3-dev (OpenSSL, depends: libssl-dev)
> > - libcurl3-openssl-dev (GnuTLS, depends: libgnutls-dev)
>
> Obvious typo/whatever here, right?
On Fri, Sep
6 matches
Mail list logo
