Building gdb on IA64 linux

Building gdb on IA64 linux

[Steve Ellcey]

Jeff,

I can now build gdb on IA64 without using libunwind, but when I try
to use libunwind, I get:

/extra/sje/gdb/src/gdb/ia64-tdep.c: In function 'ia64_find_unwind_table':
/extra/sje/gdb/src/gdb/ia64-tdep.c:2585: error: 'UNW_INFO_FORMAT_REMOTE_TABLE' undeclared (first use in this function)
/extra/sje/gdb/src/gdb/ia64-tdep.c:2585: error: (Each undeclared identifier is reported only once
/extra/sje/gdb/src/gdb/ia64-tdep.c:2585: error: for each function it appears in.)
/extra/sje/gdb/src/gdb/ia64-tdep.c:2586: error: 'union <anonymous>' has no member named 'rti'
/extra/sje/gdb/src/gdb/ia64-tdep.c:2587: error: 'union <anonymous>' has no member named 'rti'
/extra/sje/gdb/src/gdb/ia64-tdep.c:2588: error: 'union <anonymous>' has no member named 'rti'
/extra/sje/gdb/src/gdb/ia64-tdep.c: In function 'ia64_find_proc_info_x':
/extra/sje/gdb/src/gdb/ia64-tdep.c:2633: error: 'union <anonymous>' has no member named 'rti'
/extra/sje/gdb/src/gdb/ia64-tdep.c:2634: error: 'union <anonymous>' has no member named 'rti'
/extra/sje/gdb/src/gdb/ia64-tdep.c:2637: error: 'union <anonymous>' has no member named 'rti'
/extra/sje/gdb/src/gdb/ia64-tdep.c:2638: error: 'union <anonymous>' has no member named 'rti'

What is UNW_INFO_FORMAT_REMOTE_TABLE?  Do I need a new libunwind to get
this macro?  I am on a redhat 2.6 and I don't have libunwind on my
system but I am using GCC 4.0 and it has an unwind.h and a libunwind.so
in the location where I built it.  But, this unwind.h does not have a
definition of UNW_INFO_FORMAT_REMOTE_TABLE.

Steve Ellcey
sje@cup.hp.com

Re: Building gdb on IA64 linux

[Jeff Johnston]

Steve Ellcey wrote:
> Jeff,
> 
> I can now build gdb on IA64 without using libunwind, but when I try
> to use libunwind, I get:
> 
> /extra/sje/gdb/src/gdb/ia64-tdep.c: In function 'ia64_find_unwind_table':
> /extra/sje/gdb/src/gdb/ia64-tdep.c:2585: error: 'UNW_INFO_FORMAT_REMOTE_TABLE' undeclared (first use in this function)
> /extra/sje/gdb/src/gdb/ia64-tdep.c:2585: error: (Each undeclared identifier is reported only once
> /extra/sje/gdb/src/gdb/ia64-tdep.c:2585: error: for each function it appears in.)
> /extra/sje/gdb/src/gdb/ia64-tdep.c:2586: error: 'union <anonymous>' has no member named 'rti'
> /extra/sje/gdb/src/gdb/ia64-tdep.c:2587: error: 'union <anonymous>' has no member named 'rti'
> /extra/sje/gdb/src/gdb/ia64-tdep.c:2588: error: 'union <anonymous>' has no member named 'rti'
> /extra/sje/gdb/src/gdb/ia64-tdep.c: In function 'ia64_find_proc_info_x':
> /extra/sje/gdb/src/gdb/ia64-tdep.c:2633: error: 'union <anonymous>' has no member named 'rti'
> /extra/sje/gdb/src/gdb/ia64-tdep.c:2634: error: 'union <anonymous>' has no member named 'rti'
> /extra/sje/gdb/src/gdb/ia64-tdep.c:2637: error: 'union <anonymous>' has no member named 'rti'
> /extra/sje/gdb/src/gdb/ia64-tdep.c:2638: error: 'union <anonymous>' has no member named 'rti'
> 
> What is UNW_INFO_FORMAT_REMOTE_TABLE?  Do I need a new libunwind to get
> this macro?  I am on a redhat 2.6 and I don't have libunwind on my
> system but I am using GCC 4.0 and it has an unwind.h and a libunwind.so
> in the location where I built it.  But, this unwind.h does not have a
> definition of UNW_INFO_FORMAT_REMOTE_TABLE.
> 
> Steve Ellcey
> sje@cup.hp.com
>

Yes, you must have libunwind installed as there are header files installed which 
are needed when building gdb.

There is a check in configure.ac: AC_CHECK_HEADERS(libunwind-ia64.h) that will 
set HAVE_LIBUNWIND_IA64_H.  This flag protects the references to libunwind 
macros/functions in ia64-tdep.c.  Did you go around this check?

-- Jeff J.

Re: Building gdb on IA64 linux

[Steve Ellcey]

> There is a check in configure.ac: AC_CHECK_HEADERS(libunwind-ia64.h) that will 
> set HAVE_LIBUNWIND_IA64_H.  This flag protects the references to libunwind 
> macros/functions in ia64-tdep.c.  Did you go around this check?
> 
> -- Jeff J.

I did not do anything to disable the check, I just let everything
default.  I finally noticed that I do have a libunwind, it is over
in /usr/local/lib instead of /usr/lib.  That is why I didn't see it
before.  I don't see a version number but the latest copyright date
is from 2003 so it is probably just too old.

Steve Ellcey
sje@cup.hp.com

Re: Building gdb on IA64 linux

[Jeff Johnston]

Steve Ellcey wrote:
>>There is a check in configure.ac: AC_CHECK_HEADERS(libunwind-ia64.h) that will 
>>set HAVE_LIBUNWIND_IA64_H.  This flag protects the references to libunwind 
>>macros/functions in ia64-tdep.c.  Did you go around this check?
>>
>>-- Jeff J.
> 
> 
> I did not do anything to disable the check, I just let everything
> default.  I finally noticed that I do have a libunwind, it is over
> in /usr/local/lib instead of /usr/lib.  That is why I didn't see it
> before.  I don't see a version number but the latest copyright date
> is from 2003 so it is probably just too old.
> 
> Steve Ellcey
> sje@cup.hp.com
>

Yes, it is too old.  Red Hat's gdb rpm has a prereq for libunwind, but now that 
you bring this up, the prereq needs to be updated.  As well, a configure check 
is needed for regular gdb to ensure the right level of libunwind is around.  I 
suggest you upgrade to the latest libunwind rpm.

-- Jeff J.

Re: Building gdb on IA64 linux

[Jeff Johnston]

Jeff Johnston wrote:
> Steve Ellcey wrote:
> 
>>> There is a check in configure.ac: AC_CHECK_HEADERS(libunwind-ia64.h) 
>>> that will set HAVE_LIBUNWIND_IA64_H.  This flag protects the 
>>> references to libunwind macros/functions in ia64-tdep.c.  Did you go 
>>> around this check?
>>>
>>> -- Jeff J.
>>
>>
>>
>> I did not do anything to disable the check, I just let everything
>> default.  I finally noticed that I do have a libunwind, it is over
>> in /usr/local/lib instead of /usr/lib.  That is why I didn't see it
>> before.  I don't see a version number but the latest copyright date
>> is from 2003 so it is probably just too old.
>>
>> Steve Ellcey
>> sje@cup.hp.com
>>
> 
> Yes, it is too old.  Red Hat's gdb rpm has a prereq for libunwind, but 
> now that you bring this up, the prereq needs to be updated.  As well, a 
> configure check is needed for regular gdb to ensure the right level of 
> libunwind is around.  I suggest you upgrade to the latest libunwind rpm.
>

Actually on retrospect, it make more sense to put checks in ia64-tdep.c based on 
libunwind header internals.

-- Jeff J.