From: JamiKettunen <JamiKettunen@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] base-files: don't include lib32 files for musl
Date: Mon, 04 Dec 2023 18:33:27 +0100 [thread overview]
Message-ID: <20231204173327.TnbPako4-httJfol6491vBSV3kPCkuFk2NBtPK9Hidk@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-40659@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1554 bytes --]
There is an updated pull request by JamiKettunen against master on the void-packages repository
https://github.com/JamiKettunen/void-packages no-musl-multilib-base-files
https://github.com/void-linux/void-packages/pull/40659
base-files: don't include lib32 files for musl
Multilib on Void is [already only supported on glibc](https://docs.voidlinux.org/xbps/repositories/index.html#subrepositories) and as per the musl libc FAQ [there is no ldconfig](https://wiki.musl-libc.org/faq.html) (`/bin/ldconfig: symbolic link to true`).
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **YES**
<!--
#### New package
- This new package conforms to the [package requirements](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#package-requirements): **YES**|**NO**
-->
<!-- Note: If the build is likely to take more than 2 hours, please add ci skip tag as described in
https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration
and test at least one native build and, if supported, at least one cross build.
Ignore this section if this PR is not skipping CI.
-->
<!--
#### Local build testing
- I built this PR locally for my native architecture, (ARCH-LIBC)
- I built this PR locally for these architectures (if supported. mark crossbuilds):
- aarch64-musl
- armv7l
- armv6l-musl
-->
A patch file from https://github.com/void-linux/void-packages/pull/40659.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-no-musl-multilib-base-files-40659.patch --]
[-- Type: text/x-diff, Size: 1433 bytes --]
From 553cd47c381d1183d78294400bf0552f233c3f55 Mon Sep 17 00:00:00 2001
From: Jami Kettunen <jami.kettunen@protonmail.com>
Date: Mon, 21 Nov 2022 13:19:25 +0200
Subject: [PATCH] base-files: don't include lib32 files for musl
Multilib on Void is already only supported on glibc[1] and as per the
musl libc FAQ[2] there is no ldconfig.
[1] https://docs.voidlinux.org/xbps/repositories/index.html#subrepositories
[2] https://wiki.musl-libc.org/faq.html
---
srcpkgs/base-files/template | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/srcpkgs/base-files/template b/srcpkgs/base-files/template
index c3b59c8e6cd28..c9db827fe55b4 100644
--- a/srcpkgs/base-files/template
+++ b/srcpkgs/base-files/template
@@ -1,7 +1,7 @@
# Template file for 'base-files'
pkgname=base-files
version=0.143
-revision=3
+revision=4
bootstrap=yes
depends="xbps-triggers"
short_desc="Void Linux base system files"
@@ -46,8 +46,8 @@ do_install() {
ln -snrf "${DESTDIR}/usr/lib" \
"${DESTDIR}/${d}${XBPS_TARGET_WORDSIZE}"
done
- # Populate 32-bit lib files on 64-bit systems, for multilib.
- if [ "${XBPS_TARGET_WORDSIZE}" = "64" ]; then
+ # Populate 32-bit lib files on 64-bit glibc systems, for multilib.
+ if [ "${XBPS_TARGET_WORDSIZE}" = "64" ] && [ "${XBPS_TARGET_LIBC}" = "glibc" ]; then
vmkdir usr/lib32
ln -snrf "${DESTDIR}/usr/lib32" "${DESTDIR}/lib32"
ln -sf ../lib/locale "${DESTDIR}/usr/lib32/locale"
next prev parent reply other threads:[~2023-12-04 17:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-21 11:30 [PR PATCH] " JamiKettunen
2022-12-22 19:43 ` vincele
2023-03-23 1:53 ` github-actions
2023-04-07 1:49 ` [PR PATCH] [Closed]: " github-actions
2023-12-04 17:33 ` JamiKettunen [this message]
2023-12-26 17:51 ` [PR PATCH] [Merged]: " classabbyamp
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=20231204173327.TnbPako4-httJfol6491vBSV3kPCkuFk2NBtPK9Hidk@z \
--to=jamikettunen@users.noreply.github.com \
--cc=ml@inbox.vuxu.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 NNTP newsgroup(s).