Re: cross compiling R10k/6.4->R4400/6.2

New Message Reply Date view Thread view Subject view Author view

Hansong Zhang (zhangh++at++cs.unc.edu)
Tue, 16 Dec 1997 23:29:58 -0500 (EST)

Turns out due to a problem in the Makefile, one of my ten .a files is NOT
compiled with -mips3 -n32. Instead it's compiled to the default target
(mips4) on R10K. And that caused the whole problem of having "bad
request code" when the executable's run on R4400.

Now I wonder if "-mips3 -n32" is equiverlent to
"-TARG:platform=ip19:processor=r4400" which I tried first.

Looks like it would be nice to have a warning message when -mips3 is
specified but one of the library files is mips4. The "bad request code"
message is really not very illuminating.

anyway next time you see "bad request code", make sure that ALL
object/library files are for the correct target.

Hansong

>
> -mips3 -n32 (-O2)
>
> > > > -TARG:platform=ip19:processor=r4400
>

=======================================================================
List Archives, FAQ, FTP: http://www.sgi.com/Technology/Performer/
            Submissions: info-performer++at++sgi.com
        Admin. requests: info-performer-request++at++sgi.com

New Message Reply Date view Thread view Subject view Author view

This archive was generated by hypermail 2.0b2 on Mon Aug 10 1998 - 17:56:26 PDT

This message has been cleansed for anti-spam protection. Replace '++at++' in any mail addresses with the '@' symbol.