From: Gottox <Gottox@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] muon: rebuild against libpkgconf.so.4
Date: Fri, 29 Mar 2024 10:16:22 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-49587@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1631 bytes --]
There is a new pull request by Gottox against master on the void-packages repository
https://github.com/Gottox/void-packages fix/muon-segfault
https://github.com/void-linux/void-packages/pull/49587
muon: rebuild against libpkgconf.so.4
muon started segfaulting after the recent pkgconf update:
```
~/src/sqsh-tools (main ✗) muon setup "build"
detected compiler gcc '13.2.0' (['cc']), linker ld.bfd
configuring 'sqsh-tools', version: 1.3.0
dependency threads found
found dependency threads
[1] 997 segmentation fault muon setup "build"
```
Rebuild it fixed the issue.
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **YES**|**briefly**|**NO**
<!--
#### 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/49587.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-fix/muon-segfault-49587.patch --]
[-- Type: text/x-diff, Size: 1032 bytes --]
From aa68b7415a9724c71d833bce6ea21ac4b0de8ba1 Mon Sep 17 00:00:00 2001
From: Enno Boland <gottox@voidlinux.org>
Date: Fri, 29 Mar 2024 10:12:14 +0100
Subject: [PATCH] muon: rebuild against libpkgconf.so.4
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
muon started segfaulting after the recent pkgconf update:
```
~/src/sqsh-tools (main ✗) muon setup "build"
detected compiler gcc '13.2.0' (['cc']), linker ld.bfd
configuring 'sqsh-tools', version: 1.3.0
dependency threads found
found dependency threads
[1] 997 segmentation fault muon setup "build"
```
Rebuild it fixed the issue.
---
srcpkgs/muon/template | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/srcpkgs/muon/template b/srcpkgs/muon/template
index 31ea11c5109bf3..d5ecb0f5ca0af8 100644
--- a/srcpkgs/muon/template
+++ b/srcpkgs/muon/template
@@ -1,7 +1,7 @@
# Template file for 'muon'
pkgname=muon
version=0.2.0
-revision=1
+revision=2
build_style=meson
build_helper="qemu"
configure_args="
next reply other threads:[~2024-03-29 9:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-29 9:16 Gottox [this message]
2024-03-31 8:15 ` [PR PATCH] [Merged]: " Gottox
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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-49587@inbox.vuxu.org \
--to=gottox@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).