unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Josselin Poiret <dev@jpoiret.xyz>
Cc: 68656@debbugs.gnu.org
Subject: [bug#68656] [PATCH core-updates 0/7] Cryptsetup woes
Date: Wed, 24 Jan 2024 11:42:06 -0500	[thread overview]
Message-ID: <87wmrywun5.fsf@gmail.com> (raw)
In-Reply-To: <cover.1705762361.git.dev@jpoiret.xyz> (Josselin Poiret's message of "Mon, 22 Jan 2024 14:33:14 +0100")

Hi Josselin,

Josselin Poiret <dev@jpoiret.xyz> writes:

> Hi everyone,
>
> I'm working on core-updates, trying to build gnome and the desktop
> configuration example.  I've already pushed some fixes, but cryptsetup and
> lvm2 are proving to be quite annoying: for the same reason as the recent mpv
> patches [1], the Require.private fields of pkg-config files are actually used
> even when dynamic linking [2].

Ooof.  I've read this whole thread, and if I got something right, our
best options would be:

1. try using pkgconf instead of pkg-config, which supports
Requires.internal as a correct way to define Requires.private for truly
private libraries, and may have a different handling (more correct?) of
the Requires.private field.

2. Specify the -Ddefault_library=shared in the default configure-flags
of Meson; when done that way, Meson doesn't add the libs to
Requires.private in its generated .pc files.  That obviously means
building static libraries is not supported, but that's not a concern too
great for Guix, I would think.

Thoughts?

-- 
Thanks,
Maxim




      parent reply	other threads:[~2024-01-24 16:43 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-22 13:33 [bug#68656] [PATCH core-updates 0/7] Cryptsetup woes Josselin Poiret via Guix-patches via
2024-01-22 13:36 ` [bug#68656] [PATCH core-updates 1/7] gnu: cryptsetup: Update to 2.6.1 Josselin Poiret via Guix-patches via
2024-01-22 13:36 ` [bug#68656] [PATCH core-updates 2/7] gnu: Add libdevmapper-propagated-inputs Josselin Poiret via Guix-patches via
2024-01-22 13:36 ` [bug#68656] [PATCH core-updates 3/7] gnu: Add libcryptsetup-propagated-inputs Josselin Poiret via Guix-patches via
2024-01-22 13:36 ` [bug#68656] [PATCH core-updates 4/7] gnu: volume-key: Add required transitive dependencies Josselin Poiret via Guix-patches via
2024-01-22 13:36 ` [bug#68656] [PATCH core-updates 5/7] gnu: libblockdev: Add libcryptsetup propagated inputs Josselin Poiret via Guix-patches via
2024-01-22 13:36 ` [bug#68656] [PATCH core-updates 6/7] gnu: lvm2-static: Properly handle eudev dependency in pkg-config Josselin Poiret via Guix-patches via
2024-01-22 13:36 ` [bug#68656] [PATCH core-updates 7/7] gnu: cryptsetup-static: Fix static build Josselin Poiret via Guix-patches via
2024-01-24 16:42 ` Maxim Cournoyer [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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87wmrywun5.fsf@gmail.com \
    --to=maxim.cournoyer@gmail.com \
    --cc=68656@debbugs.gnu.org \
    --cc=dev@jpoiret.xyz \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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).