On Mon, Aug 25, 2008 at 10:13:02PM +0200, Thomas Kerkmann wrote:
> Yes, libgsasl is installed in /usr/lib64
>
> So I changed everything to point there
>
> [EMAIL PROTECTED] jabberd-2.2.3]# ./configure --enable-sqlite --enable-ssl \
> --with-extra-include-path=/usr/local/include \
> --with-ex
Yes, libgsasl is installed in /usr/lib64
So I changed everything to point there
[EMAIL PROTECTED] jabberd-2.2.3]# ./configure --enable-sqlite --enable-ssl \
--with-extra-include-path=/usr/local/include \
--with-extra-library-path=/usr/lib64
[EMAIL PROTECTED] jabberd-2.2.3]# cat /etc/ld.so.c
On Mon, Aug 25, 2008 at 08:41:03PM +0200, Thomas Kerkmann wrote:
> Thanks for replying, but nope
>
> [EMAIL PROTECTED] jabberd-2.2.3]# ./configure --enable-sqlite --enable-ssl
> --with-extra-include-path=/usr/local/include
> --with-extra-library-path=/usr/local/lib
>
> checking for string
Thanks for replying, but nope
[EMAIL PROTECTED] jabberd-2.2.3]# ./configure --enable-sqlite --enable-ssl
--with-extra-include-path=/usr/local/include
--with-extra-library-path=/usr/local/lib
checking for stringprep_check_version in -lidn... yes
checking for Libidn version >= 0.3.0... yes
Dnia 2008-08-24, nie o godzinie 17:02 -0700, Ed - 0x1b, Inc. pisze:
> I was thinking that the first step to handling client or server
> certs/credentials is handling the error states in a less generic
> fashion(that is what the additional fields would do right?) - [...]
I was talking about user au
