From: "Doug Evans" <dje@google.com>
To: "Jim Blandy" <jimb@codesourcery.com>
Cc: gdb@sourceware.org
Subject: Re: gdbserver + libiberty?
Date: Tue, 15 Jan 2008 18:42:00 -0000 [thread overview]
Message-ID: <e394668d0801151041i10067cf9g2ead16bb70ee73eb@mail.gmail.com> (raw)
In-Reply-To: <m37iibotcg.fsf@codesourcery.com>
On Jan 15, 2008 10:07 AM, Jim Blandy <jimb@codesourcery.com> wrote:
>
> dje at google.com (Doug Evans) writes:
> > Hi. Is there any reason to not link gdbserver with libiberty?
> > I'm working on a patch where that would be useful.
>
> gdbserver would need to be linked with a libiberty compiled for the
> target, obviously.
This part I'm not clear on. I found this in gdb/configure.ac:
# We only build gdbserver automatically in a native configuration.
if test "$gdb_native" = "yes"; then
AC_MSG_CHECKING(whether gdbserver is supported on this host)
if test "x$build_gdbserver" = xyes; then
AC_MSG_RESULT(yes)
AC_CONFIG_SUBDIRS(gdbserver)
else
AC_MSG_RESULT(no)
fi
fi
I couldn't find any docs on building gdbserver for cross targets (i.e
--host != --target), got any pointers? It's only useful for targets
that otherwise can be build natively (AIUIp. Would gdbserver ever be
built with CC_FOR_TARGET whereas gdb got built with CC? I can't find
any code to handle this in gdb or the top level configury. And if not
would gdbserver ever need a different libiberty than the one gdb is
linked with?
next prev parent reply other threads:[~2008-01-15 18:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-15 17:26 Doug Evans
2008-01-15 18:08 ` Jim Blandy
2008-01-15 18:42 ` Doug Evans [this message]
2008-01-15 19:45 ` Paul Koning
2008-01-15 20:24 ` Daniel Jacobowitz
2008-01-16 21:42 ` Jim Blandy
2008-01-16 22:15 ` Daniel Jacobowitz
2008-01-16 22:56 ` Jim Blandy
2008-01-17 14:37 ` Daniel Jacobowitz
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=e394668d0801151041i10067cf9g2ead16bb70ee73eb@mail.gmail.com \
--to=dje@google.com \
--cc=gdb@sourceware.org \
--cc=jimb@codesourcery.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