From: Zdenek Kabelac <zdenek.kabelac@gmail.com>
To: "LVM general discussion and development" <linux-lvm@redhat.com>,
程智星 <zhixing@nj.iscas.ac.cn>
Subject: Re: [linux-lvm] Problems encountered in compiling lvm packages using the musl Toolchain
Date: Wed, 9 Aug 2023 14:27:51 +0200 [thread overview]
Message-ID: <accecfd1-d329-9306-94b0-cef460c9d1e7@gmail.com> (raw)
In-Reply-To: <c63bc8d.3c07c.1898fef021b.Coremail.zhixing@nj.iscas.ac.cn>
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/
prev parent reply other threads:[~2023-08-09 12:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
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 message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=accecfd1-d329-9306-94b0-cef460c9d1e7@gmail.com \
--to=zdenek.kabelac@gmail.com \
--cc=linux-lvm@redhat.com \
--cc=zhixing@nj.iscas.ac.cn \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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 read-only IMAP folder(s) and NNTP newsgroup(s).