-
Notifications
You must be signed in to change notification settings - Fork 35
Remove UMF_DISABLE_HWLOC option #1228
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
base: main
Are you sure you want to change the base?
Conversation
5229bc6
to
29de648
Compare
29de648
to
732af42
Compare
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.
in general lgtm, but pls rebase
732af42
to
cf5ba95
Compare
cf5ba95
to
939160c
Compare
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.
I support this change with my whole heart.
@PatKamin if you remove the "required" job, we will need to choose a new one - please ask @lukaszstolarczuk to do that |
I'll change this to draft for now and merge when compiler's environment is ready (without it we couldn't do any updates to the compiler repo) |
Description
After all third-party usage of the
UMF_DISABLE_HWLOC
is removed, the flag itself can be removed. It was a temporary workaround for UMF usage without the hwloc installed in the system, from the beginning planned to be removed prior to the v1.0 first stable API release.Currently, UMF either uses libhwloc-dev installed in the system or fetches it from sources.
Fixes: #1047
Checklist