From: Hugues Belanger <hbelange@cgocable.net>
To: crossgcc@sources.redhat.com
Subject: Help with Cross compiling
Date: Sun, 16 Jul 2000 20:41:00 -0000 [thread overview]
Message-ID: <3972814E.CA1D788F@cgocable.net> (raw)
In-Reply-To: <963804609.28468.ezmlm@sources.redhat.com>
Hi All.
I was wondering if you can offer some guidance or just point me in the
right direction.
I've been a avid LRP (linux router project) fan for many moons now and
I'm trying to port this jewel to the LART board (SA-1100) and I find myself in the
strange world of cross compiling... (I'm not a developer so this is real scary for me)
I've downloaded the toolchain from www.handhelds.org and manage to patch
configure and compile a 2.2.14 kernel with no errors.
I then started to port the root package which contains all the libs and
basic /bin and /sbin apps...
I compiled Busybox, tinylogin, but that's it... ae, ash, ctar, etc, ... all need
extra libs and I'm not sure how to had them..
Example ae needs termcap.h it's in my /usr/include but the
toolchain doesn 't use it ? do I have to all these include to the
toolchain if so how ?
I've been doing a sone reading about the GNUPro toolkit, should I use it for this
project or stick with my current toolchain ?
Let me know if you can help
Thanks
P.S> Anybody out there which to join me in this project ? I might be able to compansate
for you efforts...
------
Want more information? See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sourceware.cygnus.com
parent reply other threads:[~2000-07-16 20:41 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <963804609.28468.ezmlm@sources.redhat.com>]
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=3972814E.CA1D788F@cgocable.net \
--to=hbelange@cgocable.net \
--cc=crossgcc@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).