Re: Linux x86 to Solaris Sparc Cross Compiler

[Alex Smith <alex at securesmith dot net>]

On Sat, 18 Mar 2000, Kai Ruottu wrote:
>  The 'sol2gas.h' was copied 'as is' from the egcs-20000306 snapshots
> (from 'gcc/config/i386') and as the comment says, it was aimed to be
> put into 'gcc/config/sparc', but then something seemingly happened
> and the thing was forgotten. I don't remember who is the Solaris2
> maintainer, but forwarding this to him/her, could be thought, the
> snapshots didn't have the GNU as possibility handled yet either...
> 
>  Perhaps the current gas snapshots already support the '-s', but with
> with GNU as up to 2.9.5.0.12 this kind of handling seems to be needed.
> 
> Cheers, Kai
> 

I made the changes both ways:
First, even before I get a response from the post, I tried editing my specs
file in my build directory to remove the '-s'.  I tired removing just the -s,
and removing everything after the -s (including the -s).  It didn't work,
instead I got many bad errors.
Second, I modifed the files as you dictated, and after adding sparc.h to tm.h
in my build area I managed to duplicate all of the bad mojo that I achived in
my first step.  

Hmm...

Here are the errors I'm getting know.  It seems that it is really expecting a
sparc at this point.

/tmp/ccus5WBe.s: Assembler messages:
/tmp/ccus5WBe.s:126: Error: Unknown pseudo-op:  `.proc'
/tmp/ccus5WBe.s:128: Error: Rest of line ignored. First ignored character is `!'
..
/tmp/ccus5WBe.s:129: Error: no such 386 instruction: `save'
/tmp/ccus5WBe.s:130: Error: Rest of line ignored. First ignored character is `!'
..
/tmp/ccus5WBe.s:131: Error: no such 386 instruction: `wr'
/tmp/ccus5WBe.s:132: Error: no such 386 instruction: `sra'
/tmp/ccus5WBe.s:133: Error: bad register name ('%i1')
/tmp/ccus5WBe.s:134: Error: no such 386 instruction: `andcc'
/tmp/ccus5WBe.s:135: Error: no such 386 instruction: `mulscc'
/tmp/ccus5WBe.s:136: Error: no such 386 instruction: `mulscc'
/tmp/ccus5WBe.s:137: Error: no such 386 instruction: `mulscc'
/tmp/ccus5WBe.s:138: Error: no such 386 instruction: `mulscc'
/tmp/ccus5WBe.s:139: Error: no such 386 instruction: `mulscc'
/tmp/ccus5WBe.s:140: Error: no such 386 instruction: `mulscc'
/tmp/ccus5WBe.s:141: Error: no such 386 instruction: `mulscc'
/tmp/ccus5WBe.s:142: Error: no such 386 instruction: `mulscc'
/tmp/ccus5WBe.s:143: Error: no such 386 instruction: `mulscc'
/tmp/ccus5WBe.s:144: Error: no such 386 instruction: `mulscc'
/tmp/ccus5WBe.s:145: Error: no such 386 instruction: `mulscc'
/tmp/ccus5WBe.s:146: Error: no such 386 instruction: `mulscc'
/tmp/ccus5WBe.s:147: Error: no such 386 instruction: `mulscc'
/tmp/ccus5WBe.s:148: Error: no such 386 instruction: `mulscc'
/tmp/ccus5WBe.s:149: Error: no such 386 instruction: `mulscc'
/tmp/ccus5WBe.s:150: Error: no such 386 instruction: `mulscc'
/tmp/ccus5WBe.s:151: Error: no such 386 instruction: `mulscc'
/tmp/ccus5WBe.s:152: Error: no such 386 instruction: `mulscc'
/tmp/ccus5WBe.s:153: Error: no such 386 instruction: `mulscc'
/tmp/ccus5WBe.s:154: Error: no such 386 instruction: `mulscc'
/tmp/ccus5WBe.s:155: Error: no such 386 instruction: `mulscc'
/tmp/ccus5WBe.s:156: Error: no such 386 instruction: `mulscc'
/tmp/ccus5WBe.s:157: Error: no such 386 instruction: `mulscc'
/tmp/ccus5WBe.s:158: Error: no such 386 instruction: `mulscc'
/tmp/ccus5WBe.s:159: Error: no such 386 instruction: `mulscc'
/tmp/ccus5WBe.s:160: Error: no such 386 instruction: `mulscc'
/tmp/ccus5WBe.s:161: Error: no such 386 instruction: `mulscc'
/tmp/ccus5WBe.s:162: Error: no such 386 instruction: `mulscc'
/tmp/ccus5WBe.s:163: Error: no such 386 instruction: `mulscc'
/tmp/ccus5WBe.s:164: Error: no such 386 instruction: `mulscc'
/tmp/ccus5WBe.s:165: Error: no such 386 instruction: `mulscc'
/tmp/ccus5WBe.s:166: Error: no such 386 instruction: `mulscc'
/tmp/ccus5WBe.s:167: Error: no such 386 instruction: `mulscc'
/tmp/ccus5WBe.s:168: Error: bad register name ('%g1')
/tmp/ccus5WBe.s:169: Error: no such 386 instruction: `rd'
/tmp/ccus5WBe.s:170: Error: bad register name ('%o0')
/tmp/ccus5WBe.s:171: Error: bad register name ('%l4')
/tmp/ccus5WBe.s:172: Error: bad register name ('%l5')
/tmp/ccus5WBe.s:173: Error: bad register name ('%i1')
/tmp/ccus5WBe.s:174: Error: operands given don't match any known 386 instruction
/tmp/ccus5WBe.s:175: Error: bad register name ('%i2')
/tmp/ccus5WBe.s:176: Error: bad register name ('%o0')
/tmp/ccus5WBe.s:177: Error: bad register name ('%i0')
/tmp/ccus5WBe.s:178: Error: operands given don't match any known 386 instruction
/tmp/ccus5WBe.s:179: Error: bad register name ('%i3')
/tmp/ccus5WBe.s:180: Error: bad register name ('%l2')
/tmp/ccus5WBe.s:181: Error: bad register name ('%l2')
/tmp/ccus5WBe.s:182: Error: bad register name ('%l0')
/tmp/ccus5WBe.s:184: Error: no such 386 instruction: `restore'
make[1]: *** [libgcc2.a] Error 1    

Let my know what you think, 
Thanks Alex

-- 
Alex Smith
Software Engineer
Intruder Alert
Axent Technologies, Inc.
(801) 227-3711
alex@securesmith.net

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