Overlinking warnings against python and some system32 dlls in windows?

[lgray]

Over in https://github.com/conda-forge/numpy-feedstock/pull/361, we see a litany of overlinking warnings in windows concerning python<VERSION>.dll and a .dll in System32 (which I assume is OK). Here is an example.

Are these benign? I am assuming so since the build does pass the CI, but for something as big as numpy it becomes necessary to ask.

We also see an overlinking warning against /usr/lib/libSystem.B.dylib on macos, but prior (still open!) issues indicate this is indeed benign.

Any pointers or tips are appreciated!

@rgommers

[rgommers]

The recipe does contain:

  run:
    - python

so the warnings for python3*.dll are spurious it looks like.

The two Scripts executables are .exe's generated by rattler-build itself from:

  python:
    entry_points:
      - if: win
        then:
          - f2py = numpy.f2py.f2py2e:main
          - numpy-config = numpy._configtool:main

so those warnings have to be spurious as well.

[lgray]

I agree with your analysis. Still, a sign-off from the rattler-build folks would be helpful.

[zelosleone]

Yeah, they do seem benign to me as well. When we added and made our .dll list for system libraries, it was only for the libraries that are by default in windows/unix systems. I guess we need to think some ways to dynamically enchance the python part without adding python library as system library. But for now, you can indeed ignore these would be my opinion.

[lgray]

Thanks for taking a look and thinking about it. We'll move forward!

[rgommers]

I guess we need to think some ways to dynamically enchance the python part without adding python library as system library.

Perhaps easy to filter as a separate step, since python*.dll can be added for any Python extension module, and those are easy to recognize from the file extensions (.pyd on Windows, .cpython*.so or abi3.so on other platforms)?