* [linux-lvm] Problems encountered in compiling lvm packages using the musl Toolchain
@ 2023-07-26 2:02 程智星
2023-08-09 12:27 ` Zdenek Kabelac
0 siblings, 1 reply; 2+ messages in thread
From: 程智星 @ 2023-07-26 2:02 UTC (permalink / raw)
To: linux-lvm
[-- Attachment #1.1: Type: text/plain, Size: 829 bytes --]
hi,friend:
I encountered the following problems when compiling lvm packages using the musl Toolchain:
Question 1 :
| vgimportdevices.c: In function 'vgimportdevices':
| vgimportdevices.c:148:30: error: 'LOCK_EX' undeclared (first use in this function); did you mean 'LOCKED'?
| 148 | if (!lock_devices_file(cmd, LOCK_EX)) {
| | ^~~~~~~
| | LOCKED
| vgimportdevices.c:148:30: note: each undeclared identifier is reported only once for each function it appears in
About LOCK_EX definition is in file.h, I can compile this package by adding this Header file in vgimportdevices.c:
#include <sys/file.h>
Could you add this Header file to our source code to fix this problem or do you have a better solution?
Looking forward to your reply!
[-- Attachment #1.2: Type: text/html, Size: 1642 bytes --]
[-- Attachment #2: Type: text/plain, Size: 202 bytes --]
_______________________________________________
linux-lvm mailing list
linux-lvm@redhat.com
https://listman.redhat.com/mailman/listinfo/linux-lvm
read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [linux-lvm] Problems encountered in compiling lvm packages using the musl Toolchain
2023-07-26 2:02 [linux-lvm] Problems encountered in compiling lvm packages using the musl Toolchain 程智星
@ 2023-08-09 12:27 ` Zdenek Kabelac
0 siblings, 0 replies; 2+ messages in thread
From: Zdenek Kabelac @ 2023-08-09 12:27 UTC (permalink / raw)
To: LVM general discussion and development, 程智星
Dne 26. 07. 23 v 4:02 程智星 napsal(a):
> hi,friend:
>
> I encountered the following problems when compiling lvm packages using the
> musl Toolchain:
>
> Question 1 :
>
> | vgimportdevices.c: In function 'vgimportdevices':
> | vgimportdevices.c:148:30: error: 'LOCK_EX' undeclared (first use in this
> function); did you mean 'LOCKED'?
> | 148 | if (!lock_devices_file(cmd, LOCK_EX)) {
> | | ^~~~~~~
> | | LOCKED
> | vgimportdevices.c:148:30: note: each undeclared identifier is reported only
> once for each function it appears in
>
> About LOCK_EX definition is in file.h, I can compile this package by adding
> this Header file in vgimportdevices.c:
>
> #include <sys/file.h>
>
> Could you add this Header file to our source code to fix this problem or do
> you have a better solution?
>
>
> Looking forward to your reply!
>
Hi
Commit a1a1439215f56335a06ae5ac6ca73b5e0d734760 has been added upstream Feb 7.
So please make sure you are compiling latest upstream.
Note: recently the git HEAD has been moved to https://gitlab.com/lvmteam/lvm2
although sourceware git mirror should also work.
Regards
Zdenek
_______________________________________________
linux-lvm mailing list
linux-lvm@redhat.com
https://listman.redhat.com/mailman/listinfo/linux-lvm
read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2023-08-09 12:53 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2023-07-26 2:02 [linux-lvm] Problems encountered in compiling lvm packages using the musl Toolchain 程智星
2023-08-09 12:27 ` Zdenek Kabelac
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).