joezuntz/cosmosis

Compiler error Ubuntu Instalation

eduardojsbarroso opened this issue · 2 comments

Hi. I'm trying to install cosmosis in a conda enviroment but I keep getting the same error when trying to run make in the library. i have tried to change the python version and I'm still getting the same error. Here is the log:

+ make
make: Entering directory '/home/eduardo/firecrown/cosmosis-standard-library'
make[1]: Entering directory '/home/eduardo/firecrown/cosmosis-standard-library/boltzmann'
make[2]: Entering directory '/home/eduardo/firecrown/cosmosis-standard-library/boltzmann/isitgr'
cd camb_Jan12_isitgr && make libcamb.so
make[3]: Entering directory '/home/eduardo/firecrown/cosmosis-standard-library/boltzmann/isitgr/camb_Jan12_isitgr'
/home/eduardo/miniconda3/envs/firecrown_developer/bin/x86_64-conda-linux-gnu-gfortran -O3 -g -fPIC -fopenmp -I/home/eduardo/miniconda3/envs/firecrown_developer/lib/python3.11/site-packages/cosmosis/datablock -std=gnu -ffree-line-length-none -I. -c constants.f90
/home/eduardo/miniconda3/envs/firecrown_developer/bin/x86_64-conda-linux-gnu-gfortran -O3 -g -fPIC -fopenmp -I/home/eduardo/miniconda3/envs/firecrown_developer/lib/python3.11/site-packages/cosmosis/datablock -std=gnu -ffree-line-length-none -I. -c utils.F90
f951: internal compiler error: in cpp_diagnostic_at, at libcpp/errors.c:41
0x7f5f04842082 __libc_start_main
        ../csu/libc-start.c:308
Please submit a full bug report,
with preprocessed source if appropriate.
Please include the complete backtrace with any bug report.
See <https://github.com/conda-forge/ctng-compilers-feedstock/issues/new/choose> for instructions.

I appreciate the help.

Hi there. Is this an existing conda environment that you are adding things to, or a fresh one?

You might need to follow the instructions it gives, this seems to be a gfortran error.

What Ubuntu version are you on?

I'm using Ubuntu 20.04. I tried reinstalling conda, the enviroment, everything and nothing worked. Eventually I reinstalled everythin in my ubuntu and it worked, so it was probably some package conflit. Thank you for the help.