Skip to content

Tentative upgrade to ASL_jll v0.1.5 - #851

Open
cvanaret wants to merge 4 commits into
mainfrom
upgrade_asl
Open

Tentative upgrade to ASL_jll v0.1.5#851
cvanaret wants to merge 4 commits into
mainfrom
upgrade_asl

Conversation

@cvanaret

@cvanaret cvanaret commented Aug 15, 2026

Copy link
Copy Markdown
Owner

Tentative upgrade to latest ASL. I'm suspecting that ASL_jll.jl is not up to date, let's give it a try.

What I'm after:

  • Sphese and Hvcompe: Hessian evaluation and Hessian-vector product with an extra nerror parameter
  • (minor) const correctness of the ASL signatures

AFAICT there were no breaking changes in the API, only additional functions.

@cvanaret cvanaret self-assigned this Aug 15, 2026
@cvanaret cvanaret added the AMPL label Aug 15, 2026
@cvanaret

Copy link
Copy Markdown
Owner Author

That's what I thought. The latest changes to https://www.netlib.org/ampl/solvers/ are not in ASL_jll.jl.
@amontoison do I simply need to change the tgz hash and bump the version in https://github.com/JuliaPackaging/Yggdrasil/blob/master/A/ASL/build_tarballs.jl?

@amontoison

amontoison commented Aug 16, 2026

Copy link
Copy Markdown
Collaborator

@cvanaret It is a little bit more complex for ASL_jll.jl because it is used by many artifacts and I don't want to break anything.
What I propose is to update the General registry with a PR to add a compat entry on ASL_jll.jl for JLL compiled without it.
The concerned JLL are:

  • SHOT
  • Ipopt
  • IpoptMKL
  • Bonmin
  • Cbc
  • Couenne

The only JLL with a compat entry on ASL_jll.jl is... Uno!

Once it is done, we can update all the related build_tarballs.jl files to add the compat entry but not trigger a cross-compilation (no CI).

Once it is done, we can use the GitHub repository of ASL (like you did for ASL2) and specify a meaningful version (XXXX.YY.ZZ).
It will be great because we don't know what version was used for ASL_jll, AMPL recycles the same link for new solvers.tgz...

I broke a bunch of packages with the upgrade SCOTCH 6 --> SCOTCH 7 in the past and I don't want to reproduce it with the upgrade of ASL:

What do you think Oscar?
cc @odow

@odow

odow commented Aug 16, 2026

Copy link
Copy Markdown
Contributor

I've never wanted to touch ASL_jll.jl for this reason...

AFAICT there were no breaking changes in the API, only additional functions.

Are you reeeeeeally sure?

@cvanaret

Copy link
Copy Markdown
Owner Author

Are you reeeeeeally sure?

Not a 100% :)

I think the only way out is to have Uno depend on ASL2(_jll), which can be kept in sync.

@amontoison

amontoison commented Aug 17, 2026

Copy link
Copy Markdown
Collaborator

@cvanaret Can you provide a draft PR on Yggdrasil to update ASL_jll.jl such that we can cross-compile it on a fork like we do for UnoUtils_jll.jl ?

It will give us a chance to test it and check if it breaks a library.
If we have all the tests of AmplNLWriter.jl and AmplNLReader.jl working on linux / mac / windows, maybe we can upgrade it.

@cvanaret cvanaret changed the title Tentative upgrade to latest ASL Tentative upgrade to ASL_jll v0.1.5 Sep 5, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants