From: ericonr <ericonr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: ldc: update to 1.26.0.
Date: Wed, 26 May 2021 05:12:10 +0200 [thread overview]
Message-ID: <20210526031210.BxB5dOaNvumwWSULbX6wTOj26mB-zCQcIa-63DoYzfI@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-31062@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 2448 bytes --]
There's a merged pull request on the void-packages repository
ldc: update to 1.26.0.
https://github.com/void-linux/void-packages/pull/31062
Description:
Also move to llvm12.
@q66
It ends up underlinked, because when I try building corecollector with it I get:
```
Project version: 0.3.5
Error relocating /usr/lib/libdruntime-ldc-shared.so.96: unw_init_local: symbol not found
Error relocating /usr/lib/libdruntime-ldc-shared.so.96: unw_get_proc_name: symbol not found
Error relocating /usr/lib/libdruntime-ldc-shared.so.96: unw_step: symbol not found
Error relocating /usr/lib/libdruntime-ldc-shared.so.96: unw_getcontext: symbol not found
Error relocating /usr/lib/libdruntime-ldc-shared.so.96: unw_get_proc_info: symbol not found
meson.build:1:0: ERROR: Executables created by D compiler ldc2 are not runnable.
```
But running with `LD_PRELOAD=/usr/lib/libunwind.so.1` after installing `llvm-libunwind` makes meson not complain.
Alpine seems to be doing a trick to build with `libunwind` (https://git.alpinelinux.org/aports/tree/community/ldc/APKBUILD): `-DC_SYSTEM_LIBS="unwind;m;pthread;rt;dl"`, which we can probably just appropriate.
<!-- Mark items with [x] where applicable -->
#### General
- [ ] This is a new package and it conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements)
#### Have the results of the proposed changes been tested?
- [ ] I use the packages affected by the proposed changes on a regular basis and confirm this PR works for me
- [ ] I generally don't use the affected packages but briefly tested this PR
<!--
If GitHub CI cannot be used to validate the build result (for example, if the
build is likely to take several hours), make sure to
[skip CI](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration).
When skipping CI, uncomment and fill out the following section.
Note: for builds that are likely to complete in less than 2 hours, it is not
acceptable to skip CI.
-->
<!--
#### Does it build and run successfully?
(Please choose at least one native build and, if supported, at least one cross build. More are better.)
- [ ] 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
-->
prev parent reply other threads:[~2021-05-26 3:12 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-22 6:55 [PR PATCH] " ericonr
2021-05-22 11:13 ` q66
2021-05-22 18:49 ` [PR PATCH] [Updated] " ericonr
2021-05-22 19:00 ` ericonr
2021-05-22 20:17 ` q66
2021-05-22 23:12 ` ericonr
2021-05-23 2:29 ` [PR PATCH] [Updated] " ericonr
2021-05-23 2:53 ` ericonr
2021-05-23 3:22 ` ericonr
2021-05-23 3:23 ` ericonr
2021-05-23 3:36 ` ericonr
2021-05-23 4:23 ` ericonr
2021-05-23 15:01 ` aurieh
2021-05-25 19:08 ` [PR PATCH] [Updated] " ericonr
2021-05-25 23:19 ` aurieh
2021-05-26 0:11 ` ericonr
2021-05-26 3:12 ` ericonr [this message]
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=20210526031210.BxB5dOaNvumwWSULbX6wTOj26mB-zCQcIa-63DoYzfI@z \
--to=ericonr@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).