This is the mail archive of the crossgcc@sourceware.cygnus.com mailing list for the crossgcc project.

See the CrossGCC FAQ for lots more infromation.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: GCC: different OS targets.


Roger Williams wrote:

> >>>>> Brendan Simon <brendan@dgs.monash.edu.au> writes:
>
>   > I would like to be able to build gcc _ONCE_ for powerpc-eabi and
>   > be able to build the RTEMS, eCos (or any other OS) libraries and
>   > install them in an appropriate place.
>
> Yes indeed, this would be *very* helpful.  I'm currently developing
> MPC8xx code for no-OS, Linux, and Neutrino, and I have separate
> development installations for each of these.  I want to start working
> with eCos, but I dread the thought of yet another set of powerpc-eabi
> tools and libraries...

I've had a look through the gcc info files and noticed LOTS of -m command line
switches (eg. -mcall-linux, -mcall-sysv, -mcall-sysv-eabi, -mcall-sysv,
-mcall-aix, -mcall-solaris, ...).  Does this mean that I can have _ONE_ gcc
compiler for all my needs ?  If so, why is it common practise to build gcc with
targets such as "powerpc-eabi", "powerpc-aix", "powerpc-linux", etc ?  Sure all
one needs is something like "powerpc".  If the others are used to set the default
output style then surely this could be set with a configure command such as
--enable-call-aix or --default-call-aix or --with-call-aix (you get the picture).

Brendan Simon.



------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sourceware.cygnus.com


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]