[Kroupware] Compiling imapd and postfix fails

[Henning Holtschneider]

--On Sonntag, 29. Dezember 2002 21:47 +0100 Poul M=F8ller Hansen=20
<pmh@teleservice.com> wrote:

> The system is a SuSE 8.1. I have attached the output of compiling imapd.
> To me it seems as it can't find the sasl libraries although it is
> installed  according to this list:

[---- schnipp ----]
/kolab/bin/cc -L/kolab/lib -Wl,-rpath,/kolab/lib -L/kolab/lib=20
-L/usr/local/lib -Wl,-rpath,/usr/local/lib -L/kolab/lib -L/kolab/lib -Wall=20
-O -I/kolab/include -Ino/include   -o imapd \
 ../master/service.o pushstats.o backend.o imapd.o index.o tls.o version.o=20
libimap.a ../acap/libacap.a ../lib/libcyrus.a  -L/kolab/lib=20
/kolab/lib/libsasl2.a    -ldl -lfl  -ldb3  -lssl -lcrypto -lresolv=20
../et/libcom_err.a -lwrap -lnsl
/kolab/lib/libsasl2.a(otp.o): In function `opie_server_mech_step':
otp.o(.text+0x98e): undefined reference to `opiechallenge'
otp.o(.text+0xa92): undefined reference to `opieverify'
/kolab/lib/libsasl2.a(otp.o): In function `opie_server_mech_dispose':
otp.o(.text+0xba9): undefined reference to `opieverify'
collect2: ld returned 1 exit status
make[1]: *** [imapd] Error 1
make: *** [all] Error 1
error: Bad exit status from /kolab/RPM/TMP/rpm-tmp.37297 (%build)
[---- schnapp ----]

Do you have another libsasl in /usr/local/lib? That's the only path the=20
compiler looks for when building imapd (other than the stuff inside the=20
kolab environment). Did the sasl package build without errors?

opiechallenge/opieverify are part of the sasl package but at least on my=20
machine, "strings /kolab/lib/sasl/* | grep opie" finds no matches.

Regards,
hh