-
Notifications
You must be signed in to change notification settings - Fork 415
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unexpected binary is None
in liefldd.py
#4787
Comments
Welp, just hit this as well, when it worked on Linux and Windows. Is it possible to work around it by downgrading to an earlier version of conda-build? |
Hi @h-vetinari, Thanks for filing this bug. I dug a little deeper on this, and it turns out our usage of this particular library in conda-build is a bit fragile. In my opinion, I think it's probably to time refactor https://github.com/conda/conda-build/blob/main/conda_build/os_utils/liefldd.py and reconsider the way we use the I've added the https://github.com/conda/conda-build/labels/good-first-issue label because this could be a reasonable task for someone new to the repository. Otherwise, we unfortunately cannot promise when this will be addressed. |
I don't think it's possible to work around this with an earlier version of conda-build. After viewing a git blame, I could see this code was added five years ago. I think the work around fix for this is to somehow force install the version of |
Looks like there's an upstream bug to track for this: lief-project/LIEF#873 |
The easiest way to work-around this would be to skip files ending with conda-build/conda_build/post.py Line 738 in c5146a0
Collecting of dependencies of .a static libraries have never worked and is not expected to work as they do not have dependency info on them.
|
I don't think that's a good approach. I've been hitting this issue because we are packaging LLVM, and it is crucial the |
I think you misunderstand (or I do!)... This is not a question whether we package static libs (there are cases that are unavoidable, like compiler-builtins that you mention), but whether we run the lief-machinery on them that inspects the artefacts for their dependencies (and fails). |
Any update? We're stuck because we need to build compiler-rt, and there are two PR that fix this exact issue. |
binary is None
in liefldd.py
binary is None
in liefldd.py
yes, I agree. I ran into same issue with llvm/clang 16 building ... I patched lief/conda-build for it |
I will share a PR with conda-build on the changes I made to it. In general it would be pretty good to have a switch in conda-build, which could be used to turn off the lief checks |
There are two unmerged PRs that solve this bug already.
They just need someone to review and merge one or the other.
…On Wed, 24 May 2023, at 18:12, Kai Tietz wrote:
I will share a PR with conda-build on the changes I made to it. In general it would be pretty good to have a switch in conda-build, which could be used to turn off the lief checks
—
Reply to this email directly, view it on GitHub <#4787 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAFIPSGP5ZJNQK3B7RH5YLLXHY6P5ANCNFSM6AAAAAAVII4MKI>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
I just read through them. I think they both fix the issue here in particular, but there might be a way to resolve it more generic. Btw why this filtering of file-endings was removed anyway. IIRC there was such a feature in the past, and now we attempt to run over any files in PREFIX with a lot of noise |
see as suggestion to fix this the pull 4900, which does this in a more general way |
Doesn't hurt to link it: #4900 Fine by me, whatever gets this resolved, thanks! :) |
Checklist
What happened?
With the last conda-smithy release, conda-forge is now back to using lief 0.12.3, and failing in conda-forge/compiler-rt-feedstock#61 with:
Conda Info
conda-forge CI for osx-64 / osx-arm64
Conda Config
conda-forge CI for osx-64 / osx-arm64
Conda list
host env:
build env:
Additional Context
Failing CI run here
The text was updated successfully, but these errors were encountered: