Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Marcel Moolenaar <marcel@cup.hp.com>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: brobecker@adacore.com, gdb-patches@sources.redhat.com
Subject: Re: [RFC] link GDB against libunwind-ia64
Date: Fri, 12 Aug 2005 17:13:00 -0000	[thread overview]
Message-ID: <086DD99C-38DE-42F1-8F85-64A71EC36F1B@cup.hp.com> (raw)
In-Reply-To: <200508120805.j7C85nrW021087@elgar.sibelius.xs4all.nl>

On Aug 12, 2005, at 1:05 AM, Mark Kettenis wrote:

>> Date: Thu, 11 Aug 2005 15:23:23 -0700
>> From: Joel Brobecker <brobecker@adacore.com>
>>
>> Hello,
>>
>> So I'd like to add an option so that GDB is explicitly linked against
>> libunwind-ia64, instead of using dlopen(). As a bonus, this may  
>> simplify
>> our work in terms of binary distribution...
>>
>
> If libunwind-ia64 is always available on ia64-*-hpux*, we really
> should simply link against it.

There's a libunwind on HP-UX that's part of the system, but it doesn't
have a libunwind-ia64 component. The libunwind-ia64 shared object is an
implementation detail of David Mosberger's library. Since we're talking
about libunwind-ia64, I can only assume that we're talking about David's
library. That library is not always available in the general case.

Still, I think it's good to be able to link against libunwind. It really
should be present on any ia64 system, irrespective of the OS.

-- 
  Marcel Moolenaar                                marcel@cup.hp.com




  reply	other threads:[~2005-08-12 17:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-11 23:54 Joel Brobecker
2005-08-12  1:28 ` Kevin Buettner
2005-08-12  9:41 ` Mark Kettenis
2005-08-12 17:13   ` Marcel Moolenaar [this message]
2005-08-12 20:31     ` Joel Brobecker
2005-08-15 19:04   ` Joel Brobecker

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=086DD99C-38DE-42F1-8F85-64A71EC36F1B@cup.hp.com \
    --to=marcel@cup.hp.com \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=mark.kettenis@xs4all.nl \
    /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