z/OS Tools & Language

Expand all | Collapse all

Conda Install Problem

  • 1.  Conda Install Problem

    Posted 01-20-2021 16:49


    After installing Miniconda (v 1.2.1) I tried creating a new environment and installing a package to it, for example: 

    conda create -n curl

    conda activate curl

    conda install .. curl

    The conda create and activate worked fine but the install produced several messages like as follows:

    IBMUSER:/u/ibmuser: >conda install -c https://conda.anaconda.org/zoss-appdev gzip
    compile command returned 65280
    Failed to load /u/ibmuser/.ffi/i_.so: CEE3501S The module /u/ibmuser/.ffi/i_.so was not found.
    No ffi call function could be found or created
    compile command returned 65280
    Failed to load /u/ibmuser/.ffi/v_iiPi.so: CEE3501S The module /u/ibmuser/.ffi/v_iiPi.so was not found.
    compile command returned 65280

    I was able to circumvent the error but copying the missing files from the Miniconda install lib/ffi directory, but I wonder if I missed something during the Miniconda install/config?



    Greg Keuken
    Systems Programmer

  • 2.  RE: Conda Install Problem

    Posted 01-21-2021 05:25
    Hi Greg Keuken,

    Make sure the FFI_LIB environment variable is set correctly: env | grep FFI_LIB
    it must be set to "$CONDA_PREFIX/lib/ffi" when activating the base environment

    So, your problem might be that you forgot to run the command 'conda activate base' before 'conda create -n curl' etc.


    Alexander Klochkov
    Rocket Software

  • 3.  RE: Conda Install Problem

    Posted 01-21-2021 08:39

    Thanks Alexander,

    I didn't see 'conda activate base' as a requirement in the Miniconda PDF doc for creating new environments. Perhaps this should be added?

    This did indeed solve the problem, however, now I run into another minor issue. It seems that after creating a new environment and activating only that new environment after a logon, any further conda commands (like conda info --env or conda list) will still produce the above error messages.

    So for example:

    I logon to z/OS USS (WITHOUT doing conda activate base) .. I can run conda commands without the CEE3501S errors. Note that FFI_LIB environment variable is NOT set at this point.

    I run:

    conda activate base

    conda create -n test

    conda install .. gzip

    conda activate test

    at this point everything is working fine .. but 

    I then update users .bashrc to only activate the new environment (eg. 'conda activate test') and after logging back on to USS other conda commands (like conda list) will produce CEE3501S errors unless I export FFI_LIB variable, or 'conda activate base' AND then 'conda activate test'.


    Greg Keuken
    Systems Programmer

  • 4.  RE: Conda Install Problem

    Posted 01-26-2021 11:04
    Hello Greg,
    This information is not included into documentation, because it is not mandatory: directory $HOME/.ffi with all required files should be automatically created when you run conda commands. However, it doesn't happen in your environment. We are going to investigate that. Note, that the engineers have to prioritize support assistance for customers that are paying for support, so the research might take time.
    There is another workaround to skip activating base environment. You need to install libffi package into each environment, you are going to use. When you activate the environment FFI_LIB environment variable will be set.

    Tatiana Balaburkina
    Rocket Software