Skip to content

Make LLVM 19.x available #155

Description

@hellium6

I needed LLVM 19.x to try Zig 0.14.0 dev so I had to edit it myself (my version available here https://github.com/hellium6/zig-master-netbsd). I kept them in separate directories ("llvm19" vs "llvm") for my use case.

The changes were not that difficult. It would be great to see it in repos.

If it causes trouble with other packages, maybe a separate "llvm19" package would be appropriate?

Activity

  1. bsiegert commented on Feb 7, 2025

    @bsiegert
    Contributor

    You can use wip/llvm from pkgsrc-wip. It is at version 19.1. I think the update in pkgsrc itself is in progress, but there are some issues about compatibility with Rust, Chromium, etc.

  2. hellium6 commented on Feb 7, 2025

    @hellium6
    Author

    Thanks for the quick response

    It seems I did all this work for nothing. But anyways, learned things along the way.

    If SEO for NetBSD content was better I wouldn't have had to do it. Searching for "llvm 19 on NetBSD" brought up nothing.

  3. hellium6 commented on Feb 21, 2025

    @hellium6
    Author

    ...but there are some issues about compatibility with Rust, Chromium, etc.

    While looking into how other operating systems package LLVM I discovered that FreeBSD has seperate packages for LLVM- devel/llvm18 and devel/llvm19 - for example.

    I was able to make the packages in my repo to install in a different prefix than the official ones. I was able to install both LLVM 18 and 19 (for Zig stable and Zig master) on the same system. So it is not impossible to do.

    With Zig 0.14 releasing on March 3rd, is there any plan to do something similar on NetBSD? Maybe a lang/llvm18 can be kept for problem packages and lang/llvm19 can be made available for others?

  4. added a commit that references this issue on Aug 31, 2025
  5. added a commit that references this issue on Nov 1, 2025
  6. added a commit that references this issue on Dec 4, 2025
  7. added a commit that references this issue on Mar 19, 2026
  8. added a commit that references this issue on May 2, 2026
  9. 43 remaining items

  10. added a commit that references this issue on Jun 24, 2026
  11. added a commit that references this issue on Jul 30, 2026
  12. added a commit that references this issue on Aug 26, 2026
  13. added a commit that references this issue on Sep 12, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions