On Wed, Jan 28, 2004, Christopher M. O'Malley wrote:
> Building sasl-2.1.17-20040126.src.rpm with login and ldap support
> results in:
>
> lak.c:60:23: sasl/sasl.h: No such file or directory
> lak.c: In function `lak_sasl_interact':
> lak.c:947: error: `sasl_interact_t' undeclared (first use in this
> function)
> lak.c:947: error: (Each undeclared identifier is reported only once
> lak.c:947: error: for each function it appears in.)
> lak.c:947: error: `in' undeclared (first use in this function)
> lak.c:951: error: `SASL_CB_LIST_END' undeclared (first use in this
> function)
> lak.c:954: error: `SASL_CB_AUTHNAME' undeclared (first use in this
> function)
> lak.c:960: error: `SASL_CB_USER' undeclared (first use in this function)
> lak.c:966: error: `SASL_CB_GETREALM' undeclared (first use in this
> function)
> lak.c:970: error: `SASL_CB_PASS' undeclared (first use in this function)
> lak.c: In function `lak_check_crypt':
> lak.c:1712: warning: assignment makes pointer from integer without a
> cast
> make[3]: *** [lak.o] Error 1
> make[2]: *** [all] Error 2
> make[1]: *** [all-recursive] Error 1
> make: *** [all] Error 2
>
> any ideas?
Good catch. Cyrus SASL 2.1.17 was broken. I've fixed it
in sasl-2.1.17-20040128. Thanks for the feedback.
Ralf S. Engelschall
[EMAIL PROTECTED]
www.engelschall.com
______________________________________________________________________
The OpenPKG Project www.openpkg.org
User Communication List [EMAIL PROTECTED]
