linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: 程智星 <zhixing@nj.iscas.ac.cn>
To: linux-lvm@redhat.com
Subject: [linux-lvm] Problems encountered in compiling lvm packages using the musl Toolchain
Date: Wed, 26 Jul 2023 10:02:32 +0800 (GMT+08:00)	[thread overview]
Message-ID: <c63bc8d.3c07c.1898fef021b.Coremail.zhixing@nj.iscas.ac.cn> (raw)


[-- 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/

             reply	other threads:[~2023-07-26  6:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-26  2:02 程智星 [this message]
2023-08-09 12:27 ` [linux-lvm] Problems encountered in compiling lvm packages using the musl Toolchain Zdenek Kabelac

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=c63bc8d.3c07c.1898fef021b.Coremail.zhixing@nj.iscas.ac.cn \
    --to=zhixing@nj.iscas.ac.cn \
    --cc=linux-lvm@redhat.com \
    /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 NNTP newsgroup(s).