[GitHub] fhieber commented on issue #8532: mxnet-mkl (v0.12.0) crash when using (conda-installed) numpy with MKL

[GitBox <gi...@apache.org>]

fhieber commented on issue #8532: mxnet-mkl (v0.12.0) crash when using (conda-installed) numpy with MKL
URL: https://github.com/apache/incubator-mxnet/issues/8532#issuecomment-359745503
 
 
   @ykim362 I just tried this again in a Docker image with `mxnet-cu90mkl==1.0.0.post4` and the following `conda info` output:
   ```
                  platform : linux-64
             conda version : 4.3.30
          conda is private : False
         conda-env version : 4.3.30
       conda-build version : not installed
            python version : 3.6.3.final.0
          requests version : 2.18.4
          root environment : /opt/conda  (writable)
       default environment : /opt/conda
          envs directories : /opt/conda/envs
                             /root/.conda/envs
             package cache : /opt/conda/pkgs
                             /root/.conda/pkgs
              channel URLs : https://repo.continuum.io/pkgs/main/linux-64
                             https://repo.continuum.io/pkgs/main/noarch
                             https://repo.continuum.io/pkgs/free/linux-64
                             https://repo.continuum.io/pkgs/free/noarch
                             https://repo.continuum.io/pkgs/r/linux-64
                             https://repo.continuum.io/pkgs/r/noarch
                             https://repo.continuum.io/pkgs/pro/linux-64
                             https://repo.continuum.io/pkgs/pro/noarch
               config file : None
                netrc file : None
              offline mode : False
                user-agent : conda/4.3.30 requests/2.18.4 CPython/3.6.3 Linux/4.9.58-18.51.amzn1.x86_64 / glibc/2.17
                   UID:GID : 0:0
   ```
   
   I still observe the same crash:
   ```
   > OMP: Error #15: Initializing libiomp5.so, but found libiomp5.so already initialized.
   > OMP: Hint: This means that multiple copies of the OpenMP runtime have been linked into the program. That is dangerous, since it can degrade performance or cause incorrect results. The best thing to do is to ensure that only a single OpenMP runtime is linked into the process, e.g. by avoiding static linking of the OpenMP runtime in any library. As an unsafe, unsupported, undocumented workaround you can set the environment variable KMP_DUPLICATE_LIB_OK=TRUE to allow the program to continue to execute, but that may cause crashes or silently produce incorrect results. For more information, please see http://www.intel.com/software/products/support/.
   ```

----------------------------------------------------------------
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