-
Notifications
You must be signed in to change notification settings - Fork 60
[WIP] Fixes for OS X #743
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
[WIP] Fixes for OS X #743
Conversation
This is needed to fix the error described here: http://stackoverflow.com/questions/17691176/ Unfortunately upstream only distributes a large patch on top of the latest 5.9 release, so I created a github repository for the code and just use that.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think I should add a check that /usr/include/dispatch/object.h exists in the first place, and then also do this fix for OS X 10.10 only.
This fixes a build failure on OS X 10.10. Unfortunately, this disabled https access, so it is only enabled if 'disable_crypto' parameter is 'true'.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This disables https support, so it is not a solution. It makes git build with our gcc at least, so that's why I did it, but we need to find a real solution.
|
@ahmadia, @cekees these are changes that I needed to make to get at least some initial profile working with Hashdist's gcc (see #741). Many packages still fail to build. The above must work, so we just need to figure out the proper fixes to some of the hacks that I had to do in this PR. I would appreciate any feedback or help with this. I am new to OS X. How do you use Hashdist on OS X? Do you just use the native Apple clang? If so, how do you compile Fortran packages? Any alternative way to use Hashdist must also work. |
|
@certik I think if the updates are logical commits its fine for it to be in one merge |
I should probably split this into several PRs, but I am posting it here so that others can use it already.
It also needs to be tested on linux.