From: Andrew Cagney <ac131313@cygnus.com>
To: Christoph Plattner <christoph.plattner@gmx.at>
Cc: gdb@sources.redhat.com
Subject: Re: `gdbserver' in cross compiled builds
Date: Sat, 23 Feb 2002 09:31:00 -0000 [thread overview]
Message-ID: <3C77D1F6.1020704@cygnus.com> (raw)
In-Reply-To: <3C5B3201.2F2FB670@gmx.at>
Hello,
The first problem is that GDB server is only configured when build
``native''. A native gdbserver needs to be linked against the hosts
ptrace libraries. To do this using a cross compiler, you need to
configure things do what is often refered to as a ``canadian cross'':
--host=i386-linux-gnu \
--target=i386-linux-gnu \
--build=<build-machine>
The second problem is bit rot between core-gdb and gdbserver. Core GDB
is being changed in ways that are not compatible with gdbserver (a
compromize). gdbserver was recently been overhauled (by Daniel J) to
address this.
Can I suggest downloading a current GDB (see
http://sources.redhat.com/gdb/current/ ).
Andrew
> Hello GDB group !
>
> I often try to build up cross tool chains for different platforms:
> i386, PowerPC, Atmel AVR, HP PA-RISC, and SPARC soon.
>
> But I always have the problem with the standard GDB server (not
> a stub in special environments).
>
> First of all a question: Why is the gdbserver not built up auto-
> matically. If I build a native GDB, then I want to have a `gdbserver'
> for my native system, for example I have the same core system, but
> only small disk (CompactFlash, for example) and I want to use
> `gdbserver' there. If I build a cross build, for example a PPC cross
> setup from a intel machine, then I think it is also a clear way
> to build a `gdb' running on a i386 and handling PPC code, and
> a `gdbserver' running on the target (--host=$TARGET) and in the
> best also install it to $prefix/$TARGET as `glibc' and others
> do so.
>
> When I build up such a tool chain, I always have source and
> object trees seperated. How can I configure and build a
> `gdbserver' in such a tree setup. When I do the configuration
> in the source tree under ./gdb/gdbserver (which I do not like
> in the source tree ...), then the built cannot find generated
> header files. I cannot run the `configure' from the object tree,
> as there is no subdirectory under `./gdb' named `gdbserver'.
> Doing a copy from the src/gdb-5.1.1/gdb/gdbserver to the
> corresponding place into the object tree does not work also.
>
> How is this done correctly. I cannot find good information
> on this topic in the internet.
>
> PLEASE: Send it directly to me, as I am not registered on the
> GDB mailing list (perhaps I want to, if the problem stays longer ...)
>
> With friendly regards
> Christoph P.
>
>
>
>
next parent reply other threads:[~2002-02-23 17:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3C5B3201.2F2FB670@gmx.at>
2002-02-23 9:31 ` Andrew Cagney [this message]
[not found] ` <3C780221.CF27FBDA@gmx.at>
2002-02-23 13:26 ` Andrew Cagney
2002-02-24 3:26 ` Christoph Plattner
2002-02-24 8:37 ` Daniel Jacobowitz
2002-02-24 10:21 ` Dan Kegel
2002-02-24 10:25 ` 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=3C77D1F6.1020704@cygnus.com \
--to=ac131313@cygnus.com \
--cc=christoph.plattner@gmx.at \
--cc=gdb@sources.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