Your message dated Mon, 6 Jun 2011 19:06:31 +0200
with message-id 
<BANLkTik217biCyK_2jkUQuMKFruNOb89OxO7zSiOhSOB=uh...@mail.gmail.com>
and subject line Re: Bug#629372: libsasl2-dev: Missing file
has caused the Debian Bug report #629372,
regarding libsasl2-dev: Missing file
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
629372: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=629372
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libsasl2-dev
Version: 2.1.24~rc1.dfsg1+cvs2011-05-23-2
Severity: serious
Justification: Policy 8.4

According to http://packages.debian.org/sid/amd64/libsasl2-dev/filelist
the package should contain /usr/lib/libsasl2.la but the file is not
provided in the package. The result is that building other packages
dynamically linking against libsasl2 fails.

-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.39-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/bash

Versions of packages libsasl2-dev depends on:
ii  libc6-d 2.13-4                           Embedded GNU C Library: Developmen
ii  libsasl 2.1.24~rc1.dfsg1+cvs2011-05-23-2 Cyrus SASL - pluggable authenticat

libsasl2-dev recommends no packages.

libsasl2-dev suggests no packages.

-- no debconf information



--- End Message ---
--- Begin Message ---
2011/6/6 Michael Rasmussen <m...@datanom.net>:
> On Mon, 6 Jun 2011 07:42:04 +0200
> Ondřej Surý <ond...@sury.org> wrote:
>
>> Could you please be more specific? Like what and how it failed?
>>
> For one the package list state this file should be included. This is
> obviously an error given the fact that the file was never intended to
> be in the package.
>
> The failing part:
> I am trying to build an application - claws-mail - from source.
> Claws-mail depends on libetpan which adds these parameters to gcc:
>
> $ libetpan-config --libs
> -L/usr/lib -letpan -pthread -lcurl -lexpat -lgnutls -ldb-5.1 -llockfile
> -lsasl2

First - that's a bug on etpan side, it doesn't need to export all
libraries the library depends on, just those you need for linking
(which is only -letpan).

> As you can see libetpan adds -lsasl2 to gcc which causes ld (and
> libtool) to look for the file libsasl2.la which cannot be found any
> more.

No, it does not. The -lsasl2 causes the linker to look for libsasl2.so
(and libsasl2.la if found, but it's not a requirement).

To prove that I have just done:

apt-get build-dep claws-mail
rm /usr/lib/*.la
cd /tmp/buildd/claws-mail-3.7.9
dpkg-buildpackage

And it works like a charm...  I have also tried same thing with
upstream source and I can compile it just fine.

The linker is even smart enough that it adds needed libraries even in
case you link the binary only with -letpan (without all the jingles).

Also the libetpan-dev library itself doesn't include .la files.

> libtool: link: cannot find the library `/usr/lib/libsasl2.la' or
> unhandled argument `/usr/lib/libsasl2.la'

There's no bug on cyrus-sasl2 side, the claws-mail can be compiled OK
without any .la file on the system. Your libtool or another part of
the build chain must be broken.

Or just try doing make distclean; autoreconf -fi; and try building the
claws-mail again.

O.
-- 
Ondřej Surý <ond...@sury.org>


--- End Message ---

Reply via email to