julia @0.6.2_3: llvm-4.0 has been replaced by llvm-8.0; please install that instead

[ryandesign (Ryan Carsten Schmidt)]

​julia does not build because it depends on an llvm version which was deleted from MacPorts:

--->  Configuring llvm-4.0
DEBUG: Preferred compilers: clang macports-clang-5.0 macports-clang-4.0
DEBUG: Using compiler 'Xcode Clang'
DEBUG: Executing proc-pre-org.macports.configure-configure-0
Error: llvm-4.0 has been replaced by llvm-8.0; please install that instead.
Error: Failed to configure llvm-4.0: obsolete port

I don't know if there is a good reason why julia uses this specific version of llvm; maybe using a newer version would work. If not, maybe updating julia to the latest version would add compatibility with newer llvm versions.

[ryandesign (Ryan Carsten Schmidt)]

Replying to ryandesign:

maybe updating julia to the latest version would add compatibility with newer llvm versions.

See #56956 for a not-yet-successful attempt in updating the port, and the presumably llvm-related errors that were encountered in the attempt.

[p-bro]

Does that mean that for the time being I have to live with a permanently broken macports installation, unless I uninstall julia?

[ryandesign (Ryan Carsten Schmidt)]

It means that nobody can install julia at the moment, and it means that if you upgraded llvm-4.0 to its replacement llvm-8.0, then any existing julia installation you may have had will be declared broken by sudo port rev-upgrade and probably will not work.

Until somebody fixes this by updating julia to use a newer llvm, you could unbreak your julia by reactivating the deactivated llvm-4.0 @4.0.1_6 port. See wiki:howto/InstallingOlderPort. If you do this, remember to deactivate or uninstall llvm-4.0 after julia gets updated.

[kencu (Ken)]

Ths current julia appears to use llvm-6.0 <​https://github.com/JuliaLang/julia/blob/master/doc/build/build.md#required-build-tools-and-external-libraries> so that would be the place to spend the effort, I guess.

[ryandesign (Ryan Carsten Schmidt)]

julia was updated to 1.1.1 and no longer uses llvm, so it should no longer be possible to encounter the problem reported in this ticket.