public inbox for bzip2-devel@sourceware.org
 help / color / mirror / Atom feed
From: "sourceware at ryandesign dot com" <sourceware-bugzilla@sourceware.org>
To: bzip2-devel@sourceware.org
Subject: [Bug bzip2/31660] New: Add bzip2.pc pkg-config file
Date: Fri, 19 Apr 2024 20:29:49 +0000	[thread overview]
Message-ID: <bug-31660-11876@http.sourceware.org/bugzilla/> (raw)

https://sourceware.org/bugzilla/show_bug.cgi?id=31660

            Bug ID: 31660
           Summary: Add bzip2.pc pkg-config file
           Product: bzip2
           Version: unspecified
            Status: UNCONFIRMED
          Severity: enhancement
          Priority: P2
         Component: bzip2
          Assignee: nobody at sourceware dot org
          Reporter: sourceware at ryandesign dot com
                CC: bzip2-devel at sourceware dot org
  Target Milestone: ---

Please add a pkg-config bzip2.pc file.

Code to do so was committed in 2019:

https://gitlab.com/bzip2/bzip2/-/commit/70ec984159c8263fdd4aac7c4670977aff0fe5b3

yet there does not appear to be a release of bzip2 containing
this improvement.

Separately a patch to do this was submitted in 2022:

https://sourceware.org/pipermail/bzip2-devel/2022q2/000169.html

As Eli Schwartz wrote in that message:

> A pkg-config file is necessary in order to robustly
> communicate across build systems that bz2 is installed,
> *where* it is installed, and the correct CFLAGS / LDFLAGS to
> use in order to compile and link against it.

In a follow-up, he wrote:

https://sourceware.org/pipermail/bzip2-devel/2022q2/000171.html

> Some distros already provide one of these, so it's currently a
> bit inconsistent how to look for the library. As a result,
> there is software in the wild that probes for the library
> name, and fails if the library is installed to a custom
> prefix, and other software that checks for pkg-config, and
> fails on distros that don't provide their own bzip2.pc

The response from Sam James was:

https://sourceware.org/pipermail/bzip2-devel/2022q4/000176.html

> The whole series looks great, thanks for doing this.

The patch cannot be applied to bzip2 1.0.8 as is because it
modifies files configure.ac and Makefile.in which do not exist
in the bzip2 1.0.8 distribution. A previous patch in Eli's
series is needed to port the build system to autoconf:

https://sourceware.org/pipermail/bzip2-devel/2022q2/000170.html

-- 
You are receiving this mail because:
You are on the CC list for the bug.

             reply	other threads:[~2024-04-19 20:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-19 20:29 sourceware at ryandesign dot com [this message]
2024-04-19 20:36 ` [Bug bzip2/31660] " sourceware at ryandesign dot com
2024-04-20  7:44 ` sam at gentoo dot org
2024-04-21  1:46 ` eschwartz93 at gmail dot com
2024-04-21  2:33 ` sourceware at ryandesign dot com

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=bug-31660-11876@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=bzip2-devel@sourceware.org \
    /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).