Closed phil-blain closed 4 years ago
Thanks for the report @phil-blain.
If you're able to take a look at fixing it, the issue is probably in gfortran_osx-64-feedstock.
If not, @conda-forge/gfortran_osx-64 can you take a look?
LDFLAGS and HOST are set by more than one compiler and so it is not clear if they are related to gfortran. The other two were missed and can be added.
@chrisburr, @beckermr also I noticed none of the compiler activation/deactivation scripts have csh versions, would that be easy to add ?
This is a bigger ask. They are spread across multiple feedstocks. Do you have a list of what is needed?
I'm only working on mac and linux, and on these platforms an environment created with conda create -c conda-forge -n compilers compilers
has these scripts:
on Linux:
$ ls -1 $CONDA_PREFIX/etc/conda/activate.d
activate-binutils_linux-64.sh
activate-gcc_linux-64.sh
activate-gfortran_linux-64.sh
activate-gxx_linux-64.sh
on macOS:
$ ls -1 $CONDA_PREFIX/etc/conda/activate.d
activate-gfortran_osx-64.sh
activate_clang_osx-64.sh
activate_clangxx_osx-64.sh
(the deactivation scripts are the same)
Should be fixed now
Issue: the deactivation script for gfortran does not unset all variables set by the activation script on macOS. These variables stay defined:
Also, the deactivation script has a verbose output:
Environment (
conda list | grep -e compiler -e gfortran -e clang -e binutils -e ld
):Details about
conda
and system (conda info
):