1 May 2003 05:11
IMAPD, SASL and sasl_checkapop
Diego Rivera <lrivera <at> racsa.co.cr>
2003-05-01 03:11:27 GMT
2003-05-01 03:11:27 GMT
Hello all!
I've tried to install the kolab server, and have been successful in building all but two of the packages that need to install (I'm using Mandrake 9.0, for the test install - future tests will be on RHAS and other distros).
The two packages are imap and kolab - kolab requires imap, so I can't say if it would compile correctly or not until I can compile imap.
The error I get is when imap is running "configure":
--- ERROR ---
checking for sasl_checkapop in -lsasl2... no
configure: error: libsasl2 without working sasl_checkapop. Cannot continue.
error: Bad exit status from /kolab/RPM/TMP/rpm-tmp.25769 (%build)
- END ERROR -
I tried to explicitly set '--enable-checkapop' in sasl's spec file (for when sasl runs configure), and it still failed.
Can anyone offer a clue as to why this is happening? Perhaps it's linking against the wrong SASL (i.e., the one on the outer system vs. the kolab-specific one)?
Also, you should mention on the QIM that glibc-static needs to be present on the system to build openldap, sasl and postfix - otherwise these will fail with strange "lib not found" errors.
Best
I've tried to install the kolab server, and have been successful in building all but two of the packages that need to install (I'm using Mandrake 9.0, for the test install - future tests will be on RHAS and other distros).
The two packages are imap and kolab - kolab requires imap, so I can't say if it would compile correctly or not until I can compile imap.
The error I get is when imap is running "configure":
--- ERROR ---
checking for sasl_checkapop in -lsasl2... no
configure: error: libsasl2 without working sasl_checkapop. Cannot continue.
error: Bad exit status from /kolab/RPM/TMP/rpm-tmp.25769 (%build)
- END ERROR -
I tried to explicitly set '--enable-checkapop' in sasl's spec file (for when sasl runs configure), and it still failed.
Can anyone offer a clue as to why this is happening? Perhaps it's linking against the wrong SASL (i.e., the one on the outer system vs. the kolab-specific one)?
Also, you should mention on the QIM that glibc-static needs to be present on the system to build openldap, sasl and postfix - otherwise these will fail with strange "lib not found" errors.
Best
| -- -- =========================================================== * Diego Rivera * * * * "The Disease: Windows, the cure: Linux" * * * * E-mail: lrivera <at> racsa.co.cr * * GPG: BE59 5469 C696 C80D FF5C 5926 0B36 F8FF DA98 62AD * * GPG Public Key avaliable at: http://pgp.mit.edu * =========================================================== |
_______________________________________________ Kroupware mailing list Kroupware <at> mail.kde.org http://mail.kde.org/mailman/listinfo/kroupware
RSS Feed