Re: [COMMIT]: ia64 update

[jjohnstn <jjohnstn@redhat.com>]

On Thu, 9 Jun 2005, Steve Ellcey wrote:

> > From: Jeff Johnston <jjohnstn@redhat.com>
> > 
> > A long-overdue update of the ia64 code has been made.  It contains a number of
> > changes worked on by myself and David Mosberger that were only in Red Hat's ia64
> > gdb.
> 
> Is it supposed to be possible to build gdb on IA64 Linux using
> --without-libunwind?  When I tried it I died in the linker with:
> 
> | rm -f gdb
> | //sje/be/bin/gcc -g       \
> |         -o gdb gdb.o libgdb.a \
> |            ../readline/libreadline.a ../opcodes/libopcodes.a ../bfd/libbfd.a  ..
> | /libiberty/libiberty.a     -lncurses -lm  ../libiberty/libiberty.a  -ldl -rdynamic
> | libgdb.a(ia64-tdep.o)(.text+0x2b22): In function `ia64_pseudo_register_read':
> | /extra/sje/gdb/src/gdb/ia64-tdep.c:682: undefined reference to `libunwind_is_initialized'
> | libgdb.a(ia64-tdep.o)(.text+0x2b72):/extra/sje/gdb/src/gdb/ia64-tdep.c:682: undefined reference to `libunwind_get_reg_special'
> | collect2: ld returned 1 exit status
> | make[1]: *** [gdb] Error 1
> | make[1]: Leaving directory `/extra/sje/gdb/obj_gdb/gdb'
> | make: *** [all-gdb] Error 2
> 

Oops.  Yes, it should have built.  It also should have built without
warnings about gdb_byte.  I have just checked in a subsequent patch
for both problems.

I don't recommend using ia64 gdb without libunwind.

-- Jeff J.