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

[Christopher F. <chr...@gm...>]

I've had JamVM building for some time as a 64-bit executable on Darwin but
have been using gcc to build it.

I'd actually be somewhat surprised if it _didn't_ build with clang.

Also, Rob, I think you did add support for darwin builds recently, but I
basically copied and slightly modified your linux / x86_64 code to Darwin
and it seems to be working fine for as long as I've been using it (a year
or more off & on).

If there are any special tests you'd like me to run, I can do that, but
otherwise, I could submit a patch to the list. I guess I could test out
clang support as well.

©

Sent from my Android
On Oct 27, 2014 4:46 AM, "Robert Lougher" <rob...@gm...> wrote:

> Great you've got it to build!  Obviously, as a 32-bit executable you
> can't use a heap of more than a couple of GB.  BTW, the option is
> --enable-ffi, not --enable-libffi.
>
> Rob.
>
> On 27 October 2014 00:22, Anitha B Gollamudi <ani...@gm...>
> wrote:
> > 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
>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Jamvm-general mailing list
> Jam...@li...
> https://lists.sourceforge.net/lists/listinfo/jamvm-general
>