Skip to content

Conversation

@fingolfin
Copy link
Member

Should be merged with [skip ci].

It may be that some of the macOS specific things will have to be added back (e.g. I have no idea why it was setting custom LDFLAGS and OBJCFLAGS). My idea here was to remove everything, then add things back as needed, but this time perhaps with a comment or two indicating the reason.

@barch Please let me know uf you have any explanations or additional thoughts on this!

@fingolfin
Copy link
Member Author

Huh, now getting this:

ERROR: LoadError: version 16.0.6 of package LLVM_full_jll is not available. Available versions: 8.0.1+0, 8.0.1+1, 8.0.1+2, 8.0.1+3, 9.0.1+0, 9.0.1+1, 9.0.1+2, 9.0.1+3, 9.0.1+4, 9.0.1+5, 9.0.1+6, 9.0.1+7, 9.0.1+8, 10.0.0+0, 10.0.0+1, 10.0.1+0, 10.0.1+1, 10.0.1+2, 11.0.0-rc5+0, 11.0.0-rc5+1, 11.0.0-rc6+2, 11.0.0+3, 11.0.0+4, 11.0.0+5, 11.0.0+6, 11.0.0+7, 11.0.0+8, 11.0.0+9, 11.0.0+10, 11.0.1+0, 11.0.1+1, 11.0.1+2, 11.0.1+3, 11.0.1+4, 12.0.0+0, 12.0.0+1, 12.0.1+0, 12.0.1+1, 12.0.1+2, 12.0.1+3, 12.0.1+4, 13.0.0+0, 13.0.0+1, 13.0.0+2, 13.0.0+3, 13.0.1+0, 13.0.1+1, 13.0.1+2, 13.0.1+3, 14.0.2+0, 14.0.2+1, 14.0.5+0, 14.0.5+1, 14.0.5+2, 14.0.5+3, 14.0.6+0, 14.0.6+1, 14.0.6+2, 14.0.6+3, 14.0.6+4, 15.0.7+0, 15.0.7+1, 15.0.7+2, 15.0.7+3, 15.0.7+4, 15.0.7+5, 15.0.7+6, 15.0.7+7, 15.0.7+8, 15.0.7+9, 15.0.7+10, 16.0.6+0, 16.0.6+1, 16.0.6+2, 16.0.6+3, 16.0.6+4, 16.0.6+5, 16.0.6+6, 17.0.6+0, 17.0.6+1, 17.0.6+2, 17.0.6+3, 17.0.6+4, 17.0.6+5, 18.1.7+0, 18.1.7+1, 18.1.7+2, 18.1.7+3, 18.1.7+4, 18.1.7+5, 19.1.1+0, 19.1.1+1, 19.1.1+2, 19.1.7+0, 19.1.7+1, 19.1.7+2, 20.1.2+0, 20.1.2+1, 20.1.2+2, 20.1.2+3, 20.1.8+0, 21.1.2+0

Which it didn't show the last it was built. I note that 16.0.6+0 up to 16.0.6+6 are in that list.... I'd not expect this failure, though, the + should not matter for the version selection here:

BuildDependency(PackageSpec(name="LLVM_full_jll", version=qt_llvm_version)),

Now I wonder: perhaps in between we did the update to Julia 1.12 ?

@giordano ?

@giordano
Copy link
Member

giordano commented Dec 6, 2025

Packagespec needs a string instead of a version number

@fingolfin fingolfin marked this pull request as draft December 6, 2025 22:10
@barche
Copy link
Contributor

barche commented Dec 7, 2025

Sorry, I don't really remember the specifics, it took a lot of tweaking to get this to compile on all platforms. I'd have to do the same as you are doing now, remove things and add back as needed.

@fingolfin
Copy link
Member Author

@barche no worries. It compiles on all platforms (well, it did, last I tried), except for macOS -- no surprise since the main change here is to how it uses the macOS SDK.

But anyway, it seems I now got it to build on ARM, and the x86 failure was "just" a timeout.

@fingolfin
Copy link
Member Author

@barche this should be ready know (well, let's see if the rest of the CI passes, but the macOS ones do).

But there is no need to rebuild the JLLs, so it would be fine to merge this with [skip ci]. I mainly wanted to have this in place so that it is safe to update some of the other Qt6 recipes.

@fingolfin fingolfin marked this pull request as ready for review December 7, 2025 23:18
@fingolfin fingolfin enabled auto-merge (squash) December 7, 2025 23:18
@fingolfin fingolfin merged commit a34ee59 into master Dec 7, 2025
3 of 4 checks passed
@fingolfin fingolfin deleted the mh/Qt6Base branch December 7, 2025 23:25
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.

4 participants