Please test RE24.
Thanks!
--Quanah
--
Quanah Gibson-Mount Principal Software Engineer Zimbra, Inc -------------------- Zimbra :: the leader in open source messaging and collaboration
Am Thu, 10 Jun 2010 13:09:58 -0700 schrieb Quanah Gibson-Mount quanah@zimbra.com:
Please test RE24.
OK on openSUSE-11.2 i686, with db 4.8.26
-Dieter
On 06/11/2010 12:09 AM, Quanah Gibson-Mount wrote:
Please test RE24.
Thanks!
--Quanah
--
Quanah Gibson-Mount Principal Software Engineer Zimbra, Inc
Zimbra :: the leader in open source messaging and collaboration
Hello,
I've just got the source code from the cvs and installed it locally (configure with no parameters). After installation I've found this: libldap-2-devel.so.0.0.0: undefined reference to `lutil_atoix'
readelf -Wa libldap-2-devel.so.0.0.0 | grep lutil_atoix: 00047088 00001007 R_386_JUMP_SLOT 00000000 lutil_atoix 16: 00000000 0 NOTYPE GLOBAL DEFAULT UND lutil_atoix 602: 00000000 0 NOTYPE GLOBAL DEFAULT UND lutil_atoix
Is it normally? The previous release 2.4.22 hasn't this symbol dependency. My environment is openSUSE 11.2, x86.
--On Friday, June 11, 2010 7:10 PM +0400 Andrey Ponomarenko susanin@ispras.ru wrote:
On 06/11/2010 12:09 AM, Quanah Gibson-Mount wrote:
Please test RE24.
Thanks!
--Quanah
--
Quanah Gibson-Mount Principal Software Engineer Zimbra, Inc
Zimbra :: the leader in open source messaging and collaboration
Hello,
I've just got the source code from the cvs and installed it locally (configure with no parameters). After installation I've found this: libldap-2-devel.so.0.0.0: undefined reference to `lutil_atoix'
readelf -Wa libldap-2-devel.so.0.0.0 | grep lutil_atoix: 00047088 00001007 R_386_JUMP_SLOT 00000000 lutil_atoix 16: 00000000 0 NOTYPE GLOBAL DEFAULT UND lutil_atoix 602: 00000000 0 NOTYPE GLOBAL DEFAULT UND lutil_atoix
Is it normally? The previous release 2.4.22 hasn't this symbol dependency. My environment is openSUSE 11.2, x86.
[quanah@freelancer src]$ cd openldap-2.4.22/libraries/liblutil/ [quanah@freelancer liblutil]$ grep atoix * utils.c:lutil_atoix( int *v, const char *s, int x )
OpenLDAP 2.4.22 definitely had this function in it. In any case, are you sure you're compiling the 2.4 branch and not HEAD?
--Quanah
--
Quanah Gibson-Mount Principal Software Engineer Zimbra, Inc -------------------- Zimbra :: the leader in open source messaging and collaboration
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 6/10/10 22:09 , Quanah Gibson-Mount wrote:
Please test RE24.
Thanks!
I'm getting a build error during "make" on OS X 10.6.3/Intel that I haven't seen during previous calls for RE24 testing:
gcc-4.2 -march=x86-64 -isystem /usr/local/BerkeleyDB.4.7/include - -L/usr/local/BerkeleyDB.4.7/lib -L/usr/local/BerkeleyDB.4.7/lib -g -O2 - -I../../include -I../../include -DLDAP_LIBRARY -c cyrus.c -fno-common - -DPIC -o .libs/cyrus.o cyrus.c: In function 'ldap_int_sasl_get_option': cyrus.c:1056: error: 'SASL_GSS_CREDS' undeclared (first use in this function) cyrus.c:1056: error: (Each undeclared identifier is reported only once cyrus.c:1056: error: for each function it appears in.) cyrus.c: In function 'ldap_int_sasl_set_option': cyrus.c:1155: error: 'SASL_GSS_CREDS' undeclared (first use in this function) make[2]: *** [cyrus.lo] Error 1 make[1]: *** [all-common] Error 1 make: *** [all-common] Error 1
I'm guessing there were SASL-related changes that mean the standard system stuff on OS X is no longer sufficient?
jens
Jens Vagelpohl wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 6/10/10 22:09 , Quanah Gibson-Mount wrote:
Please test RE24.
Thanks!
I'm getting a build error during "make" on OS X 10.6.3/Intel that I haven't seen during previous calls for RE24 testing:
gcc-4.2 -march=x86-64 -isystem /usr/local/BerkeleyDB.4.7/include
- -L/usr/local/BerkeleyDB.4.7/lib -L/usr/local/BerkeleyDB.4.7/lib -g -O2
- -I../../include -I../../include -DLDAP_LIBRARY -c cyrus.c -fno-common
- -DPIC -o .libs/cyrus.o
cyrus.c: In function 'ldap_int_sasl_get_option': cyrus.c:1056: error: 'SASL_GSS_CREDS' undeclared (first use in this function) cyrus.c:1056: error: (Each undeclared identifier is reported only once cyrus.c:1056: error: for each function it appears in.) cyrus.c: In function 'ldap_int_sasl_set_option': cyrus.c:1155: error: 'SASL_GSS_CREDS' undeclared (first use in this function) make[2]: *** [cyrus.lo] Error 1 make[1]: *** [all-common] Error 1 make: *** [all-common] Error 1
I'm guessing there were SASL-related changes that mean the standard system stuff on OS X is no longer sufficient?
SASL_GSS_CREDS has been part of Cyrus SASL since April 2006. I guess we can put an #ifdef around this code, but really, you need to get up to date. There've been a lot of fixes in Cyrus since then...
--On Saturday, June 12, 2010 12:57 PM -0700 Howard Chu hyc@symas.com wrote:
Jens Vagelpohl wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 6/10/10 22:09 , Quanah Gibson-Mount wrote:
Please test RE24.
Thanks!
I'm getting a build error during "make" on OS X 10.6.3/Intel that I haven't seen during previous calls for RE24 testing:
gcc-4.2 -march=x86-64 -isystem /usr/local/BerkeleyDB.4.7/include
- -L/usr/local/BerkeleyDB.4.7/lib -L/usr/local/BerkeleyDB.4.7/lib -g -O2
- -I../../include -I../../include -DLDAP_LIBRARY -c cyrus.c -fno-common
- -DPIC -o .libs/cyrus.o
cyrus.c: In function 'ldap_int_sasl_get_option': cyrus.c:1056: error: 'SASL_GSS_CREDS' undeclared (first use in this function) cyrus.c:1056: error: (Each undeclared identifier is reported only once cyrus.c:1056: error: for each function it appears in.) cyrus.c: In function 'ldap_int_sasl_set_option': cyrus.c:1155: error: 'SASL_GSS_CREDS' undeclared (first use in this function) make[2]: *** [cyrus.lo] Error 1 make[1]: *** [all-common] Error 1 make: *** [all-common] Error 1
I'm guessing there were SASL-related changes that mean the standard system stuff on OS X is no longer sufficient?
SASL_GSS_CREDS has been part of Cyrus SASL since April 2006. I guess we can put an #ifdef around this code, but really, you need to get up to date. There've been a lot of fixes in Cyrus since then...
Fix applied to RE24 now.
--Quanah
--
Quanah Gibson-Mount Principal Software Engineer Zimbra, Inc -------------------- Zimbra :: the leader in open source messaging and collaboration
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 6/13/10 00:06 , Quanah Gibson-Mount wrote:
--On Saturday, June 12, 2010 12:57 PM -0700 Howard Chu hyc@symas.com wrote:
Jens Vagelpohl wrote:
cyrus.c:1155: error: 'SASL_GSS_CREDS' undeclared (first use in this function)
SASL_GSS_CREDS has been part of Cyrus SASL since April 2006. I guess we can put an #ifdef around this code, but really, you need to get up to date. There've been a lot of fixes in Cyrus since then...
Fix applied to RE24 now.
Thanks, it works now and all tests pass (OS X 10.6.3/Intel x86-64).
I'm only using this system for running the tests, by the way - it's my laptop. In production I'd use a Linux system, anyway.
The stock SASL componentry included in OS X 10.6 claims to be 2.1.22, and the sasl.h header file has no definition for SASL_GSS_CREDS. On the other hand, a CentOS/RHEL 5 server I looked at also claims to have syrus-sasl version 2.1.22, yet it contains the definition.
jens
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
On -28163/01/-10 11:59, Quanah Gibson-Mount wrote:
Please test RE24.
All tests succeeded on FreeBSD 9-CURRENT/amd64.
Cheers, - -- Xin LI delphij@delphij.net http://www.delphij.net/ FreeBSD - The Power to Serve! Live free or die
On 06/11/2010 12:09 AM, Quanah Gibson-Mount wrote:
Please test RE24.
Thanks!
Hello,
We have obtained some sanity test results for the OPENLDAP_REL_ENG_2_4 revision in our Upstream Tracker: http://linuxtesting.org/upstream-tracker/versions/openldap.html
May be it will be useful.
Andrey Ponomarenko wrote:
On 06/11/2010 12:09 AM, Quanah Gibson-Mount wrote:
Please test RE24.
Thanks!
Hello,
We have obtained some sanity test results for the OPENLDAP_REL_ENG_2_4 revision in our Upstream Tracker: http://linuxtesting.org/upstream-tracker/versions/openldap.html
May be it will be useful.
Thanks. If you find any real bugs, you should report them to the ITS.
I looked at a couple of the failures in your test results; your test programs are not using the APIs as they are intended to be used. Since you provide invalid/uninitialized inputs, there are naturally going to be crashes - garbage in, garbage out.