From: meator <meator@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] strace: revbump
Date: Sat, 02 Mar 2024 22:47:34 +0100 [thread overview]
Message-ID: <20240302214734.545A3232F5@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-49037@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1511 bytes --]
There is an updated pull request by meator against master on the void-packages repository
https://github.com/meator/void-packages strace
https://github.com/void-linux/void-packages/pull/49037
strace: revbump
This fixes the
```
strace: Symbol `_UPT_accessors' has different size in shared object, consider re-linking
```
warning. I don't know what causes this warning. A proper solution that would prevent this warning from appearing again in the future would probably be better.
<!-- 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/49037.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-strace-49037.patch --]
[-- Type: text/x-diff, Size: 928 bytes --]
From cc8238508fa02a6a9ad12c1c150f4b2d8d490ca0 Mon Sep 17 00:00:00 2001
From: meator <meator.dev@gmail.com>
Date: Sat, 2 Mar 2024 21:22:22 +0100
Subject: [PATCH] strace: rebuild against newer libunwind
This fixes the
strace: Symbol `_UPT_accessors' has different size in shared object,
consider re-linking
warning.
An ABI break was introduced in
https://github.com/libunwind/libunwind/commit/d7e59261feb4f9425728ae08031bee3d5bf6e48a
---
srcpkgs/strace/template | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/srcpkgs/strace/template b/srcpkgs/strace/template
index 6448685e7967d8..483c3680db54f9 100644
--- a/srcpkgs/strace/template
+++ b/srcpkgs/strace/template
@@ -1,7 +1,7 @@
# Template file for 'strace'
pkgname=strace
version=6.7
-revision=1
+revision=2
build_style=gnu-configure
configure_args="--enable-silent-rules $(vopt_with libunwind)"
makedepends="$(vopt_if libunwind libunwind-devel)"
next prev parent reply other threads:[~2024-03-02 21:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-02 20:25 [PR PATCH] " meator
2024-03-02 20:55 ` icp1994
2024-03-02 21:34 ` oreo639
2024-03-02 21:47 ` meator [this message]
2024-03-03 1:03 ` [PR PATCH] [Merged]: strace: rebuild against newer libunwind oreo639
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=20240302214734.545A3232F5@inbox.vuxu.org \
--to=meator@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).