Comment:
I have noticed that packages that I build with a rust component get this warning from conda-build:
WARNING (rustworkx): dso library package conda-forge/linux-64::libstdcxx-ng==13.2.0=h7e041cc_4 in requirements/run but it is not used (i.e. it is overdepending or perhaps statically linked? If that is what you want then add it to build/ignore_run_exports)
Searching around in conda-forge, I see that this warning seems to be issued for all rust packages except the ones that specify compiler('c') in their build requirements. I think this is because rust builds C-compatible shared libraries that link to libgcc? The feedstock currently specifies gcc_impl_{{ target_platform }} # [linux] as a run requirement for rust. Should it specify a more strong export? Or should it be standard practice to specify compiler('c') even when building a project that has only Rust code and not C? (And I acknowledge that it is unlikely to build a conda environment that doesn't pull in libgcc any way).
Comment:
I have noticed that packages that I build with a rust component get this warning from conda-build:
Searching around in conda-forge, I see that this warning seems to be issued for all rust packages except the ones that specify
compiler('c')in their build requirements. I think this is because rust builds C-compatible shared libraries that link to libgcc? The feedstock currently specifiesgcc_impl_{{ target_platform }} # [linux]as a run requirement forrust. Should it specify a more strong export? Or should it be standard practice to specifycompiler('c')even when building a project that has only Rust code and not C? (And I acknowledge that it is unlikely to build a conda environment that doesn't pull in libgcc any way).