From: Joel Brobecker <brobecker@adacore.com>
To: Tom Tromey <tromey@redhat.com>
Cc: Jan Kratochvil <jan.kratochvil@redhat.com>, gdb-patches@sourceware.org
Subject: Re: [RFC/ia64] link against libunwind rather than using dlopen
Date: Wed, 29 Jun 2011 16:28:00 -0000 [thread overview]
Message-ID: <20110629162751.GD2407@adacore.com> (raw)
In-Reply-To: <m362np7mv6.fsf@fleche.redhat.com>
> We could make this work if we truly wanted to. It just seems like a lot
> of effort; and building gdb is not so very hard.
I also think that this is unnecessary. The only reason for doing that
is transportability. But in either case, it's easy to achieve,
especially in the libunwind case where we only have to worry about
a couple of SOs, by also copying the libraries. That's what we do
when we distribute GDB with Python enabled.
--
Joel
prev parent reply other threads:[~2011-06-29 16:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-17 16:11 Joel Brobecker
2011-06-22 14:40 ` Tom Tromey
2011-06-22 15:36 ` Joel Brobecker
2011-06-25 18:49 ` Jan Kratochvil
2011-06-28 19:55 ` Tom Tromey
2011-06-29 16:28 ` Joel Brobecker [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=20110629162751.GD2407@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=tromey@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