OSX linker errors trying to update 2 different python/C++ feedstocks

Issue: see https://github.com/conda-forge/humanleague-feedstock/pull/7 and https://github.com/conda-forge/neworder-feedstock/pull/7

The errors seem identical in both, e.g. from the humanleague PR

I’m trying to update the version of this package and 2 of the builds (both OSX) are failing with:

2020-11-07T14:03:44.4972520Z   clang-10: error: -Wl,-export_dynamic: 'linker' input unused [-Werror,-Wunused-command-line-argument]
2020-11-07T14:03:44.4996480Z   error: command 'x86_64-apple-darwin13.4.0-clang' failed with exit status 1
2020-11-07T14:03:44.5178070Z   Building wheel for humanleague (setup.py): finished with status 'error'

I could silence this by adding -Wno-unused-command-line-argument (if I knew where to put it, which I don’t) but it’s probably not the best solution anyway. The other OSX build is fine (despite using the same version of clang), but does emit this warning:

2020-11-07T14:01:19.6837930Z   ld: warning: -pie being ignored. It is only used when linking a main executable

which I’m assuming is relevant. I’ve no idea where the -fPIE flag has come from, it’s not in my setup.py and its not appropriate here as the target is a library? So I’m stumped, can anybody help please?

[virgesmith]

all done now, thanks @isuruf

[isuruf]

then you just have -fPIE -Wno-unused-command-line-argument in your CFLAGS and everyone is happy?

That’d make autoconf scripts go crazy.

But fair enough, if neworder 0.0.8 had the warning but not the 2 failures, then I wonder if its a red herring that the failures are due to the same warning being promoted to an error? It could be another unused link arg?, sadly clang’s error message isn’t expliciit. Anyway I’ll update one of the packages over the weekend and see if that fixes it…

The only error is the -Wl,-export_dynamic being unused. -fPIE is a harmless warning. You should remove https://github.com/virgesmith/neworder/blob/master/setup.py#L36 as compiler warnings increase in every new compiler version and then you’ll have to have workarounds. You should only add them in your CI scripts.