Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make LLVM 19.x available #155

Open
hellium6 opened this issue Feb 7, 2025 · 3 comments
Open

Make LLVM 19.x available #155

hellium6 opened this issue Feb 7, 2025 · 3 comments

Comments

@hellium6
Copy link

hellium6 commented Feb 7, 2025

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?

@bsiegert
Copy link
Contributor

bsiegert commented Feb 7, 2025

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.

@hellium6
Copy link
Author

hellium6 commented Feb 7, 2025

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.

netbsd-srcmastr pushed a commit that referenced this issue Feb 18, 2025
v2.0.0 (2025-02-09)

Breaking

    refactor!: rename python package serializable -> py_serializable (#155)

    The python package was renamed from serializable to py_serializable.
    Therefore, you need to adjust your imports.

    The following shows a quick way to adjust imports in the most efficient way.
    OLD imports

    import serializable
    from serializable import ViewType, XmlArraySerializationType, XmlStringSerializationType
    from serializable.helpers import BaseHelper, Iso8601Date

ADJUSTED imports

import py_serializable as serializable
from py_serializable import ViewType, XmlArraySerializationType, XmlStringSerializationType
from py_serializable.helpers import BaseHelper, Iso8601Date

    see migration path: https://py-serializable.readthedocs.io/en/refactor-rename-installable-py_serializable/migration.html

Unknown

    Delete duplicate CODEOWNERS (#156)

    we have a codeowners file in root already (b64cdde)

What's Changed

    chore(deps-dev): update mypy requirement from 1.11.2 to 1.12.0 by @dependabot in #143
    chore(deps-dev): update mypy requirement from 1.12.0 to 1.13.0 by @dependabot in #145
    chore(deps-dev): update flake8-bugbear requirement from 24.8.19 to 24.10.31 by @dependabot in #146
    chore(deps-dev): update flake8-bugbear requirement from 24.10.31 to 24.12.12 by @dependabot in #150
    chore(deps-dev): update mypy requirement from 1.13.0 to 1.14.1 by @dependabot in #154
    Delete duplicate CODEOWNERS by @jkowalleck in #156
    chore(docs): chanelog contains only relevant by @jkowalleck in #157
    chore(docs): recreate changelog by @jkowalleck in #158
    chore(deps): bump actions/upload-artifact from 3 to 4 by @dependabot in #37
    refactor!: rename python package serializable -> py_serializable by @jkowalleck in #155
    chore(deps): update sphinx requirement from <8,>=7.2.6 to >=7.2.6,<9 by @dependabot in #127
@hellium6
Copy link
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?

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

No branches or pull requests

2 participants