IB wrote: > So my questions are: > (1) Do I just change some options at the command-line to compile my > assembly file (written in SPARC)? If so, in gcc or via as and how do I > do this? I've tried: > $ as -Av6 printHello.s > as: unrecognized option '-Av6'
While gcc and binutils do support many dozens of target platforms, they only support one specific target configuration at any time[1]. The gcc and binutils that Cygwin provides are native tools -- they target Cygwin and can make Cygwin binaries only[2]. To do what you're trying to do you need to build a cross tool chain (cross-assembler, cross-linker, cross-compiler, etc.) That is certainly possible with Cygwin but it's not something that is provided by default so you have to build it yourself. The gcc and binutils manuals are monolithic in that they documents all supported targets and options from one document so anything but the options in the i386 section will be irrelevant unless you build a cross compiler. Brian [1] Technically through the multilib facility this definition of one target can be stretched somewhat, but even with multilibs you are still limited to one backend. [2] Technically it can also make MinGW binaries with the -mno-cygwin switch, but that's implemented by simply searching a different set of target libraries and setting various options in the specs file, a variation on the multilib concept. It's still the same common i386 PE backend in both cases however. -- 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/
