From: Tom Tromey <tromey@redhat.com>
To: gdb-patches@sourceware.org
Subject: [RFC 0/2] let gdbserver use libiberty
Date: Mon, 20 Jan 2014 18:49:00 -0000 [thread overview]
Message-ID: <1390243792-31176-1-git-send-email-tromey@redhat.com> (raw)
This series changes gdbserver to build its own copy of libiberty
(using ACX_CONFIGURE_DIR) and then link against it. I've needed this
at least once (for a cloexec patch) and I've seen other situations
where it would have been useful.
This is of course not the ideal way to depend on libiberty -- better
would be to use the same build that gdb uses. However, due to the
requirement that gdbserver be separately configurable, this is the
best that can be done immediately.
FWIW I do have a branch to move common, gnulib, and gdbserver to
top-level. However, that branch still has some issues to be sorted
out (namely, what to rename "common", and how to compute the
definition of CORE_ADDR); and in any case a patch like this one would
be required at some point in the process -- and it seems useful to
have it sooner rather than later.
Built and regtested on x86-64 Fedora 18.
Tom
next reply other threads:[~2014-01-20 18:49 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-20 18:49 Tom Tromey [this message]
2014-01-20 18:49 ` [RFC 1/2] link gdbserver against libiberty Tom Tromey
2014-01-21 1:49 ` Yao Qi
2014-01-21 2:33 ` Tom Tromey
2014-02-07 14:49 ` Tom Tromey
2014-02-07 16:32 ` Pedro Alves
2014-02-07 21:00 ` Tom Tromey
2014-02-10 13:27 ` Pedro Alves
2014-02-12 16:44 ` Tom Tromey
2014-02-12 16:49 ` Pedro Alves
2014-02-08 2:36 ` Yao Qi
2014-01-21 2:03 ` Yao Qi
2014-01-20 18:49 ` [RFC 2/2] delete gdbserver's freeargv Tom Tromey
2014-02-07 16:35 ` Pedro Alves
2014-01-20 18:54 ` [RFC 0/2] let gdbserver use libiberty Tom Tromey
2014-06-12 20:37 ` Tom Tromey
2014-06-16 13:26 ` James Greenhalgh
2014-06-18 12:27 ` Marcus Shawcroft
2014-06-19 14:48 ` Tom Tromey
2014-06-20 10:52 ` Pedro Alves
2014-06-20 12:01 ` Gary Benson
2014-06-20 14:16 ` Tom Tromey
2014-06-20 14:44 ` [COMMITTED PATCH] Fix mingw32 build on x86-64 RHEL 6.5 Gary Benson
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=1390243792-31176-1-git-send-email-tromey@redhat.com \
--to=tromey@redhat.com \
--cc=gdb-patches@sourceware.org \
/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