Re: NetBSD 4.0 "opcode not supported on this processor:mips1"...

"..I'd rather be coding ASM!" <[email protected]> Thu, 1 Oct 2009 15:56:26 +0300 (EEST)
Newsgroups gmane.os.netbsd.ports.cobalt
Message-ID <[email protected]>
Tried changing your CFLAGS to say: -arch=mips2  at worst, or -arch=mips3 ?

Looks like it's got mips1 hardwired in and something for mips2 is comming 
up. Or try CFLAGS="-arch=mips1" and see if it gets that? Sounds fishy.

The r5xxx in the mips cobalt's should be mips3 capable. Perhaps gcc's
only compiled with mips1 numonics?

Have a play. See how you go.

Al.

On Thu, 1 Oct 2009, Mike Hebel wrote:

> My primary DNS server drive died sometime between last night and this morning 
> so I'm trying to build BIND from scratch on one of my other boxes but it's 
> died with the attached error.
>
> I've read some notes that changing things in the CFLAG line might resolve 
> this but I'm clueless as to what needs to be changed.  This is a RAQ running 
> 4.0 with 65M of RAM.
>
> A little help here for an unemployed flu-riddled geek? ;-)
>
> ===========
>
> /var/tmp//cc6JN3Ze.s: Assembler messages:
> /var/tmp//cc6JN3Ze.s:24: Error: opcode not supported on this processor: mips1 
> (mips1) `ll $3,0($4)'
> /var/tmp//cc6JN3Ze.s:27: Error: opcode not supported on this processor: mips1 
> (mips1) `sc $3,0($4)'
> *** Error code 1
>
> Stop.
> make: stopped in /root/bind-9.6.1-P1/lib/isc
> *** Error code 1
>
> Stop.
> make: stopped in /root/bind-9.6.1-P1/lib
> *** Error code 1
>
> Stop.
> make: stopped in /root/bind-9.6.1-P1
> nothing#
>
> --
> Mike
>
>
> Azarath, Metrion, Zinthos!
>
>
>

-- 
  --
  Al Boyanich
  adb -w -P "world> " -k /dev/meta/galaxy/ksyms /dev/god/brain