On 02/05/2012 12:52 PM, Kai Ruottu wrote: > 3.2.2012 15:54, Kai Ruottu kirjoitti: > >> The "as1750" should understand the output from a '1750a' targeted >> plain vanilla FSF GCC... > > After being away from town during the weekend I made the 'as1750' > from its sources - that succeeded without any problems - and tried > it with the earlier made gcc-3.2.3 for 1750a target. But the build > didn't succeed to continue with it : > > /home/src/gcc-3.2.3-pl1/build/gcc/xgcc > -B/home/src/gcc-3.2.3-pl1/build/gcc/ -nostdinc > -B/home/src/gcc-3.2.3-pl1/build/1750a/newlib/ -isystem > /home/src/gcc-3.2.3-pl1/build/1750a/newlib/targ-include -isystem > /home/src/gcc-3.2.3-pl1/newlib/libc/include -B/usr/local/1750a/bin/ > -B/usr/local/1750a/lib/ -isystem /usr/local/1750a/include -O2 -DIN_GCC > -DCROSS_COMPILE -W -Wall -Wwrite-strings -Wstrict-prototypes > -Wmissing-prototypes -isystem ./include -DIN_LIBGCC2 > -D__GCC_FLOAT_NOT_NEEDED -Dinhibit_libc -I. -I. -I../../gcc > -I../../gcc/. -I../../gcc/config -I../../gcc/../include -DL_muldi3 -c > ../../gcc/libgcc2.c -o libgcc/./_muldi3.o > Output file extension must be one of: > .hex => Tektronix Extended Hex > .ldm => TLD Load Module > .llm => TLD Logical Load Module > make[2]: *** [libgcc/./_muldi3.o] Virhe 1 > > This was however expected because the "GCC Install / Specific Install > Notes" tells : > > -------------------- clip ------------------------- > 1750a-*-* > MIL-STD-1750A processors. This target is obsoleted in GCC 3.1. > > The MIL-STD-1750A cross con guration produces output for as1750, an > assembler/linker available under the GNU General Public License for > the 1750A. > <snip> > You should ignore a fatal error during the building of `libgcc' > (`libgcc' is not yet implemented for the 1750A.) > > The as1750 assembler requires the fi le `ms1750.inc', which is found > in the directory `gcc/config/1750a'. > -------------------- clip ------------------------- > > So I think the compiler was already there... What one should/could do > with it, is left as a homework for someone who really is familiar with > this system, "GCC for 1750a". > > What comes to the "alternative" 'm1750a-coff' target, using the GNU > binutils, with the 'cpp1750.zip' provided headers etc, with it, that > is totally an another issue... Thank you very much for your time and help with this. I do appreciate it. Let me see how much of your work I can reproduce. ~Stack~
Attachment:
signature.asc
Description: OpenPGP digital signature
