tests/test_api_build.py::test_sysroots_detection failure

[kenodegard]

tests/test_api_build.py::test_sysroots_detection implemented here is now failing on main, see https://github.com/conda/conda-build/actions/runs/10671805383/job/29578195906

Originally posted by @kenodegard in #5404 (comment)

[kenodegard]

Is this caused by conda-forge/ctng-compilers-feedstock#148?

cc @h-vetinari @isuruf

[isuruf]

Is this caused by conda-forge/ctng-compilers-feedstock#148?

Yes, the solution was to add an empty host section

[kenodegard]

Is this caused by conda-forge/ctng-compilers-feedstock#148?

Yes, the solution was to add an empty host section

Already attempted to do that and it doesn't resolve the failure (see #5476)

I've gotten the tests to pass again by adding ignore_run_exports_from (see #5471) inspired by changes done to other conda-forge recipes (conda-forge/ctng-compilers-feedstock#148 (comment))

[isuruf]

Oh we have

conda-build/conda_build/post.py

Lines 1327 to 1328 in abb3f18

	if subdir.startswith("linux"):
	ignore_list.append("libgcc-ng")

. We can just add libgcc too

[kenodegard]

Wouldn't it be more appropriate to add a selector to conda-forge::libgcc's run_exports instead of adding more hardcoded conditions into conda-build?

[isuruf]

Wouldn't it be more appropriate to add a selector to conda-forge::libgcc's run_exports instead of adding more hardcoded conditions into conda-build?

What do you mean? Can you explain more about the selectors?

[kenodegard]

Can't we just do something like the following in https://github.com/conda-forge/ctng-compilers-feedstock:

outputs:
  - name: gcc_impl_{{ cross_target_platform }}
    run_exports:                      # [not linux]
      strong:                         # [not linux]
        - libgcc >={{ gcc_version }}  # [not linux]

[isuruf]

That's not the issue. The C compiler adds a libgcc (it was libgcc-ng before) dependency to all packages that were compiled with the compiler, but libgcc_s.so is not always needed for a program compiled with the C compile gcc. The overlinking check however complaints when a conda package with a DSO like libgcc_s.so is added to run due to a run_exports, but is unused.

[kenodegard]

oops, I was checking stuff on the wrong platform

gotcha, we want the overlinking/overdepending checks to be run on a subset of run_exports, and this cannot be achieved in the upstream package, so either every downstream package defines their own ignore_run_exports_from or we make your suggested change in conda-build