[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Getfem-users] Compilation problem on Mac 10.9
From: |
Walker, Ryan T. (GSFC-615.0)[UNIV OF MARYLAND] |
Subject: |
Re: [Getfem-users] Compilation problem on Mac 10.9 |
Date: |
Fri, 13 Feb 2015 21:03:26 +0000 |
I’ve fixed the problem and successfully installed. I had to set MATLAB_RELEASE
in interface/src/matlab/gfm_common.h,
and later set the extension on the gf_matlab file (mexmaci64 for me) to get
make install to work.
On Feb 11, 2015, at 5:30 PM, Walker, Ryan T. (GSFC-615.0)[UNIV OF MARYLAND]
<address@hidden> wrote:
> I’m trying to compile on Mac OS X 10.9 with Matlab 2014a. I read previous
> posts about problems with clang and superlu, so I’m using gcc 4.9 (obtained
> from Sourceforge) installed in /usr/local/bin.
>
> First I ran ./configure --with-pic --enable-matlab --enable-python="no"
> CC="/usr/local/bin/gcc -arch x86_64" CXX="/usr/local/bin/g++ -arch x86_64"
>
> I noticed that this didn’t find my Matlab release or path.
>
> Compilation ends with this error:
>
> Making all in private
> make[5]: Nothing to be done for `all'.
> make[5]: Nothing to be done for `all-am'.
> ../../../bin/extract_doc ./.. matlab-com || (rm -f gf_mesh.m; /bin/false )
> mex -largeArrayDims -output gf_matlab -g CDEBUGFLAGS="-O3 -fPIC"
> LD="/usr/local/bin/g++ -arch x86_64" \
> -I. -I./.. -DMATLAB_RELEASE= \
> ./gfm_mex.c ./gfm_common.c ./../gfi_array.c \
> ../.libs/libgetfemint.a ../../../src/.libs/libgetfem.a -lmuparser
> -lblas -llapack || (rm gf_matlab; false)
> Building with 'Xcode with Clang'.
> /Users/rtwalker/getfem-4.3/interface/src/matlab/gfm_mex.c:127:20: error:
> invalid token at start of a preprocessor expression
> #if MATLAB_RELEASE == 12
> ^
> 1 error generated.
>
> rm: gf_matlab: No such file or directory
> make[4]: *** [gf_matlab] Error 1
> make[3]: *** [all-recursive] Error 1
> make[2]: *** [all-recursive] Error 1
> make[1]: *** [all-recursive] Error 1
> make: *** [all] Error 2
>
> I really don’t know what to make of this. Suggestions would be greatly
> appreciated!
>
> Thanks,
> Ryan
>