All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Simon Rowe <simon.rowe@nutanix.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/lvm2: enable package with musl
Date: Sun, 19 Mar 2023 17:25:54 +0100	[thread overview]
Message-ID: <20230319172554.0d5ea60c@windsurf> (raw)
In-Reply-To: <20230316113615.138847-1-simon.rowe@nutanix.com>

Hello Simon,

On Thu, 16 Mar 2023 11:36:15 +0000
Simon Rowe <simon.rowe@nutanix.com> wrote:

> LVM uses some glibc-specific functions to try and control locking
> memory in RAM. As a result the package is currently disabled when
> using musl.
> 
> Apply patches taken from gentoo:
> 
>     https://github.com/gentoo/gentoo/pull/25883
>     https://github.com/gentoo/gentoo/pull/26024
> 
> and drop the prohibition on musl in Config.in.
> 
> Signed-off-by: Simon Rowe <simon.rowe@nutanix.com>

Thanks Simon for those patches! Could you rework the 4 patches so that
they are generated with git format-patch and have your Signed-off-by? I
recommend that you take the upstream Git repo of lvm2, checkout the tag
corresponding to version 2.03.14, apply the 4 Gentoo patches, each time
turning the changes into a proper commit.

Another thing to look at is that the multipath-tools package is
selecting BR2_PACKAGE_LVM2_STANDARD_INSTALL, so you need to check
whether the depends on !BR2_TOOLCHAIN_USES_MUSL used in
BR2_PACKAGE_MULTIPATH_TOOLS is still needed? Perhaps thanks to your
work on lvm2 it is now possible to build/use multipath-tools with musl.

Another question is the upstream status of the Gentoo patches? Have
they been submitted for inclusion by the upstream lvm2 project?

Thanks!

Thomas
-- 
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2023-03-19 16:26 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-16 11:36 [Buildroot] [PATCH 1/1] package/lvm2: enable package with musl Simon Rowe
2023-03-19 16:25 ` Thomas Petazzoni via buildroot [this message]
2023-03-21 13:39   ` Simon Rowe
2023-03-21 13:54     ` Thomas Petazzoni via buildroot
2023-03-23 12:36       ` Simon Rowe
2023-03-23 13:15         ` Thomas Petazzoni via buildroot
2023-03-23 14:13 ` [Buildroot] [PATCH v2 1/2] " Simon Rowe
2023-03-23 14:13   ` [Buildroot] [PATCH v2 2/2] package/multipath-tools: enable " Simon Rowe
2023-03-26 21:11     ` Thomas Petazzoni via buildroot
2023-03-26 21:10   ` [Buildroot] [PATCH v2 1/2] package/lvm2: enable package " Thomas Petazzoni via buildroot

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=20230319172554.0d5ea60c@windsurf \
    --to=buildroot@buildroot.org \
    --cc=simon.rowe@nutanix.com \
    --cc=thomas.petazzoni@bootlin.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.