jmr3904 build problem

[Jonathan Larmour]

I would have thought this would be pretty obvious, but perhaps it just got
missed. Is it okay? Or is there some odd reason it was compiled with -mips3
before (and if so, how did it work!).

Jifl

Jonathan Larmour wrote:
> 
> I don't know how this could ever have worked, unless -mips1 and -mips3
> weren't incompatible before.
> 
> Okay to apply?
> 
> Jifl
> 
> 2001-08-13  Jonathan Larmour  <jlarmour@redhat.com>
> 
>         * mips/Makefile.in: Don't build jmr3904-io.c with -mips3.
> 
> Index: Makefile.in
> ===================================================================
> RCS file: /cvs/cvsfiles/devo/libgloss/mips/Makefile.in,v
> retrieving revision 1.39
> diff -u -5 -p -r1.39 Makefile.in
> --- Makefile.in 2000/12/05 20:10:53     1.39
> +++ Makefile.in 2001/08/13 20:16:05
> @@ -217,11 +217,11 @@ vr4300.o: ${srcdir}/vr4300.S
>         $(CC) -c $(CFLAGS_FOR_TARGET) $(CFLAGS) ${srcdir}/vr4300.S
>  vr5xxx.o: ${srcdir}/vr5xxx.S
>         $(CC) -c $(CFLAGS_FOR_TARGET) $(CFLAGS) ${srcdir}/vr5xxx.S
>  lsipmon.o: $(srcdir)/lsipmon.S $(srcdir)/pmon.S
>  jmr3904-io.o: ${srcdir}/jmr3904-io.c
> -       $(CC) -c $(CFLAGS_FOR_TARGET) $(CFLAGS) -mips3 ${srcdir}/jmr3904-io.c -o
> $@
> +       $(CC) -c $(CFLAGS_FOR_TARGET) $(CFLAGS) ${srcdir}/jmr3904-io.c -o $@
> 
>  # cma101 can not be compiled mips16, if a mips16 version is needed then
>  # it will have to be built, then this rule can be scrapped, allowing
>  # the implicit rule to run.
>  cma101.o: ${srcdir}/cma101.c
> 

-- 
Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 (1223) 271062
Maybe this world is another planet's Hell -Aldous Huxley || Opinions==mine