From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: libunwind: add patches for ppc*-musl
Date: Mon, 10 Jun 2019 01:27:25 +0200 [thread overview]
Message-ID: <20190609232725.LZnRFZNMk0uSN-cxjjmPJkD482Qhc9fNsgxYZVA3aM8@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-12360@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 837 bytes --]
New comment by pullmoll on void-packages repository
https://github.com/void-linux/void-packages/pull/12360#issuecomment-500254154
Comment:
Trying to build `strace` for `ppc-musl` or `ppc64-musl` with this PR's `libunwind` and `libucontext` gives me an error:
```
…
checking libunwind-ptrace.h usability... yes
checking libunwind-ptrace.h presence... yes
checking for libunwind-ptrace.h... yes
checking for backtrace in -lunwind... no
configure: error: in `/builddir/strace-5.1':
configure: error: failed to find libunwind
See `config.log' for more details
=> ERROR: strace-5.1_1: do_configure: '${configure_script} ${configure_args}' exited with 1
=> ERROR: in do_configure() at common/build-style/gnu-configure.sh:7
```
I don't know if perhaps `libunwind` for `*-musl` should `makedepends+=" libexecinfo-devel"`...
next prev parent reply other threads:[~2019-06-09 23:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-09 19:21 [PR PATCH] " voidlinux-github
2019-06-09 19:52 ` voidlinux-github
2019-06-09 20:16 ` [PR PATCH] [Updated] " voidlinux-github
2019-06-09 20:16 ` voidlinux-github
2019-06-09 20:18 ` voidlinux-github
2019-06-09 23:27 ` voidlinux-github [this message]
2019-06-09 23:53 ` voidlinux-github
2019-06-10 0:39 ` voidlinux-github
2019-06-10 0:45 ` [PR PATCH] [Updated] " voidlinux-github
2019-06-10 0:45 ` voidlinux-github
2019-06-10 0:45 ` voidlinux-github
2019-06-10 4:08 ` [PR PATCH] [Closed]: " voidlinux-github
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=20190609232725.LZnRFZNMk0uSN-cxjjmPJkD482Qhc9fNsgxYZVA3aM8@z \
--to=voidlinux-github@inbox.vuxu.org \
--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).