You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@mxnet.apache.org by GitBox <gi...@apache.org> on 2017/12/07 10:26:47 UTC

[GitHub] mjmg commented on issue #8974: MXNET compatibility with MKL libraries bundled in Microsoft R Open

mjmg commented on issue #8974: MXNET compatibility with MKL libraries bundled in Microsoft R Open
URL: https://github.com/apache/incubator-mxnet/issues/8974#issuecomment-349926412
 
 
   I already did something equivalent for the libraries in /usr/local/lib prior to make rpkg
   ```
   # echo "/usr/local/lib" >> /etc/ld.so.conf.d/local-lib.conf
   # ldconfig
   ```
   These are my make flags for building mxnet for MKL CPU acceleration when since mxnet 1.0.0 came out:
   ```
   USE_OPENCV=1 USE_BLAS=mkl USE_MKLML=1 USE_MKL2017=1 USE_MKL2017_EXPERIMENTAL=1  USE_GPERFTOOLS=1
   ```
   
   But it seems if I add the flag "USE_LAPACK=1", there are incompatibilities with "USE_BLAS=mkl" with several lapack routines unable to be found during linking stage if I don't install LAPACK development packages separately. Since there are LAPACK routines in the following libraries from MRO:
   ```
   libmkl_core.so      
   libmkl_gnu_thread.so  
   libRblas.so 
   libgfortran.so.1  
   libmkl_gf_ilp64.so  
   libmkl_vml_def.so     
   libRlapack.so
   libiomp5.so       
   libmkl_gf_lp64.so   
   libmkl_vml_mc3.so     
   libR.so
   ```
   I was wondering if MXNET could be able to link from these without downloading the full MKL installation or installing openblas/atlas/lapack separately.

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services