Closed paulmenzel closed 3 years ago
Interesting ... what distro / compiler are you using?
We have our own distribution based loosely on Linux From Scratch (MarIuX64).
I tested GCC 7.5 and 10.1.
asking because we are testing quite a few compilers in our github worklflows. Still not covering everything, obviously.
OK - it's because you don't have LIBDM_API_DEFERRED set. You seem to be using a very old version of libdevmapper.
Indeed, /usr/include/libdevmapper.h
is from lvm2-2.02.100-0.x86_64.
I'll create a patch to avoid this error. Be advised though that multipath testing has almost exclusively been done with newer versions of libdevmapper for several years. Maybe it's time to update :-)
Thank you for your analysis and help.
Indeed, updating is a good idea. I only need kpartx
and will run it manually.
The easiest workaround in cases like this is to just using somewhat less strict warning flags. You could simply add -Wno-unused in the WARNFLAGS
(Makefile.inc
), for example. If you examine the warnings, you'll see that they are non-fatal, so loosening the flags a bit is justified for that specific use case. We are trying to use strict warn flags to catch errors, but making that work for any distro (or like in your case, with any old library version) is almost impossible, and thus we focus on more modern distros. Our CI goes back to Debian "Jessie", but we can't cover everything.
Please test with 20c2697 (mwilck/tip).
Perfect. Tested successfully.
(In the commit message, you might want to prefix the issue URL with Resolves:. (But maybe you waited for my test.))
Thank you very much.
Commit msg updated.
I took the liberty to also add a Tested-by: Paul Menzel tag.
Yes, thank you. I received your patch message.
Indeed,
/usr/include/libdevmapper.h
is from _lvm2-2.02.100-0.x8664.
It's nearly 8 years old !!!
You are going to find a lot of bugs fun.
Well, at least code wise, we still support these old versions. We just haven't tested current multipath-tools on them for a long time. Also, there are enterprise distros released in 2014 which still have some years of support left. So, I'm generally glad about bug reports like this.
Build version 0.8.6 fails with the error below: