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

Fix build for macOS Sierra + LLVM 3.9. #18910

Merged
merged 2 commits into from
Dec 30, 2016
Merged

Fix build for macOS Sierra + LLVM 3.9. #18910

merged 2 commits into from
Dec 30, 2016

Conversation

andreasnoack
Copy link
Member

@andreasnoack andreasnoack commented Oct 13, 2016

According to this comment this change shouldn't be a problem.

(edit by tkelman - closes #19762)

@kshyatt kshyatt added building Build system, or building Julia or its dependencies system:mac Affects only macOS labels Oct 13, 2016
@tkelman
Copy link
Contributor

tkelman commented Oct 13, 2016

We'd need to update all places that list 10.7 as the minimum supported version.

@andreasnoack
Copy link
Member Author

I'm not sure that this changes the minimum required version. This PR only changes the minimum requirement when USE_LIBCPP=1 and that is only the default for OS X >= 10.9 .

@tkelman
Copy link
Contributor

tkelman commented Oct 14, 2016

If the binaries get built on a newer system than that, then this will change the minimum supported version.

@andreasnoack
Copy link
Member Author

So https://status.julialang.org/download/osx10.7+ should be changed. Are there other places?

@tkelman
Copy link
Contributor

tkelman commented Oct 14, 2016

The downloads page, readme, documentation, anywhere else we refer to 10.7

@andreasnoack
Copy link
Member Author

I've changed the places that matched "10.7" but I didn't see any matches in the documentation and the readme is about building Julia which is still possible on 10.7 as mentioned. Is the download link on the download page automatically generated or should I open PR for the homepage? Please be specific if you want other places to be changed.

$julianightlies/osx/x64/$majmin/julia-$majminpatch-$shashort-osx.dmg
cp "julia-$version-osx10.7 .dmg" "julia-$majmin-latest-osx10.7 .dmg"
cp "julia-$version-osx10.8 .dmg" "julia-$majmin-latest-osx10.8 .dmg"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this isn't correct unless the buildbots get changed

@tkelman
Copy link
Contributor

tkelman commented Oct 14, 2016

The downloads page is not autogenerated, so yes check the website as well.

I don't know where they all are, we'll need to look and double-check to avoid leaving incorrect information. The buildbots determine the binary names in many cases.

@andreasnoack
Copy link
Member Author

@tkelman Could you please recap the steps most convenient for merging of this. Should the buildbot setup change before or after this PR to minimize the problems/misleading info?

@tkelman
Copy link
Contributor

tkelman commented Nov 11, 2016

This is somewhat coupled to #18554 which is proposing renaming the binary download file names, but isn't quite settled yet in terms of all the various places that will need to have links updated.

The changes should at least be prepared before this merges. That way once they're ready we can merge everything around the same time.

@tkelman
Copy link
Contributor

tkelman commented Dec 29, 2016

We'd need to update all places that list 10.7 as the minimum supported version.

@staticfloat how many places and filenames is this that you can think of? release filenames, links, buildbot info...

Alternately, could we stub out future_error so our LLVM 3.9 build maintains osx 10.7 compatibility to fix #19762?

@tkelman
Copy link
Contributor

tkelman commented Dec 29, 2016

I'm going to push a commit to this branch that makes the default build 10.8+, but allow setting a makefile variable to modify that. The buildbots don't build Julia from 10.12, so we can maybe keep it at 10.7 there by setting the variable appropriately.

@staticfloat
Copy link
Member

@staticfloat how many places and filenames is this that you can think of? release filenames, links, buildbot info...

The only places I can think of are the actual naming of binaries, so that would include download URLs and the like. The only reason we had the 10.7+ on the end of filenames was we used to have a 10.6 version of Julia as well for a while. As you've noted, #18554 will drop this completely, so perhaps we don't have to worry about this too much.

so we can potentially adjust buildbots to still build 10.7-compatible binaries
@ViralBShah
Copy link
Member

10.8 was released 4 years ago. Seems reasonable to make it the min supported OS.

@tkelman tkelman merged commit 4dc0edb into master Dec 30, 2016
@tkelman tkelman deleted the anj/osx branch December 30, 2016 05:51
@tkelman
Copy link
Contributor

tkelman commented Dec 30, 2016

If necessary and if dropping 10.7 gets us anything in return, sure. it shouldn't actually be needed yet if building on 10.11 or earlier and setting this variable to 10.7, which we can do on the buildbots.

@stevengj
Copy link
Member

(Meanwhile, people on the mailing list are still complaining about Windows XP. Thank goodness no one is bugging us for MacOS 10.1 support.)

@tkelman
Copy link
Contributor

tkelman commented Dec 30, 2016

it would be a very small patch to bring back xp support, at least part of the way. don't think you can say that about powerpc 32 bit macs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
building Build system, or building Julia or its dependencies system:mac Affects only macOS
Projects
None yet
Development

Successfully merging this pull request may close these issues.

build failure on macOS
6 participants