Fwd: Status of gcj/java on PPC Linux?

[Kevin B. Hendricks]

Hi,

Okay one more thing.  I don't want my patches to break anything for any other POWERPC port.  Unfortunately the trampoline sizes and code and how parameters are passed are different for different AIX and Linux PPC.

I need to define some things in ffi.h.in to turn on closures and set the trampoline size and don't want to simply use the libffi defined(POWERPC) for fear it breaks AIX.

What is the best way to limit this?

Will defined(__linux__) && defined(__powerpc__) work or is there something like
defined(LINUX) && defined(POWERPC) you would rather I used.

Thanks,

Kevin


On Thursday, February 8, 2001, at 12:02 PM, Tom Tromey wrote:

> >>>>> "Mark" == Mark Wielaard <mark@klomp.org> writes: 
>  
> >> What parameters to configure should I pass to force the building of 
> >> all the java requirements during the full gcc build? 
>  
> Mark> You should configure with --enable-languages=c++,java 
>  
> Even that might not be enough, if the top-level configure thinks that 
> java is unbuildable.  If it still decides not to build Java, you'll 
> need to dig through configure/configure.in (you *won't* need autoconf 
> -- these are not autoconf configure scripts) and find where libgcj is 
> disabled for your platform. 
>  
> Tom 
>  
>