[B2-devel] Re: basilisk-devel digest, Vol 1 #257 - 1 msg

[Mark H. <ma...@mm...>]

----- Original Message ----- 
From: <bas...@li...>
To: <bas...@li...>
Sent: Saturday, January 24, 2004 11:01 PM
Subject: basilisk-devel digest, Vol 1 #257 - 1 msg


> Send basilisk-devel mailing list submissions to
> bas...@li...
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.sourceforge.net/lists/listinfo/basilisk-devel
> or, via email, send a message with subject or body 'help' to
> bas...@li...
>
> You can reach the person managing the list at
> bas...@li...
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of basilisk-devel digest..."
>
>
> Today's Topics:
>
>    1. Re: Zaurus SheepShaver with gcc33 (Gwenole Beauchesne)
>
> --__--__--
>
> Message: 1
> Date: Sat, 24 Jan 2004 12:48:15 +0100
> Subject: Re: [B2-devel] Zaurus SheepShaver with gcc33
> From: Gwenole Beauchesne <gb...@di...>
> To: bas...@li...
> Reply-To: bas...@li...
>
> Hi,
>
> > ../kpx_cpu/src/cpu/ppc/ppc-translate.cpp:99: error: (Each undeclared
> > identifier
> >    is reported only once for each function it appears in.)
> > make: *** [obj/ppc-translate.o] Error 1
>
> Move up the #if PPC_ENABLE_JIT as there is no JIT support for ARM yet,
> nor disassembler.
>
> BTW, where is the gcc33 env on ipaq4?
>


Hi Gwenole,

I thought that that autogen set the no jit compiler option once it saw that
it was compiling for a non-x86 cpu?  I'm pretty sure I remember seeing the
enable jit compiler option set to no in the config summary.  I could be
wrong so I'll double check.

If you go into /home/guest/dso...@ma... and browse you will see
three env scripts to set either gcc 2.9 something, 3.2.1, and then 3.3.
Feel free to use these or anything in in the dir!

Thanks for all the help,
Mark