-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
Mac OS binaries looking for libgfortran #4315
Comments
This is definitely a bug. The binary build should not have a dependency on |
Yes, definitely a bug, but it's not looking for a compiler, but the cc @staticfloat |
Right - it looks like the same type of problem as : #1703 |
This should be addressed in 22f7d4f, please redownload the latest binary and retry. |
Seems to be working now, though when I call
Not sure if that's just a separate LAPACK-related problem. I can open a new issue for that if so. |
Those are normal. We actually have an issue about suppressing those
|
We've had numerous issues with BLAS/LAPACK symbol conflicts in the past, e.g. #1642; it seems like this keeps popping up. |
#1642 is a different issue. Same symptoms, but different underlying cause. The cause of this is that we're linking against Accelerate, and various libraries pull the BLAS symbols into the current namespace multiple times. Since they are the same symbols, the warnings are harmless. #3342 is the issue I was thinking of that would perhaps give us more control over when those warnings are printed and when they aren't. I'm glad it's working for you, @carljv! I'm going to close the issue now. |
I've installed the Mac OS binary beta version above and am running into an odd problem. When I call a function like
Base.inv
, I get the following error:Now, I have a gfortran compiler installed (via Homebrew, but a 4.7 version -- there's no directory for 4.8.1 like Julia seems to be looking for here). But I find it odd that the binary is looking for a compiler like this anyway. Am I missing something in the install?
Thanks,
-c.
The text was updated successfully, but these errors were encountered: