Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Jeff Johnston <jjohnstn@redhat.com>
To: Jeff Johnston <jjohnstn@redhat.com>
Cc: Steve Ellcey <sje@cup.hp.com>, gdb@sources.redhat.com
Subject: Re: Building gdb on IA64 linux
Date: Wed, 15 Jun 2005 17:40:00 -0000	[thread overview]
Message-ID: <42B067EF.5000308@redhat.com> (raw)
In-Reply-To: <42B062B9.7060907@redhat.com>

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.



      reply	other threads:[~2005-06-15 17:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-14 17:26 Steve Ellcey
2005-06-14 17:57 ` Jeff Johnston
2005-06-14 18:35   ` Steve Ellcey
2005-06-15 17:18     ` Jeff Johnston
2005-06-15 17:40       ` Jeff Johnston [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=42B067EF.5000308@redhat.com \
    --to=jjohnstn@redhat.com \
    --cc=gdb@sources.redhat.com \
    --cc=sje@cup.hp.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox