Skip to content
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

Package cannot be installed on M1 Macs #58

Closed
bryaan opened this issue Dec 20, 2021 · 12 comments
Closed

Package cannot be installed on M1 Macs #58

bryaan opened this issue Dec 20, 2021 · 12 comments

Comments

@bryaan
Copy link

bryaan commented Dec 20, 2021

I am trying to install but I get a build error. Running on M1 Mac.

julia> Pkg.build("CodecZlib")
    Building CodecZlib → `~/.julia/scratchspaces/44cfe95a-1eb2-52ea-b672-e2afdf69b78f/05916673a2627dd91b4969ff8ba6941bc85a960e/build.log`
ERROR: Error building `CodecZlib`:
┌ Warning: Platform `arm64-apple-darwin21.1.0` is not an officially supported platform
└ @ BinaryProvider ~/.julia/packages/BinaryProvider/U2dKK/src/PlatformNames.jl:450
ERROR: LoadError: KeyError: key "unknown" not found
@aryan-jain
Copy link

Facing the same issue. Any resolution?

@duanasq
Copy link

duanasq commented Jan 8, 2023

Facing same issue

@Ifihan
Copy link

Ifihan commented Mar 20, 2023

Hi, I'm also facing the same issue

@hare1039
Copy link

Hi, I have same error on the new mac os

ERROR: Error building `CodecZlib`: 
┌ Warning: Platform `arm64-apple-darwin22.4.0` is not an officially supported platform

@ViralBShah
Copy link
Contributor

Works fine on M1 for me. Please post more details on Julia version and such if still a problem.

@Ifihan
Copy link

Ifihan commented Aug 16, 2023

I just tried building and I got the same error as above. Installing it works fine. My Julia version is 1.8.1

Building CodecZlib → `~/.julia/scratchspaces/44cfe95a-1eb2-52ea-b672-e2afdf69b78f/05916673a2627dd91b4969ff8ba6941bc85a960e/build.log`
ERROR: Error building `CodecZlib`:
┌ Warning: Platform `arm64-apple-darwin21.5.0` is not an officially supported platform
└ @ BinaryProvider ~/.julia/packages/BinaryProvider/U2dKK/src/PlatformNames.jl:450
ERROR: LoadError: KeyError: key "unknown" not found

@ViralBShah ViralBShah reopened this Aug 16, 2023
@ViralBShah
Copy link
Contributor

BinaryProvider is no longer really used. So somehow you are picking up a very old release of this package, it seems - and it is trying to build some binaries and such.

@Ifihan
Copy link

Ifihan commented Aug 16, 2023

Sys.MACHINE gives "arm64-apple-darwin21.5.0". No, I am not running a MacOS Beta. I'm currently on Ventura.

@Ifihan
Copy link

Ifihan commented Aug 16, 2023

BinaryProvider is no longer really used. So somehow you are picking up a very old release of this package, it seems - and it is trying to build some binaries and such.

What should I do? Uninstall and re-install the package?

@ViralBShah
Copy link
Contributor

Yeah, try to update, or some other package is forcing an old version of this package. We stopped using BinaryProvider years ago. I would recommend at least using the latest Julia 1.8 release (or 1.9 if you can), and updating the packages. You can also look at Pkg.status() to see what might be holding it back.

@giordano
Copy link
Member

BinaryProvider hasn't been used in this package for over 3 years, since #49. If BinaryProvider is involved here, coming from this package, an extremely old version of the package is being used

@Ifihan
Copy link

Ifihan commented Aug 17, 2023

After uninstalling and reinstalling the package, I was able to resolve the issue successfully. In the process, I identified a reason that could be causing this problem.

One of the contributing factors was that some packages were still relying on the 0.6.0 version, which resulted in errors in the M1 architecture. For instance, I had the StackOverflow package and it was utilizing the 0.6.0 version of CodecZlib. To address this, I experimented with a solution. I first installed the latest version of CodecZlib and then added the StackOverflow package. Upon inspecting the package statuses, I noticed that the version of CodecZlib reverted back to 0.6.0, accompanied by a warning message

Info Packages marked with ⌅ have new versions available but cannot be upgraded. To see why use status --outdated -m

To investigate further, I executed the command mentioned in the warning: status --outdated. The outcome of this command was a display similar to the image shown below:

image

As a result, I devised a potential solution to the issue. My approach involves executing the status --outdated command to identify which packages are utilizing the outdated version of CodecZlib and triggering the error. Subsequently, the CodecZlib version in those specific packages to prevent encountering this error in the future.

Thank you @ViralBShah and @giordano for taking time to attend to this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants