Message-ID: <dc41e1260903180517i10ede2e1p73d2bf0750ac2d6b@mail.gmail.com>
Date: 2009-03-18T12:17:26Z
From: Ei-ji Nakama
Subject: R with MKL
In-Reply-To: <fb1538e20903172251u3ad9cd64lcc27d305b26acdce@mail.gmail.com>
Hi Cristi?n.
>> However, It is a little different.( -lgomp and configure line)
>>
>> MKL=" ? -L$@{MKL_LIB_PATH@} ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? \
>> ? ? ? ?-Wl,--start-group ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? \
>> ? ? ? ? ? ? ? ?$@{MKL_LIB_PATH@}/libmkl_gf_lp64.a ? ? ? ?\
>> ? ? ? ? ? ? ? ?$@{MKL_LIB_PATH@}/libmkl_gnu_thread.a ? ? \
>> ? ? ? ? ? ? ? ?$@{MKL_LIB_PATH@}/libmkl_core.a ? ? ? ? ? \
>> ? ? ? ?-Wl,--end-group ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? \
>> ? ? ? ?-lgomp -lpthread"
>> ./configure --with-blas="$MKL" --with-lapack="$MKL"
>>
> ...
>
> Thanks for all your answers. I read carefully the userguide and the
> admin guide. I now understand that with gfortran I need to use
> libmkl_gf_lp64 and libmkl_gnu_thread, either shared or static.
> Unfortunately for MKL version 10.1.1.019, libmkl_gnu_thread links
> against the symbol "_gfortran_internal_malloc64" which was present in
> gcc-4.1 and is not present anymore in gcc-4.3.
However, the support of openmp is gcc-4.2 or latter.
> So my alternatives are installing an older compiler, waiting for a
> newer MKL version, building R with Intel compiler or switching away
> from MKL.
Please download the following files, and test the procedure to which
the file is written first.
http://prs.ism.ac.jp/~nakama/mkl/mkl_gf.c
--
EI-JI Nakama <nakama (a) ki.rim.or.jp>
"\u4e2d\u9593\u6804\u6cbb" <nakama (a) ki.rim.or.jp>