Skip to content

Juliaup: Update from 1.18.9 to 1.19.9#13420

Open
DilumAluthge wants to merge 2 commits intomasterfrom
dpa/juliaup-1.19.9
Open

Juliaup: Update from 1.18.9 to 1.19.9#13420
DilumAluthge wants to merge 2 commits intomasterfrom
dpa/juliaup-1.19.9

Conversation

@DilumAluthge
Copy link
Copy Markdown
Member

No description provided.

@DilumAluthge DilumAluthge requested a review from giordano March 30, 2026 03:12
@DilumAluthge
Copy link
Copy Markdown
Member Author

cc: @ViralBShah @IanButterworth @davidanthoff

@DilumAluthge
Copy link
Copy Markdown
Member Author

[03:16:28] error: rustc 1.87.0 is not supported by the following packages:
[03:16:28]   human-panic@2.0.6 requires rustc 1.88
[03:16:28]   sysinfo@0.37.2 requires rustc 1.88

@DilumAluthge
Copy link
Copy Markdown
Member Author

@giordano Would it be possible for me to get Rust 1.88?

@giordano
Copy link
Copy Markdown
Member

Not forcing 1.87

compilers=[:rust, :c], julia_compat="1.6", preferred_rust_version=v"1.87",
when latest version available is 1.94 would do it.

@DilumAluthge
Copy link
Copy Markdown
Member Author

🤦

@DilumAluthge
Copy link
Copy Markdown
Member Author

DilumAluthge commented Mar 30, 2026

From build-j-slash-juliaup-aarch64-linux-musl:

[04:04:27] cargo:warning=/opt/x86_64-linux-musl/registry/src/index.crates.io-1949cf8c6b5b557f/aws-lc-sys-0.36.0/aws-lc/generated-src/linux-aarch64/crypto/fipsmodule/aesv8-gcm-armv8-unroll8.S:8338: Error: selected processor does not support `pmull v17.1q,v18.1d,v16.1d'

But when I look at the GitHub release (https://github.com/JuliaLang/juliaup/releases/tag/v1.19.9), I see a Juliaup build for juliaup-1.19.9-aarch64-unknown-linux-musl-portable.tar.gz, so CI on that repo was able to build.

@DilumAluthge
Copy link
Copy Markdown
Member Author

I can exclude the platform (I really only need the most popular ones), but it'd be nice to fix.

@DilumAluthge
Copy link
Copy Markdown
Member Author

To give more details, my use case is that I want to use juliaup_jll in AutoMerge.jl.

On the General registry, we run AutoMerge on Linux x86_64, so that's the most important platform to support.

For people developing and testing AutoMerge.jl locally, I'd like to support the most popular platforms (Linux x86_64, Windows x86_64, macOS x86_64, and macOS aarch64), to make life easier for people developing AutoMerge.jl.

For folks running AutoMerge on their custom registries, I suppose they could be using Linux aarch64 on a self-hosted runner. So it'd be nice to not break them, but also worst case we can say that AutoMerge only supports the aforementioned platforms.

@DilumAluthge
Copy link
Copy Markdown
Member Author

Also, to clarify, I only want to use juliaup_jll in AutoMerge.jl (not RegistryCI.jl).

@giordano
Copy link
Copy Markdown
Member

Using a newer version of gcc (and hence binutils) should fix that, but I don't know what's the first version of as which supports that.

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

Successfully merging this pull request may close these issues.

2 participants