Reputation: 169
I upgraded to Anaconda 5 which comes with its own compiler toolset, i.e. does not use the OS-provided compilers anymore, see https://conda.io/projects/conda-build/en/latest/resources/compiler-tools.html. However, I need to use a different GCC compiler (since a library is apparently not available), but have been unsuccessful to set the correct path(s) and am not sure about the descriptions at the above link.
In short, how can I force the use of a certain (let's say OS-provided) gcc compiler when running a setup.py script within an Anaconda environment? Alternatively, how can I (temporarily) circumvent setting the path to the Anaconda compilers when activating an environment?
Upvotes: 1
Views: 654
Reputation: 169
Based on merv's helpful comment, I (temporarily) removed the contents of the bash script $CONDA_PREFIX/etc/conda/activate.d/activate-gcc_linux-64.sh
, re-activated the anaconda environment and successfully compiled with the paths set in the OS.
Edit: As added here by merv, $CONDA_PREFIX/etc/conda/deactivate.d/deactivate-gcc_linux-64.sh
might also be helpful.
Upvotes: 1