-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
libudev: add a non-system recipe #26162
base: master
Are you sure you want to change the base?
Conversation
@valgur (in continuation of other thread on cross compiling libudev from x86_64 to x86_64). If you can help us with quick look please. May be by cross building for x86.
Command line:
|
@vithalsm Should be fixed now. Give it another try. |
@valgur Yes, its fixed and could build libudev successfully. Thanks again. |
Finally, could build 'dpdk' with additional changes as below -
|
@vithalsm i think the If you want to keep using dpdk with rdma-core, I suggest adding
to your profile to override the version everywhere. |
@valgur thank you for this suggestion, was looking for exactly like this. It helped. |
The static version tends to cause linking errors for the consuming packages while the shared version works fine.
b33e765
to
fc965d1
Compare
Summary
Changes to recipe: libudev/255.15
Motivation
libudev/system
is used in several recipes on CCI, but like othersystem
packages, it is not usable in a cross-compilation context.Details
The
libudev
library is a part of systemd, but neitherlibsystemd
orlibudev
depend on each other. I considered making it a component oflibsystemd
, but keeping them independent of each other seemed preferable, since they are not really used simultaneously in any recipes and it allows for a lighterlibudev
dependency. The only downside is slight duplication in the recipe.The recipe cross-compiles successfully with
aarch64-linux-gnu-gcc-14
.