From: cat@catcream.org <cat@catcream.org>
To: lvm-devel@redhat.com
Subject: Fix lvm2 for musl libc
Date: Tue, 21 Jun 2022 21:21:26 +0200 (CEST) [thread overview]
Message-ID: <N56haDY--3-2@catcream.org> (raw)
Hi! These patches fix lvm2 for musl.
freopen is used in place of the assignment operator since the standard streams are const in musl. https://www.gnu.org/software/libc/manual/html_node/Standard-Streams.html (it says on this page that the standard streams may not be modifiable on other systems).
The mallinfo patch is just copied from Alpine Linux and it makes _allocate_memory not do anything if glibc isn't used. I don't know if that is fine, and if not I'd probably need some help properly making the function posix compliant, thanks.
--
Sent with Tutanota, enjoy secure & ad-free emails.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: lvm2-2.03.14-freopen_n2.patch
Type: text/x-patch
Size: 575 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/lvm-devel/attachments/20220621/3594a4a7/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: lvm2-2.03.14-r1-fopen-to-freopen.patch
Type: text/x-patch
Size: 1306 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/lvm-devel/attachments/20220621/3594a4a7/attachment-0001.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: lvm2-2.03.14-r1-mallinfo.patch
Type: text/x-patch
Size: 665 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/lvm-devel/attachments/20220621/3594a4a7/attachment-0002.bin>
next reply other threads:[~2022-06-21 19:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-21 19:21 cat [this message]
2022-06-22 9:24 ` Fix lvm2 for musl libc 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=N56haDY--3-2@catcream.org \
--to=cat@catcream.org \
--cc=lvm-devel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.