DG/UX
Matthias Andree
matthias.andree at gmx.de
Mon Dec 15 01:05:53 CET 2003
Dave Lovelace <dave at firstcomp.biz> writes:
> OK, that was little if any improvement. The unresolved-symbol errors do
> not go away.
I tend to believe it's a problem with compiler, assembler or linker. It
all looks as though internal branch labels were exposed.
And I've found something related on the web:
http://gcc.gnu.org/ml/gcc/2002-01/msg00086.html
which says, summarized "dwarf-1 debugging format is not well-tested and
may not work well". I suspect dwarf-1 might be the default format for
M88K DGUX compilers and we might actually see this bug.
Dave, could you try this:
rm -f config.cache
env CFLAGS="-O" ./configure
make
make check
and see if *that* works? The default for CFLAGS is "-O2 -g" and IF your
system uses dwarf-1 as default debugging format, this may cause
troubles.
If the -O works, you can retry with -O2 to get faster code.
If -O works but not -O2, please retry with -O -g and let us know which
of the three combinations you have tried and which have worked or
failed:
-O
-O2
-O -g
-O2 -g: FAILED (this is the ./configure default for gcc compilers)
--
Matthias Andree
Encrypt your mail: my GnuPG key ID is 0x052E7D95
More information about the Bogofilter
mailing list