[Date Prev][Date Next]
Re: servers/slapd/tools/ldif2index won't compile (ITS#298)
> Full_Name: Darcy Quesnel
> Version: OpenLDAP 1.2 Stable
> OS: Linux bart.mcs.anl.gov 2.2.10 #1 SMP Wed Jul 7 10:07:01 CDT 1999 i686 unknown
> URL: ftp://ftp.openldap.org/incoming/
> Submission from: (NULL) (126.96.36.199)
> gcc -g -O2 -I../../../include -I../../../include -DHAVE_CONFIG_H
> -L/homes/quesnel/pkgs/ldap/libraries -o ldif2index ldif2index.o ../config.o
> ../ch_malloc.o ../backend.o ../charray.o ../aclparse.o ../schema.o ../result.o
> ../filterentry.o ../acl.o ../phonetic.o ../attr.o ../value.o ../entry.o ../dn.o
> ../filter.o ../str2filter.o ../ava.o ../init.o ../schemaparse.o ../libbackends.a
> -lavl -lldif -lldap -llber -lldbm -llthread -llutil -lgdbm -lcrypt -lresolv
> gcc: Internal compiler error: program ld got fatal signal 11
> make: *** [ldif2index] Error 1
> Worked around it by compiling base64.c without both the -g and -O2 flags.
It may be a compiler bug specific to the version you are using, but it is
public knowledge (it is even documented in some FAQs) that signal 11 while
compiling is the fingerprint of a memory subsystem problem: either some of
your memory chips are not up to spec or something related: overclocking,
temperature too high, chipset settings in BIOS, etc.
Can you build a new kernel on that computer? It is a good memory test,
if kernel build fails with signal 11 it is typically because of memory
problems. The system may seem to work perfectly otherwise (and even
pass with flying colors memory tests done with CheckIt and the like).
If however, the kernel build succeeds but OpenLDAP build fails, then you
are onto something, but I don't think it is an OpenLDAP fault and you
should report it to your compiler supplier or to the maintainers. If a
C source crashes a compiler, it is the compiler's fault. It it sees
something it does not like, it should complain loudly, not crash.
Crashing is not an option for any program.