RE: build breaks at sha1.c for OpenBSD 3.3/sparc64 (ITS#2591)

[hyc@highlandsun.com]

Sounds like a compiler bug. Try upgrading to a newer version of GCC, file a
bug report with the OpenBSD compiler maintainers, and/or, remove the -O
optimization flag when compiling the problem file. Since you've stated that
you have the same problem with BerkeleyDB this is obviously not an OpenLDAP
bug; this ITS will be closed.

  -- Howard Chu
  Chief Architect, Symas Corp.       Director, Highland Sun
  http://www.symas.com               http://highlandsun.com/hyc
  Symas: Premier OpenSource Development and Support

> -----Original Message-----
> From: owner-openldap-bugs@OpenLDAP.org
> [mailto:owner-openldap-bugs@OpenLDAP.org]On Behalf Of
> alex@oldschool.edu
> Sent: Wednesday, June 11, 2003 7:47 PM
> To: openldap-its@OpenLDAP.org
> Subject: build breaks at sha1.c for OpenBSD 3.3/sparc64 (ITS#2591)
>
>
> Full_Name: alex krieger
> Version: 2.1.9
> OS: OpenBSD 3.3/sparc64
> URL: ftp://ftp.openldap.org/incoming/
> Submission from: (NULL) (207.87.83.91)
>
>
> When building for OpenBSD 3.3/sparc64, build process hangs at
> sha1.c on my Ultra
> 1 w/ 160mb of memory and 320mb of swap.  It eats up as much
> CPU time as it can
> grab for nearly an hour (probably much shorter on a faster
> system) and then
> quickly consumes all available memory until killed.  This is
> a plain vanilla
> install with only gdbm 1.8.3 and cyrus-sasl 2.1.11 installed from OBSD
> ports/packages tree.
>
> I built with configure --with-cyrus-sasl --with-tls --enable-spasswd
> --enable-ldbm --with-ldbm-api=gdbm --enable-bdb=no
>
> I would use Berkeley DB instead of GDBM if I could get that
> to build -- it hangs
> also on a sha1-related file and eats all available memory.
>
> I am not using GNUmake.  Using the OBSD version of gcc 2.95.3
> (default).
>