From: mike@penbex.com.tw (mike)
To: <crossgcc@sources.redhat.com>
Subject: Re: Where to get start about cross development!
Date: Sun, 01 Apr 2001 00:00:00 -0000 [thread overview]
Message-ID: <004d01c07ac9$0e2513e0$9e0150c0@penbex.com.tw> (raw)
Message-ID: <20010401000000.uixdma99IZWz4DIncsm0pR29PirDFU7UXmCQyP4GkZ0@z> (raw)
In-Reply-To: <002401c07ac6$d0bc79a0$b200a8c0@minecard.com.tw>
Check the FAQ first
http://www.objsw.com/CrossGCC/
and mention about your target to get more response.
----- Original Message -----
From: clifftsai
To: crossgcc
Sent: Wednesday, January 10, 2001 1:33 PM
Subject: Where to get start about cross development!
Hi:
I'm new to cross development.I wanna know
where can I get start about cross development
Thanks in advance.
------
Want more information? See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sourceware.cygnus.com
next prev parent reply other threads:[~2001-04-01 0:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-09 21:42 clifftsai
2001-01-09 21:49 ` mike [this message]
2001-01-10 8:36 ` Kai Ruottu
2001-04-01 0:00 ` Kai Ruottu
2001-04-01 0:00 ` mike
2001-04-01 0:00 ` clifftsai
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='004d01c07ac9$0e2513e0$9e0150c0@penbex.com.tw' \
--to=mike@penbex.com.tw \
--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).