Open chrstnnssnr opened 1 day ago
I wasn't able to replicate this under docker.
If you haven't already, could you try starting a new terminal window, and starting again from the source ./env/bin/activate
step in the instructions? On some systems conda doesn't fully pick up installed libraries until you start a new shell.
If that doesn't work or you've already tried it, could you post (or email me, joe. zuntz @ ed. ac. uk
- remove the spaces) the complete log in case I can spot anything?
Changing the cc compiler from the provided by Miniforge:
/data/astro/software/envs/cosmosis/bin/x86_64-conda-linux-gnu-cc
to the system one:
/bin/cc
seems to work.
$ /data/astro/software/envs/cosmosis/bin/x86_64-conda-linux-gnu-cc --version
x86_64-conda-linux-gnu-cc (conda-forge gcc 13.3.0-1) 13.3.0
$ /bin/cc --version
cc (GCC) 11.4.1 20230605 (Red Hat 11.4.1-2)
I would not expect that to work in general at runtime, though you may be lucky, depending what you need to run.
I'm following the instructions https://cosmosis.readthedocs.io/en/latest/intro/installation.html "Conda-Forge (from scratch)" on a Linux machine:
In the last step:
I get the following link errors during the class build
Both, ld and the gomp library are provided by the installation procedure that is suggested in the above mentioned instructions.