From: "Raghavendra Koushik" <raghavendra.koushik@wipro.com>
To: <shripada@india.hp.com>, <help-gcc@gnu.org>
Subject: RE: gcc porting
Date: Thu, 09 May 2002 03:36:00 -0000 [thread overview]
Message-ID: <000c01c1f742$e01f3b90$5408720a@JollyRoger> (raw)
In-Reply-To: <000001c1f70b$2720da90$56724c0f@nt1486>
[-- Attachment #1: Type: text/plain, Size: 550 bytes --]
checkout this cross compiler FAQ site
http://www.sthoward.com/CrossGCC/
also find out if mc68K platform is supported on gcc. you can
do that by checkig out the list of supported platforms on
the gcc.gnu.org site.
-Koushik
-----Original Message-----
From: gcc-help-owner@gcc.gnu.org [mailto:gcc-help-owner@gcc.gnu.org]On
Behalf Of Shripad
Sent: Thursday, May 09, 2002 9:10 AM
To: help-gcc@gnu.org
Subject: gcc porting
hi..
i wanted to port gcc so that it generates code for mc68000 on my intel
machine.
Please tell me how to do it.
shripad
[-- Attachment #2: Wipro_Disclaimer.txt --]
[-- Type: text/plain, Size: 522 bytes --]
**************************Disclaimer**************************************************
Information contained in this E-MAIL being proprietary to Wipro Limited is 'privileged'
and 'confidential' and intended for use only by the individual or entity to which it is
addressed. You are notified that any use, copying or dissemination of the information
contained in the E-MAIL in any manner whatsoever is strictly prohibited.
****************************************************************************************
next prev parent reply other threads:[~2002-05-09 10:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-08 20:56 Shripad
2002-05-09 3:36 ` Raghavendra Koushik [this message]
2002-05-09 5:16 Shripad
[not found] <616BE6A276E3714788D2AC35C40CD18D621AFC@whale.softwire.co.uk>
2002-05-09 5:27 ` Rupert Wood
2002-11-16 7:42 Gcc porting Alexander Shkurko
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='000c01c1f742$e01f3b90$5408720a@JollyRoger' \
--to=raghavendra.koushik@wipro.com \
--cc=help-gcc@gnu.org \
--cc=shripada@india.hp.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).