Re: [Jamvm-general] Error building JAMVM on Mac

[Anitha B G. <ani...@gm...>]

On 26 October 2014 11:48, Robert Lougher <rob...@gm...> wrote:
> Yes it is active.  Unfortunately there's not a lot of help that I can
> give.  Macs used to be my main computers so they were well supported
> (under Linux and Mac OS X).  However, I no longer use Macs (my last
> Mac is from 2006 running OS X 10.5).  Luckily it appears that JamVM
> continued to be buildable on OS X at least until a year or two ago
> (judging by feedback) but obviously this is no longer the case.
> Without a current Mac there's not a lot I can do, so I'll probably
> remove support entirely from the next version.
>
> In case this is of help, I can see the following from your original post.
>
> 1) You no longer have gcc on Mac OS X.  The C compiler is actually
> Clang/LLVM, which is masquerading as gcc.  I have never built JamVM
> using LLVM as it uses several gcc features.  I no idea if JamVM
> compiles with LLVM.  Even if it does compile, it may not work.
>
> 2) By default, it is building 64-bit executables.  In the past, even
> on 64-bit machines, gcc on Mac OS X defaulted to 32-bit.  The error
> messages you are seeing is because JamVM by default (on Mac OS X)
> assumes it is being built for 32-bit.
>
> You could try configuring JamVM to use libffi, e.g. ./configure
> --enable-ffi.  As far as I'm aware, Mac OS X should still support
> libffi.  If this works you will have a 64-bit executable.
>
> Alternatively you could see if there is a flag to LLVM/Clang to force
> it to build in 32-bit mode.

Rob,

Finally, I am able to build 1.5.4 version forcing clang to build

[1] Using -m32.
[2] Removing "interp_cflags=-fno-reorder-blocks" (Clang does not like
this option)

Bare invocation worked so presumably everything should work though I
haven't run tests. As a side note --enable-libffi did not work either.
Configure (clang) complained that it does not know what the option
meant.

Thanks for your prompt help

-Anitha