-
Notifications
You must be signed in to change notification settings - Fork 604
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
bazel: remove numactl #25041
bazel: remove numactl #25041
Conversation
691a390
to
982e68b
Compare
i'm not saying we should do this, but from what I can tell seastar's libnuma dependency is a single call to looking at this: https://github.com/lrita/numa/blob/29f88905963797c57362861a2dd8adb14a6f152a/numa_linux.go#L161 i do wonder if freeing ourselves from the libnuma dependency would be as simple as writing our own version of this
|
@@ -6,7 +6,8 @@ edition = "2021" | |||
publish = false | |||
|
|||
[lib] | |||
path = "/dev/null" | |||
# Use a fake path here, but rules_rust requires something. | |||
path = "./dev/null" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nice. i had gone with fake.rs
ooh maybe I will send a patch to seastar and see what drama unfolds... |
Updated to remove numactl using the pending upstream patch in seastar |
06d6976
to
def94ad
Compare
I snuck in a few clang-19 fixes into this PR. I have a lot of the tree building with a couple of small seastar patches. |
CI test resultstest results on build#61934
test results on build#61942
test results on build#62027
|
@@ -47,6 +47,7 @@ bazel_dep(name = "yaml-cpp", version = "0.8.0") | |||
bazel_dep(name = "zlib", version = "1.3.1.bcr.3") | |||
bazel_dep(name = "zstd", version = "1.5.6") | |||
bazel_dep(name = "patchelf", version = "0.18.0") | |||
bazel_dep(name = "bzip2", version = "1.0.8.bcr.2") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
bazel: upgrade bzip2
but this commit is adding bzip2, right? was bzip2 being depended on indirectly, and this new bazel_dep line then causes all bzip2 instances to use the bcr.2 version?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah exactly, you can see this in the lock file
This breaks in bazel 8, so fix it now
required to work with Bazel 8
These have landed upstream
To prevent 500 errors from sourceware.org
Newer libcpp uses a wrapped iterator type for string_view so we aren't comparing the right types between string_view and ss::sstring
In newer libcpp iterators are not pointers, fix the usage here.
To address a clang-19 warning
Force push: fix conflicts in |
@rockwotj is there a specific reason we are applying these changes as patches in our redpanda-side bazel build rather than checking them into our seastar fork? Is it because if we put them into our fork it won't build (cmake style) any more? |
No we should be applying them to our seastar fork, especially since this is upstreamed and not in the cmake build once we rebase. |
Very nice. I will cherry pick this into our fork. |
Thanks, it's on my list of things to get too 😅 |
Incorporate libnuma into the Bazel build. We force dynamic linking because it's LGPL. The dynamic linking forcing is really annoying, but honestly less annoying than the new way of doing things with
cc_shared_library
. However I ran into issues using thecc_shared_library
approach, so I just fallback to using the "old school" stable ways of making shared libraries.Backports Required
Release Notes