From: Dan Dickey <ddickey@charter.net>
To: Grant Erickson <grant@borg.umn.edu>
Cc: "linuxppc-embedded@lists.linuxppc.org"
<linuxppc-embedded@lists.linuxppc.org>,
Linux PPC Dev <linuxppc-dev@lists.linuxppc.org>
Subject: Re: My cookbook approach to building a cross compiler for the powerpc on an intel x86 Linux box
Date: Tue, 11 Jan 2000 21:05:43 -0600 [thread overview]
Message-ID: <387BEF87.25EC6A2A@charter.net> (raw)
In-Reply-To: 200001100522.XAA07318@congo.borg.umn.edu
Grant Erickson wrote:
>
> Also, consider the documentation at:
>
> http://www.lcse.umn.edu/~grant/Linux/cross.html
>
> Regards,
>
> Grant Erickson
Grant,
thanks for the pointer!
This is fantastic! I believe that it would have saved me at least
an hour last Saturday had I known about your page. Ah well.
It looks like your page is a good reference for building
a "straight" cross-compiler environment. Building applications
based on glibc that will actually run on the target machine with
Linux as the OS.
What I was trying to do to begin with was a bit simpler - just
build a cross environment to allow code to run on one of the
PPC boards that are available. No OS yet, certainly not glibc.
What I imagined is having one environment for building the
"simple" environment, and a later one for actually building
the applications to run on Linux with glibc.
-Dan
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-01-12 3:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-01-10 5:23 My cookbook approach to building a cross compiler for the powerpc on an intel x86 Linux box Grant Erickson
2000-01-12 3:05 ` Dan Dickey [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-01-10 2:23 Dan Dickey
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=387BEF87.25EC6A2A@charter.net \
--to=ddickey@charter.net \
--cc=grant@borg.umn.edu \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=linuxppc-embedded@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.