strong run_exports not crossing boundaries?

[nehaljwani]

CB 3.2.0 and C 4.4.4

(base) bm-osx109-01:test builder$ cat build.sh 
stat $PREFIX/lib/libc++.dylib

(base) bm-osx109-01:test builder$ cat meta.yaml 
package:
  name: test
  version: 1.0.0

requirements:
  host:
   - make
  build:
   - {{ compiler('cxx') }}

A run of conda build fails with:

stat: /Users/builder/nwani/m3/conda-bld/test_1514579903346/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_place/lib/libc++.dylib: stat: No such file or directory

But clangxx has:

strong: [libcxx  >=4.0.1]

The build above passes up to CB 3.1.3, after that, it breaks.

[mingwandroid]

You mean CB 3.2.0 I guess?

[mingwandroid]

So the last version that worked OK here is CB 3.1.2?

[nehaljwani]

Sorry, yes, I meant CB 3.2.0. Updated it.
And the last version that worked okay was 3.1.3

[msarahan]

This bug is because the top-level metadata was never being "finalized" - that's when the run_exports stuff gets handled. This is re-raising the need to handle build-time environments differently from any outputs. The top-level output conflates the two, and makes things messy.

[github-actions]

Hi there, thank you for your contribution!

This issue has been automatically locked because it has not had recent activity after being closed.

Please open a new issue if needed.

Thanks!