From: "Christopher R. Johnson" <cjohnson@gcctech.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: powerpc gdb and gdbserver
Date: Mon, 22 Dec 2003 10:32:03 -0500 [thread overview]
Message-ID: <3FE70E73.3090309@gcctech.com> (raw)
In-Reply-To: 20031222035217.GA7378@nevyn.them.org
Good news. All I needed to do was setup Kegel's crosstool.sh by adding
the following to my powerpc-405.dat file:
GLIBC_EXTRA_CONFIG="--without-fp"
to
GLIBC_EXTRA_CONFIG="--without-fp --enable-add-ons=linuxthreads_db"
And used crosstool to rebuild the tool chain. That resulted in the
library gdbserver needed to run. I need some instruction from Dan on
how to rebuild just a component, after this type of config change, so I
don't go through the 2 hour crosstool run.
Daniel Jacobowitz wrote:
>On Thu, Dec 18, 2003 at 03:37:49PM -0500, Christopher R. Johnson wrote:
>
>>As I mentioned, the library doesn't exist. I need to build it, but I'm
>>not sure where it comes from (glibc I think) or how to get it built.
>>Its a target library, so I have to build it for ppc and deliver it to
>>my target box. That part I know how to do, its creating the library to
>>begin with that I don't know how to do.
>>
>
>Wherever you got glibc from you should have gotten libthread_db.so.1
>also; maybe it just wasn't installed?
>
--
Christopher R. Johnson
Principal Software Engineer
GCC Printers
(781)276-8763
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-12-22 15:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-17 17:50 powerpc gdb and gdbserver Christopher R. Johnson
2003-12-18 17:10 ` Daniel Jacobowitz
2003-12-18 20:27 ` Christopher R. Johnson
2003-12-18 20:35 ` Daniel Jacobowitz
2003-12-18 20:37 ` Christopher R. Johnson
2003-12-19 20:35 ` Wolfgang Denk
2003-12-22 3:52 ` Daniel Jacobowitz
2003-12-22 15:32 ` Christopher R. Johnson [this message]
2003-12-19 9:37 ` Marius Groeger
2003-12-22 3:52 ` 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=3FE70E73.3090309@gcctech.com \
--to=cjohnson@gcctech.com \
--cc=drow@false.org \
--cc=linuxppc-dev@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).