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: Cross gcc for MIPS


"Frank W. Miller" wrote:
> 
> Greetings,
> 
> Has anyone built the toolchain for --target=mips ?  I've been able to
> build binutils but cannot for the life of me get gcc to build.  I've
> added --with-gnu-as, --with-gnu-ld, and --with-newlib to my configure
> line and I keep getting different errors.  Sometimes its missing header
> files: stdio.h and sys/types.h.  Sometimes I get a redeclaration of
> sys_errlist.

 Please explain what you mean by '--target=mips'...

 I have built cross-compilers for 'mips-linux-gnu' (MIPS with Linux),
'mips-sysv4.2' (MIPS with SVR4.2MP), 'mips-ultrix4 (Decstation),
'mips64vr4100-elf' (NEC VR41xx), 'mipstx39-elf (Toshiba TX39) etc.

 So your asking of 'toolchain for --target=mips' may be just the same
as asking about 'toolchain for --target=something' and not telling what
your 'something' is.

 Once someone asked somewhere something about the same 'target', and
I couldn't resist looking at what was the system selected for this.
The GCC 'configure' seemed to select an very old MIPS Inc. RISCOS-
something... So your target will be right if you have some old MIPS
workstation from the time before SGI bought MIPS...

 My opinion is that configure shouldn't approve target names like
'mips',
'i386', 'powerpc', 'sparc', 'm68k' etc. without any info about the used
binary format or operating system.

Cheers, Kai


------
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]