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

configure.ac: use pkg-config to find numa #188

Merged
merged 1 commit into from
Aug 2, 2021
Merged

configure.ac: use pkg-config to find numa #188

merged 1 commit into from
Aug 2, 2021

Conversation

ffontaine
Copy link
Contributor

Use pkg-config to find numa and fallback to current mechanism. Thanks to pkg-config, numa dependencies such as -latomic will be retrieved.

Signed-off-by: Fabrice Fontaine fontaine.fabrice@gmail.com

@nhorman
Copy link
Member

nhorman commented Aug 1, 2021

I wouldn't bother with the fallback mechanism. If libnuma has a pkg-config file, let's just use it.

Also there is no reason. To do the AC_SUBST calls, PKG_CHECK_MODULES will handle that (see the glib2 use)

@ffontaine
Copy link
Contributor Author

ffontaine commented Aug 2, 2021

numa.pc is only available since version 2.0.12 and numactl/numactl@53ac79b so I think it is good to keep a fallback but I'll let you decide.

I'll remove the AC_SUBST calls.

Use pkg-config to find numa and fallback to current mechanism.
Thanks to pkg-config, numa dependencies such as -latomic will be
retrieved.

Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
@nhorman
Copy link
Member

nhorman commented Aug 2, 2021

Thank you! 2 years is my general rule for not worrying about a fallback mechanism. If a system can't update their libraries for two years, they can figure out compatibility.

@nhorman nhorman merged commit faae34d into Irqbalance:master Aug 2, 2021
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

Successfully merging this pull request may close these issues.

None yet

2 participants