Fix lapack for conda_builder_linux from ContinuumIO/docker-images#658
Conversation
|
Perfect, I think this is exactly what's needed. gcc should be removed from meta.yaml, but libgcc might need to stay in. The reason is that the docker build image contains runtimes that are potentially (probably) newer than system ones. These are backwards compatible, but any code you compile with the docker image may not find the symbols it needs in older runtimes. This libgcc is a bit of a work in progress. If you need it now, grab it from my anaconda.org channel: The one on the defaults channel should soon be updated to be the same. The tricky detail about doing things with GCC the way that we have is that our runtimes need to always be the same or newer version than the system libraries. Ideally, compiler requirements could be made explicit, or at the very least, encoded into readily accessible metadata. We sort of do that on Windows, since each version of Python uses a different version of Visual Studio. This is another WIP, and the most current issue on the topic is at conda/conda-build#848 - we'd welcome your thoughts on the topic. |
|
@msarahan great! Thanks for the explanation and the hint about libgcc. |
See anaconda/docker-images#23
ping @msarahan
Actually I would need to remove both
gccandlibgccfrom meta.yaml for this to work out of thebox with
conda_builder_linux.What is the policy for adding compiler requirements in conda-recipes? My take is that
they can be kept in the recipe but commented out.