From: "Christopher R. Johnson" <cjohnson@gcctech•com>
To: linuxppc-embedded@lists•linuxppc.org
Subject: Tools question
Date: Mon, 24 Nov 2003 13:32:17 -0500 [thread overview]
Message-ID: <3FC24EB1.60106@gcctech.com> (raw)
This is probably way too big a question to ask here, but I'm hoping
someone can help me. I have inherited a gcc 2.95.3 cross development
tool chain, which has been working fine to build for my powerpc-linux
target machine. I'm building the kernel and user programs fine. I'm
beginning to find as I add things in that I'm missing libraries. Today
its libresolv which I need for pump. Some questions:
1. Do I really need to go back and build my own tool chain? I've tried
grabbing 2.95.3 sources and building by running configure with
--target=powerpc-linux, but I get some missing include file errors
building libgcc2.a. I'm on a 405GP (no fp). Should I even bother doing
this?
2. On my intel development machine I see that libresolv.a comes from
glibc-devel-2.2.5-34. I have gcc-2.96-110 for my compiler. Should I go
find a version of glibc-devel that matches up with my existing 2.95.3
tools? How will I know if its the right version?
3. Better yet, is there somewhere I can just obtain a reasonable tool
chain that's ready-built for my target machine? Complete with libraries?
Sorry for the newbie type questions. I have the "Using and Porting GNU
CC" book, but am finding it a little too Stallman-esque to follow. Anyone?
Thanks!
Chris Johnson
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next reply other threads:[~2003-11-24 18:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-24 18:32 Christopher R. Johnson [this message]
2003-11-24 19:14 ` Tools question Wolfgang Denk
2003-11-25 6:08 ` Dan Kegel
-- strict thread matches above, loose matches on Subject: below --
2003-11-24 19:01 Wells, Charles
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=3FC24EB1.60106@gcctech.com \
--to=cjohnson@gcctech$(echo .)com \
--cc=linuxppc-embedded@lists$(echo .)linuxppc.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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