On 02/12/10 14:59, Christian Marquardt wrote:
Hi,
I've run into a minor glitch when trying to install rpy 2.1.9 with R
2.12 and Python 2.7.1 when using Intel'ls MKL.For compiling R, the
specification of the MKL libs looks something like this:
... -Wl,--start-group -lmkl_intel -lmkl_sequential -lmkl_core
-Wl,--end-group -lpthread ...
where the -Wl,--start-group and -Wl,--end-group are taken from Intel's
link advisor (see
http://software.intel.com/en-us/articles/intel-mkl-link-line-advisor/).
Unfortunately, the setup.py isn't prepared to accept these linker
options and complains when getting them in its RConfig class. The
attached patch solved the problem for me.
Thanks for the patch, however at first sight I am surprised that is it
really working for you.
Wouldn't
'^(?P<extra_link_args>-Wl.+)$'
be better ?
More generally, is it really a good idea to check arguments to the
compiler when trying to build Rpy?
Yes and no.
No: people may have different tweaks and compiler and not all of them
can be anticipated
Yes: this is making sure that nothing unexpected is happening, and
something does abort. This procedure helped solve installation-specific
issues quicker than it would have otherwise (especially when the
problems are reported by users with limited experience/interest in the
details of compiling Python extensions). It is also making the code for
parsing of paths and libraries somewhat clear and explicit, and let
setup.py rely rather simply on the package building infrastructure in
distutils. Also the people with less-common compiling options are hoped
to able to identify precisely a problem they might encounter and provide
a patch.
Every user might have a differently
tweaked environment, and trying to support them all seems like a
nightmare to me.
Believe it or not, this is far from a nightmare to support this way.
If I understand the code correctly, the compiler
options are obtained from the R setup, and should reflect those used
to compile R - is that correct? But if R has been installed
successfully, the compiler and linker options should be ok, no?
The detail is that distutils wants for example an include _directory_
rather than '-I/my/include/are/there', requiring us to parse the
directory out of the string.
Having that said, I might have missed something and I would read with
great interest a patch to reform the setup.py.
Best,
Laurent
Kind regards,
Christian.
------------------------------------------------------------------------------
Increase Visibility of Your 3D Game App& Earn a Chance To Win $500!
Tap into the largest installed PC base& get more eyes on your game by
optimizing for Intel(R) Graphics Technology. Get started today with the
Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs.
http://p.sf.net/sfu/intelisp-dev2dev
_______________________________________________
rpy-list mailing list
rpy-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/rpy-list
------------------------------------------------------------------------------
Increase Visibility of Your 3D Game App & Earn a Chance To Win $500!
Tap into the largest installed PC base & get more eyes on your game by
optimizing for Intel(R) Graphics Technology. Get started today with the
Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs.
http://p.sf.net/sfu/intelisp-dev2dev
_______________________________________________
rpy-list mailing list
rpy-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/rpy-list
