building gcj on Intel Mac OS X 10.4.4 ?

[Tom Tromey]

>>>>> "Andi" == Andi Vajda <andi@osafoundation.org> writes:

Andi> For gcj support, my guess would be that support for at least these is
Andi> required: target-libffi target-boehm-gc target-zlib target-libjava

That's right.

Andi> Is this error due to gcc's configure not understanding Apple's recent
Andi> move to Intel chips or is there more work required, for example in
Andi> boehm-gc, to compile an Intel-native gcj on Mac OS X ?

Going down the list:

* libffi requires porting if the Apple x86 ABI differs from existing
  x86 ABIs.  Based on Andrew Pinski's response, I assume it does.

  libffi has 2 parts.  If the closure API has not been ported, then
  you can't use the interpreter or some JNI cases.  If the base part
  of libffi is not ported, then you lose some reflection things
  (Method.invoke).

* The GC probably requires some porting.  I wouldn't expect this to be
  much code.  You might look on the GC's mailing list to see if
  anybody has done it already.

* zlib, most likely, already works.  It is disabled because the
  top-level configure knows that libgcj hasn't been ported, so it
  disables building the dependencies.  I'm a little surprised that
  configure didn't complain about fastjar... but that almost certainly
  works already as well.  Neither zlib nor fastjar have tricky system
  requirements.

* libjava probably requires some porting effort.  In particular the
  signals-to-exceptions code usually requires some work.  This code
  can be disabled but that has a performance impact.

You can explain the signals thing and the libffi things to libgcj via
libjava/configure.host.  The comment at the top explains what the
different variables mean.

Andi> Is anyone working on this ?

Not that I know of.

Tom