From: Matthew Locke <mlocke@mvista.com>
To: Seong-kyu Ko <sugenius@doit.ajou.ac.kr>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: Problems building cross environment.
Date: Wed, 30 Aug 2000 10:28:57 -0700 [thread overview]
Message-ID: <39AD4459.B22ACA7D@mvista.com> (raw)
In-Reply-To: Pine.LNX.4.21.0008301128320.457-100000@doit.ajou.ac.kr
> So I want to know, are there anyone who build cross environment?
> If you built cross environment before please tell me.
> And if it's possible, please tell me what sources you use and
> how can you build - what options? ,modify sources?
Montavista has built a Cross Development Kit for several hosts to even
more targets. Our sources and binaries are at ftp://ftp.mvista.com
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2000-08-30 17:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-08-30 2:39 Problems building cross environment Seong-kyu Ko
2000-08-30 14:39 ` Cal Erickson
2000-08-30 17:28 ` Matthew Locke [this message]
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=39AD4459.B22ACA7D@mvista.com \
--to=mlocke@mvista.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=sugenius@doit.ajou.ac.kr \
/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).