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] |
"Frank W. Miller" wrote: > > > Please explain what you mean by '--target=mips'... > > When I configure with this target, I end up with something like > mips-elf-elf. I'm putting together a toolchain to port a new OS to > the Casio Cassiopeia E-100 which has a VR4121 in it so perhaps I'll > change to the mips64vr4100-elf target you mention below. > > > 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. > I'm sorry, but along this same line, it would be nice if the configure > had a --targets option or something that would give a nice list of all > the possible targets it does support? Yes, it would be better, but just browsing the 'configure' script in GCC sources (e.g. 'gcc-2.95.2/gcc/configure') and looking at the target entries there and seeing what files it will use from the 'config/mips' directory, would be recommended. It is quite common that there are bugs, e.g. the 'mips-sni-sysv4*' config entry used to list a file 'sni-gdb.h' which didn't exist, but there was a 'sni-gas.h'... If you use the official FSF sources, you will find the 'mips64vr4100-elf' target not being supported. The egcs-snapshots may have it and the other NEC types like 'mips64vr4300-elf' and 'mips64vr5000-elf' now, but at least the eCos-1.2.1 devtools sources has them. Or you could try the 'mips64orion-elf' (was this the 'R4650' ? -- just too many types...) I copied the 'mips64vr*' configuration entries and the config files to gcc-2.95.2 sources and the stuff seemed to work there too. The eCos-1.2.1 GCC is version '2.9-990319', so there weren't a big jump to '2.95.2'. Jobs like this needs a basic know-how about the config-chain, starting from the entry in 'gcc/configure' and ending to the files in 'gcc/config/<cpu>'. And a basic knowledge about C and how to fix the possibly changed macros... I'm not sure if I needed to change anything. E:\usr\local\samples>gcc-mips64vr4100 -v Reading specs from e:\usr\local\lib\gcc-lib\mips64vr4100-elf\2_95.2\specs gcc version 2.95.2 19991024 (release) Building a reference compiler from the '2.9-990321' sources is however strongly recommended... You will not have problems with binutils (just try the snapshots if the 2.9.1 or the 2.9-990321 ones don't work...) or GDB (please try the GDB or Insight snapshots...). 'ftp://sourceware.cygnus.com/pub/....' With all the MIPS targets using the '--with-gnu-as' and '--with-gnu-ld' may be necessary to avoid all problems with 'mips-tfile' etc. BTW, is the 'Casio Cassiopeia E-100' a PDA or what ? 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] |