All of lore.kernel.org
 help / color / mirror / Atom feed
From: <rs@ti.com>
To: <otavio.salvador@ossystems.com.br>, <alex.kanavin@gmail.com>
Cc: <richard.purdie@linuxfoundation.org>, <ross.burton@arm.com>,
	<alex@linutronix.de>, <otavio@ossystems.com.br>,
	<kexin.hao@windriver.com>, <afd@ti.com>, <detheridge@ti.com>,
	<denis@denix.org>, <reatmon@ti.com>,
	<openembedded-core@lists.openembedded.org>, <vijayp@ti.com>
Subject: [PATCH] bzip2: add libbz2.so.1.0 link for compat
Date: Thu, 13 Mar 2025 19:29:34 -0500	[thread overview]
Message-ID: <20250314002937.672768-3-rs@ti.com> (raw)
In-Reply-To: <20250314002937.672768-1-rs@ti.com>

From: Randolph Sapp <rs@ti.com>

Add a link from libbz2.so.1.0 to libbz2.so.${PV} for compatibility with
other distributions.

A handfull of distributions are still using the "Makefile-libbz2_so" to
generate libbz2 and bzip2-shared. This creates a library with a soname
of "libbz2.so.1.0". This library link is not provide by default in
autotools builds so add one here as Gentoo does now [1].

This has been addressed upstream already, but there hasn't been a stable
release since then [2].

[1] https://bugs.gentoo.org/338321
[2] https://gitlab.com/bzip2/bzip2/-/merge_requests/42

Signed-off-by: Randolph Sapp <rs@ti.com>
---
 meta/recipes-extended/bzip2/bzip2_1.0.8.bb | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/meta/recipes-extended/bzip2/bzip2_1.0.8.bb b/meta/recipes-extended/bzip2/bzip2_1.0.8.bb
index 78138d1543..02d81e7069 100644
--- a/meta/recipes-extended/bzip2/bzip2_1.0.8.bb
+++ b/meta/recipes-extended/bzip2/bzip2_1.0.8.bb
@@ -62,6 +62,11 @@ do_install_ptest () {
 	sed -i -e "s|^Makefile:|_Makefile:|" ${D}${PTEST_PATH}/Makefile
 }
 
+# add the following link for cross-distro compatibility
+do_install:append () {
+	ln -s libbz2.so.${PV} "${D}${libdir}/libbz2.so.1.0"
+}
+
 FILES:libbz2 = "${libdir}/lib*${SOLIBS}"
 
 RDEPENDS:${PN}-ptest += "make bash"
-- 
2.44.0



  parent reply	other threads:[~2025-03-14  0:30 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-14  0:29 [oe-core][RFC 0/3] Display manager proposal for x11 and wayland rs
2025-03-14  0:29 ` [PATCH] Revert "gettext: fix a parallel build issue" rs
2025-03-14 18:13   ` Ross Burton
2025-03-14 18:32     ` Randolph Sapp
2025-03-14  0:29 ` rs [this message]
2025-03-14  0:29 ` [oe-core][RFC 1/3] emptty: add version 0.13.0 rs
2025-03-14  0:29 ` [oe-core][RFC 2/3] weston-init: convert to virtual-emptty-conf rs
2025-03-14  0:48   ` Patchtest results for " patchtest
2025-03-14  0:29 ` [oe-core][RFC 3/3] default-providers: set virtual-emptty-conf rs
     [not found] ` <182C83EE5DCDDC9F.6194@lists.openembedded.org>
2025-03-14  0:39   ` [OE-core] [PATCH] Revert "gettext: fix a parallel build issue" Randolph Sapp
     [not found] ` <182C83EDE0EF5771.27055@lists.openembedded.org>
2025-03-14  0:40   ` [OE-core] [PATCH] bzip2: add libbz2.so.1.0 link for compat Randolph Sapp
2025-03-14  9:14 ` [oe-core][RFC 0/3] Display manager proposal for x11 and wayland Alexander Kanavin
2025-03-14 19:14   ` Randolph Sapp
2025-03-15  0:36     ` Randolph Sapp

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=20250314002937.672768-3-rs@ti.com \
    --to=rs@ti.com \
    --cc=afd@ti.com \
    --cc=alex.kanavin@gmail.com \
    --cc=alex@linutronix.de \
    --cc=denis@denix.org \
    --cc=detheridge@ti.com \
    --cc=kexin.hao@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=otavio.salvador@ossystems.com.br \
    --cc=otavio@ossystems.com.br \
    --cc=reatmon@ti.com \
    --cc=richard.purdie@linuxfoundation.org \
    --cc=ross.burton@arm.com \
    --cc=vijayp@ti.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.