From: Steve Ellcey <sje@cup.hp.com>
To: jjohnstn@redhat.com
Cc: gdb@sources.redhat.com
Subject: Re: Building gdb on IA64 linux
Date: Tue, 14 Jun 2005 18:35:00 -0000 [thread overview]
Message-ID: <200506141834.LAA23760@hpsje.cup.hp.com> (raw)
In-Reply-To: <42AF1A55.3060202@redhat.com>
> 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
next prev parent reply other threads:[~2005-06-14 18:35 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 [this message]
2005-06-15 17:18 ` Jeff Johnston
2005-06-15 17:40 ` Jeff Johnston
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=200506141834.LAA23760@hpsje.cup.hp.com \
--to=sje@cup.hp.com \
--cc=gdb@sources.redhat.com \
--cc=jjohnstn@redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).