-
-
Notifications
You must be signed in to change notification settings - Fork 16
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
Missing objcopy
on Miniforge3 Docker
#59
Comments
I'm hesitant to do this as it would likely cause issues for packages building in conda-forge relying on Given this, is there a reason one can't install this themselves or grab it from the system? |
@jakirkham thanks for the reply. Yes, one can simply install the If there are non-trivial consequences to the latter, then it sounds better to leave it as is. |
Other ways to consider: either vendor a copy of objcopy and patch pyinstaller to use that or urge the developers of pyinstaller to switch to a solution that doesn't require dependency on objcopy (using some ELF library like py-lief or pyelftools). All objcopy is used for is this. |
Turns there is already a fallback in place, the path just doesn't get hit. Let's see what upstream devs have to say about pyinstaller/pyinstaller#5991 |
Issue
Running PyInstaller on condaforge/miniforge3:4.10.3-1 image fails to generate functional binaries. This is due to the assumption that linux-64 platform includes the
objcopy
command supplied bybinutils
. This could be remedied by addingbinutils
as a dependency.Recreate Steps
Result
Throws error message:
FileNotFoundError: [Errno 2] No such file or directory: 'objcopy'
Full Output
Expected Result
It should successfully build the binary.
Workaround
The error can be overcome by installing
binutils
. That is, running the above recreate steps, but withenables error-free running of the last step.
Recommended Solution
The feedstock maintainers should consider including
binutils
as a runtime dependency, at least forlinux-64
builds. The recipe should include a end-to-end test that would catch this failure in future builds.The text was updated successfully, but these errors were encountered: