You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is not my area of knowledge and I may be asking a dumb question but should (be expected) that liburing built with api headers 6.13 be incompatible with 6.6
We are loosely compatible with arch but arch when rebuilding the tool-chain use their latest stable kernel version and we stick to a relatively recent lts. Recently bumped to 6.13 from 6.10
We weren't building our own liburing before, now we do, and never had an issue in building btrfs mpd samba .. we now got a fatal error and it came from liburing function which lead us to building it and problem was gone.
IOW the incompatibility was never an issue in the past now it is, and possibly relates to kernel api version
I am just wondering whether this incompatibility is expected or not-expected, the library being sensitive to version. It may be possible that running wise it may not be an issue but building.
The text was updated successfully, but these errors were encountered:
This is not my area of knowledge and I may be asking a dumb question but should (be expected) that liburing built with api headers 6.13 be incompatible with 6.6
We are loosely compatible with arch but arch when rebuilding the tool-chain use their latest stable kernel version and we stick to a relatively recent lts. Recently bumped to 6.13 from 6.10
We weren't building our own liburing before, now we do, and never had an issue in building btrfs mpd samba .. we now got a fatal error and it came from liburing function which lead us to building it and problem was gone.
IOW the incompatibility was never an issue in the past now it is, and possibly relates to kernel api version
I am just wondering whether this incompatibility is expected or not-expected, the library being sensitive to version. It may be possible that running wise it may not be an issue but building.
The text was updated successfully, but these errors were encountered: