From: Daniel Jacobowitz <drow@mvista.com>
To: Christoph Plattner <christoph.plattner@gmx.at>
Cc: Andrew Cagney <ac131313@cygnus.com>, gdb@sources.redhat.com
Subject: Re: `gdbserver' in cross compiled builds
Date: Sun, 24 Feb 2002 08:37:00 -0000 [thread overview]
Message-ID: <20020224113712.A8162@nevyn.them.org> (raw)
In-Reply-To: <3C78CDDC.DCEC0237@gmx.at>
On Sun, Feb 24, 2002 at 12:26:20PM +0100, Christoph Plattner wrote:
> Yes, that's clear for me. It is the same for glibc.
> With this point I have NO problems.
>
> The problem is simple in the tree setup !
>
> In my built (objects) tree, there is NO "gdbserver" subdirectory
> created by configuring, in the gdb source tree, the configuration
> cannot be done, because all generated files (configs, header files,
> etc) are written to the build tree (OBJECT tree).
Andrew explained this to you at least twice.... if the build tree is
for a cross debugger, you CAN NOT build gdbserver in it.
> So my problems are not in the config parameters, but simple, where
> (on which path) is called what ?
> And if I do some hacks manually, PPC support (for example) cannot be
> built. Why does the gdbserver directory work so bad ?
Use current CVS instead. I've spent months fixing this.
In fact, if you get current CVS, you can:
mkdir obj
cd obj
../src/gdb/gdbserver/configure
make
And build only the server.
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2002-02-24 16:37 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
[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 [this message]
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=20020224113712.A8162@nevyn.them.org \
--to=drow@mvista.com \
--cc=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