* FFI closure on mips
@ 2009-10-12 15:49 abhishek desai
2009-10-12 16:02 ` Bryce McKinlay
0 siblings, 1 reply; 2+ messages in thread
From: abhishek desai @ 2009-10-12 15:49 UTC (permalink / raw)
To: java
Hi,
I am compiling sources of gcc 3.4.6 with libgcj interpreter support
for the mipsel platform. When compiling with --enable-interpreter flag
I get a compilation error in the file resolve.cc in function
void * _Jv_InterpMethod::ncode ()
when it tries to use the ffi_raw_closure structure. The usage is not
under any #ifdef.
In newer versions of gcc this function is in interpret.cc.
This structure is defined in the ffi.h header file of libffi under the
flag FFI_CLOSURES.
FFI_CLOSURES is defined for each target. For mips it is defined as
#define FFI_CLOSURES 0
Is ffi closure necessay for libgcj compilation ? Can we compile libgcj
without the ffi closure support ?
How can I get it compiled on a mipsel system ?
I have to use gcc 3.4.6 since it is a project requirement.
--- abhi
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: FFI closure on mips
2009-10-12 15:49 FFI closure on mips abhishek desai
@ 2009-10-12 16:02 ` Bryce McKinlay
0 siblings, 0 replies; 2+ messages in thread
From: Bryce McKinlay @ 2009-10-12 16:02 UTC (permalink / raw)
To: abhishek desai; +Cc: java
On Mon, Oct 12, 2009 at 4:49 PM, abhishek desai <abhi00@gmail.com> wrote:
> Is ffi closure necessay for libgcj compilation ? Can we compile libgcj
> without the ffi closure support ?
Closure support is required for the interpreter. You can configure
with --disable-interpreter to build libgcj without using closures.
Bryce
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2009-10-12 16:02 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2009-10-12 15:49 FFI closure on mips abhishek desai
2009-10-12 16:02 ` Bryce McKinlay
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).