[libjulia] Add v1.6.0#1987
Conversation
ca11004 to
4dd62ae
Compare
| @@ -0,0 +1,2 @@ | |||
| include("../common.jl") | |||
| build_julia(v"1.6-dev"; gitref = "d474c98667db0bf4832e4eeb7beb0e8cfc8b7481") | |||
There was a problem hiding this comment.
Regarding the version, perhaps we should imitate what Julia itself does, and use something like 1.6.0-DEV.1390 as version. (I'd not bother to replicate the code for computing the integer '1390' but rather copy it manually from a build of the given git commit).
Sounds OK?
There was a problem hiding this comment.
You can also use contrib/commit-name.sh to map from a git sha to a julia build name.
There was a problem hiding this comment.
Sure, but I don't see how that helps, as the build script which has access to this is only run inside the build_tarballs function, which already requires the version as an argument?
4dd62ae to
5f35bb6
Compare
b9c8b61 to
e139e30
Compare
|
Trying to build libjulia 1.6 to see if it will fix the macOS problems for libcxxwrap-julia, but it errors differently here than on my own machine. Here the result is: On my local attempt I get a 404 error from curl when downloading |
|
Which macOS problem do you mean? For JuliaLang/julia#38925 there is a pending PR. This JLL here currently does not really work due to the fake JLL work; I'll update it once there is a chance, but this isn't a priority as the binary for Julia 1.5 ought to work (the issues preventing it from working right now would affect the results of this PR from working, too) |
eb7a52e to
4eba925
Compare
|
Yes, that is the one, I hadn't seen that issue, but concluded from JuliaLang/julia#38829 that a 1.6 JLL was needed. If that won't fix it, this isn't urgent. |
|
It'd be nice to resume this now that v1.6 isn't that far away 🙂 |
9305825 to
054283d
Compare
|
|
We need to update: to be |
|
Ok, manually setting |
|
Yeah it's trying to download: But that has the cc: @staticfloat |
in recent OpenLIBM_jll this is in |
bac56a8 to
b4a92b2
Compare
|
Ok, worked around the issue for Windows (but the recipe is getting more and more messy 😁). Any clue where the platform used to download the binaries comes from before I dive into Makefiles? 😛 |
|
Ok, I believe I found it, it should be Yggdrasil/L/libjulia/common.jl Line 157 in b4a92b2 but after manually removing the 14 from darwin14 (it remains to be seen how to do this in a sane way in the builder....), I get stuck at
|
|
All platforms but macOS now work. For reference, the error is |
47d0529 to
52b14cc
Compare
`dsymutil` segfaults when running on `libjulia-internal.1.6.dylib`. We don't have the resources to debug the issue now (although we should look into this because it can happen elsewhere), but at least we can get the build done.
|
Ok, we can't easily debug the dsymutil segmentation fault, as a workaround.... we can skip this step 😬 @vchuravy @staticfloat could you please review this PR, including my last 3-4 commits? They're quite messy... |
| From 30c32040d81ba909242b6e5786772efa94e8120f Mon Sep 17 00:00:00 2001 | ||
| From: Valentin Churavy <v.churavy@gmail.com> | ||
| Date: Wed, 23 Sep 2020 16:48:49 -0400 | ||
| Subject: [PATCH] Allow flips to be built against system UTF8PROC |
There was a problem hiding this comment.
Is this patch already in Julia master, or at least in a PR there? Perhaps it could alao be backported to the release-1.6 branch?
There was a problem hiding this comment.
I'm confused as well: the patch applies cleanly, but the corresponding PR was merged and appears to have been backported to v1.6
There was a problem hiding this comment.
Uh, it looks like this commit was skipped from the backport
|
Seems OK to me and I can build libcxxwrap-julia using this, but in the JLL it doesn't add the When I tried using this test version as a build dependency for libcxxwrap-julia, it would pick up the Julia 1.5 libjulia instead of the newest one, even though I was requesting Julia 1.6. Not sure if this is a problem that only appears when building locally, or also when building here on Yggdrasil. |
How did you build? |
Looking at the latest revision of Artifacts.toml, there is only one target present, that being GNU/Linux x64 (C++11 string abi) |
|
Good point looking at the README, thanks. Yes, you should build for |
|
Correct, I built with only |
|
Ok, well, let's merge this and see how it goes! Thanks everybody! |

No description provided.