Package: libldap2
Version: 2.1.30.dfsg-13.5
Severity: serious
Justification: no longer builds from source


Hi,

Got myself a new laptop and went about compiling libldap2 from scratch[1] and
found the following error hitting me when compiling:

=======
[EMAIL PROTECTED]:/usr/src/deb-src/libldap2/openldap2-2.1.30.dfsg$ 
dpkg-buildpackage -us -uc -rfakeroot
[snipped]
checking for cxx... no
checking for cc++... no
checking for cl... no
checking for FCC... no
checking for KCC... no
checking for RCC... no
checking for xlC_r... no
checking for xlC... no
checking whether we are using the GNU C++ compiler... no
checking whether g++ accepts -g... no
checking how to run the C++ preprocessor... /lib/cpp
configure: error: C++ preprocessor "/lib/cpp" fails sanity check
See `config.log' for more details.
make: *** 
[/usr/src/deb-src/libldap2/openldap2-2.1.30.dfsg/debian/build/Makefile] Error 1
dpkg-buildpackage: failure: debian/rules build gave error exit status 2
[EMAIL PROTECTED]:/usr/src/deb-src/libldap2/openldap2-2.1.30.dfsg$ 
=======

The config.log reported that it could not find 'cc1plus' (provided by 'g++').  
Once
installed it compiles with no  problems.

Cheers

Alex

[1] I am also affected by bugs #262539 and #364614 and have to apply the patch
        they describe otherwise I suffer long hangs

-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 2.6.24-rc7 (SMP w/2 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages libldap2 depends on:
ii  libc6                    2.7-6           GNU C Library: Shared libraries
ii  libgnutls13              2.0.4-1         the GNU TLS library - runtime libr
ii  libsasl2-2               2.1.22.dfsg1-17 Cyrus SASL - authentication abstra

libldap2 recommends no packages.

-- no debconf information



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to