rely on run_exports for libgfortran in host env

conda-forge / openblas-feedstock

A conda-smithy repository for openblas.

BSD 3-Clause "New" or "Revised" License

9 stars 38 forks source link

rely on run_exports for libgfortran in host env #48

Closed minrk closed 5 years ago

minrk commented 6 years ago

Due to https://github.com/conda/conda-build/issues/2986 if the host env is null, run_exports won't be installed in the host env until conda-build gets a release.

libgfortran-ng appears to be unsafe to use with toolchain_fort due to https://github.com/conda-forge/toolchain-feedstock/pull/39

0.2.20 should get this fix as well because I think it's causing build failures such as this one

conda-forge-linter commented 6 years ago

Hi! This is the friendly automated conda-forge-linting service.

I wanted to let you know that I linted all conda-recipes in your PR (recipe) and found some lint.

Here's what I've got...

For recipe:

Failed to even lint the recipe, probably because of a conda-smithy bug :cry:. This likely indicates a problem in your meta.yaml, though. To get a traceback to help figure out what's going on, install conda-smithy and run conda smithy recipe-lint . from the recipe directory.

conda-forge-linter commented 6 years ago

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

minrk commented 6 years ago

This PR assumes that the comments discussing failed builds without adding libgfortran-ng was due to the conda-build bug not actually applying run_exports. If this build fails similar to that one, this assumption is probably wrong.