Commit 36cc83a3 authored by Andrew Cagney's avatar Andrew Cagney
Browse files

* PROBLEMS: Mention hppa2.0-hp-hpux10.20 compile problems.

parent 75205f78
2002-04-15 Andrew Cagney <>
* PROBLEMS: Mention hppa2.0-hp-hpux10.20 compile problems.
2002-04-15 Andrew Cagney <>
* bcache.c: Include <stddef.h> and <stdlib.h> after "defs.h".
Known problems in GDB 5.1.1
Known problems in GDB 5.2
See also the bug database
Contrary to the GDB 5.1.1 announcement, the update did not contain
fixes to a i386 floating point problem. The latest sources do contain
the fix and it will be included in GDB 5.2.
Known problems in GDB 5.1
See also:
Due to a problem (conflicting types) with libiberty/regex.c, GDB 5.1
does not build on HP/UX 10.20 when using the HP supplied compiler.
Due to bit rot, GDB 5.1 does not work on HP/UX 10.20 when built with
Due to a problem with ltconfig and long argument lines, GDB 5.1 does
not configure on HP/UX 11.00.
GDB 5.1 has a number of problems on this platform (Ref PR gdb/237). A
GDB 5.1 built with ``CC="cc -DUSE_LDR_ROUTINES"'' is reported to work
much better.
GDB 5.1 is known to have problems on this platform (encounters an
internal error in the symbol table reader).
There are known problems with building GDB 5.1 using GCC 3.0.x for the
64 bit SPARC target (bad code gen). You could try a development
version of GCC.
gdb/487: The top level make files used to build GDB are not compatible
with HP/UX make. As a workaround, use GNU make.
There are known problems with GDB 5.1's thread support on this
platform. Non-threaded programs should work.
gdb/486: The HP/UX C compiler defaults to K&R mode but GDB only builds
with an ISO C compiler. The top level configuration incorrectly sets
CC to `cc' instead of `cc -Ae'. As a workaround, the correct compiler
can be specified as part of the configuration vis:
$ 'CC=cc -Ae' ./configure
GDB 5.1 assumes that the host C compiler implemends alloca(). GCC is
one such compiler. This problem should be fixed on the trunk.
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment