Re: Mac OS X Compile problem

["Dimiter \"malkia\" Stanev" <malkia@...>]

Thanks, guys!

I just saw that gcc is actually llvm gcc. But there is "gcc-4.2" which 
is real gcc.

malkia ~/p/luajit $ which gcc && gcc --version
/usr/bin/gcc
i686-apple-darwin11-llvm-gcc-4.2 (GCC) 4.2.1 (Based on Apple Inc. build 
5658) (LLVM build 2335.15.00)
Copyright (C) 2007 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

malkia ~/p/luajit $ which gcc-4.2 && gcc-4.2 --version
/usr/bin/gcc-4.2
i686-apple-darwin11-gcc-4.2.1 (GCC) 4.2.1 (Apple Inc. build 5666) (dot 3)
Copyright (C) 2007 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

With the "gcc-4.2" it compiles and works:

malkia ~/p/luajit $ make TARGET_CC="gcc-4.2" clean amalg
make -C src clean
rm -f luajit libluajit.a libluajit.so buildvm lj_vm.s lj_bcdef.h 
lj_ffdef.h lj_libdef.h lj_recdef.h lj_folddef.h ../lib/vmdef.lua *.o 
*.obj *.lib *.exp *.dll *.exe *.manifest *.pdb *.ilk
Building LuaJIT 2.0.0-beta7
make -C src amalg
+--------------------------------------------------------------------------+
| WARNING: Compiling the amalgamation needs a lot of virtual memory        |
| (around 200 MB with GCC 4.x)! If you don't have enough physical memory   |
| your machine will start swapping to disk and the compile will not finish |
| within a reasonable amount of time.                                      |
| So either compile on a bigger machine or use the non-amalgamated build.  |
+--------------------------------------------------------------------------+
make all "LJCORE_O=ljamalg.o"
HOSTCC    buildvm.o
HOSTCC    buildvm_asm.o
HOSTCC    buildvm_peobj.o
HOSTCC    buildvm_lib.o
HOSTCC    buildvm_fold.o
HOSTLINK  buildvm
BUILDVM   lj_vm.s
ASM       lj_vm.o
BUILDVM   lj_ffdef.h
BUILDVM   lj_bcdef.h
BUILDVM   lj_folddef.h
BUILDVM   lj_recdef.h
BUILDVM   lj_libdef.h
CC        ljamalg.o
AR        libluajit.a
CC        luajit.o
BUILDVM   ../lib/vmdef.lua
DYNLINK   libluajit.so
LINK      luajit
OK        Successfully built LuaJIT

On 6/13/11 1:57 AM, Justin Cormack wrote:
> On Mon, Jun 13, 2011 at 6:52 AM, Alexander Gladysh <agladysh@gmail.com
> <mailto:agladysh@gmail.com>> wrote:
>
>     On Mon, Jun 13, 2011 at 07:55, Dimiter "malkia" Stanev
>     <malkia@gmail.com <mailto:malkia@gmail.com>> wrote:
>      > Hi Mike,
>      >
>      > I'm not able to compile LuaJIT on latest MacOSX. It looks like my
>      > /usr/include/unwind.h does not have what is supposed to be there,
>     then again
>      > there are dozen of unwind.h's from gcc folders that have this
>     information,
>      > for example, this one here has it:
>
>     FWIW I can not reproduce this.
>
>     $ gcc --version
>     i686-apple-darwin10-gcc-4.2.1 (GCC) 4.2.1 (Apple Inc. build 5664)
>     Copyright (C) 2007 Free Software Foundation, Inc.
>     This is free software; see the source for copying conditions.  There
>     is NO
>     warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR
>     PURPOSE.
>
>     $ xcodebuild -showsdks
>     Mac OS X SDKs:
>             Mac OS X 10.5                   -sdk macosx10.5
>             Mac OS X 10.6                   -sdk macosx10.6
>
>     $  uname -a
>     Darwin agmac.local 10.7.0 Darwin Kernel Version 10.7.0: Sat Jan 29
>     15:17:16 PST 2011; root:xnu-1504.9.37~1/RELEASE_I386 i386
>
>     $ git describe
>     v2.0.0-beta7-79-gbcc196e
>
>     $ make
>     ==== Building LuaJIT 2.0.0-beta7 ====
>     make -C src
>     ...
>     OK        Successfully built LuaJIT
>     ==== Successfully built LuaJIT 2.0.0-beta7 ====
>
>     But maybe your latest OS X (or XCode) is newer than mine.
>
>     Alexander.
>
>
> Yes, looks like he has the latest pre-release one as it reports iOS 5.
> The unwind stuff is related to clang not gcc. Mike fixed it for the
> version I reported a bug on a while back, but looks like there are some
> slightly different issues now...
>
> Do they still ship gcc?
>
> Justin