This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: Cygwin, gcc and processor-specific options
- From: Brian Dessent <brian at dessent dot net>
- To: cygwin at cygwin dot com
- Date: Fri, 01 Dec 2006 13:47:10 -0800
- Subject: Re: Cygwin, gcc and processor-specific options
- References: <168140.87862.qm@web33514.mail.mud.yahoo.com>
- Reply-to: cygwin at cygwin dot com
Tim Chan wrote:
> Hi! I am using gcc and g++ on cygwin. How come I can't
> use the machine and processor specific options such as
> -68hc12. How can I take advantage of m68hc11.md?
The gcc included with Cygwin is a native gcc, which means it creates
executables that run under Windows on the IA-32 architecture, and
nothing else. In general a specific copy of gcc is only capable of
supporting a single target. If you want something else you need to
configure and build gcc for the desired target. Just because gcc
supports three dozen different architectures doesn't mean you can use
them all at once. You seem to be looking at random files in the gcc
source code and inferring something about their presence that is not
true.
Building cross-compilers is not exactly on-topic for this list, there
are better places to ask, like the crossgcc list or google.
Brian
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/