From: tranzystorek-io <tranzystorek-io@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: LLVM 15
Date: Mon, 13 Mar 2023 15:27:40 +0100 [thread overview]
Message-ID: <20230313142740.UwLoOCT-TTdoVIVUpKscN0G-spSxjsc_eaL-H7H4mVE@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-40821@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1229 bytes --]
New comment by tranzystorek-io on void-packages repository
https://github.com/void-linux/void-packages/pull/40821#issuecomment-1466246146
Comment:
> Did a git bisect on the 32bit arm build failure.
>
> It broke with the following commit [llvm/llvm-project@425620c](https://github.com/llvm/llvm-project/commit/425620ccdd47e56b59512913cdc71e116f951e4e) but I'm unsure on how to fix it correctly.
>
> ```
> /usr/lib/gcc/armv7l-linux-gnueabihf/12.2.0/../../../../armv7l-linux-gnueabihf/bin/ld: projects/libcxx/src/CMakeFiles/cxx_shared.dir/locale.cpp.o: in function `std::__1::__time_get_c_storage<char>::__x() const [clone .localalias]':
> locale.cpp:(.text._ZNKSt3__120__time_get_c_storageIcE3__xEv+0xb4): undefined reference to `std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >::~basic_string()'
> /usr/lib/gcc/armv7l-linux-gnueabihf/12.2.0/../../../../armv7l-linux-gnueabihf/bin/ld: projects/libcxx/src/CMakeFiles/cxx_shared.dir/locale.cpp.o: in function `std::__1::__time_get_c_storage<char>::__X() const [clone .localalias]':
> ```
>
> Build log: https://gist.github.com/Johnnynator/e9dddc63100c212303fb81aa27cc39f6
This is still unresolved, I'll add it to the TODO list.
next prev parent reply other threads:[~2023-03-13 14:27 UTC|newest]
Thread overview: 96+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-28 15:30 [PR PATCH] [WIP] " tranzystorek-io
2022-11-28 15:32 ` tranzystorek-io
2022-11-28 16:36 ` dkwo
2022-11-28 19:13 ` [PR PATCH] [Updated] " tranzystorek-io
2022-11-28 23:49 ` tranzystorek-io
2022-11-29 0:31 ` tranzystorek-io
2022-12-05 8:05 ` tranzystorek-io
2022-12-05 8:17 ` tranzystorek-io
2022-12-05 8:22 ` [PR REVIEW] " oreo639
2022-12-05 8:22 ` oreo639
2022-12-05 8:29 ` oreo639
2022-12-05 8:29 ` oreo639
2022-12-05 8:30 ` oreo639
2022-12-05 8:39 ` oreo639
2022-12-05 9:28 ` oreo639
2022-12-05 9:55 ` oreo639
2022-12-05 9:55 ` oreo639
2022-12-06 10:11 ` [PR PATCH] [Updated] " tranzystorek-io
2022-12-07 5:04 ` Vaelatern
2022-12-07 5:04 ` Vaelatern
2022-12-12 18:26 ` [PR PATCH] [Updated] " tranzystorek-io
2022-12-17 8:56 ` tranzystorek-io
2022-12-17 9:00 ` tranzystorek-io
2022-12-17 9:09 ` tranzystorek-io
2022-12-17 10:44 ` [PR REVIEW] " paper42
2022-12-17 23:41 ` [PR PATCH] [Updated] " tranzystorek-io
2022-12-18 0:02 ` [PR REVIEW] " oreo639
2022-12-18 0:03 ` oreo639
2022-12-18 0:05 ` oreo639
2022-12-18 11:24 ` [PR PATCH] [Updated] " tranzystorek-io
2022-12-18 23:30 ` tranzystorek-io
2022-12-19 23:58 ` oreo639
2022-12-19 23:59 ` oreo639
2022-12-20 0:04 ` oreo639
2022-12-20 0:09 ` oreo639
2022-12-22 4:26 ` simvux
2022-12-22 4:48 ` oreo639
2022-12-22 10:15 ` ardadem
2023-01-05 14:13 ` [PR PATCH] [Updated] " tranzystorek-io
2023-01-06 12:39 ` [PR REVIEW] " tranzystorek-io
2023-01-06 12:56 ` [PR PATCH] [Updated] " tranzystorek-io
2023-01-06 16:15 ` tranzystorek-io
2023-01-07 10:31 ` tranzystorek-io
2023-01-07 17:02 ` tranzystorek-io
2023-01-09 0:22 ` tranzystorek-io
2023-01-09 0:58 ` tranzystorek-io
2023-01-10 8:20 ` dkwo
2023-01-12 18:46 ` [PR PATCH] [Updated] " tranzystorek-io
2023-01-14 22:16 ` Johnnynator
2023-01-15 1:46 ` [PR PATCH] [Updated] " tranzystorek-io
2023-01-16 13:45 ` tranzystorek-io
2023-01-17 19:01 ` [PR REVIEW] " Johnnynator
2023-01-24 13:05 ` [PR PATCH] [Updated] " tranzystorek-io
2023-01-24 13:15 ` tranzystorek-io
2023-01-26 22:36 ` tranzystorek-io
2023-02-01 12:34 ` tranzystorek-io
2023-02-05 12:42 ` tranzystorek-io
2023-02-05 13:58 ` tranzystorek-io
2023-02-07 9:14 ` tranzystorek-io
2023-02-10 14:20 ` tranzystorek-io
2023-02-10 14:49 ` oreo639
2023-02-10 14:50 ` oreo639
2023-02-10 14:51 ` oreo639
2023-02-10 14:51 ` oreo639
2023-02-10 14:55 ` oreo639
2023-02-10 16:26 ` [PR PATCH] [Updated] " tranzystorek-io
2023-02-10 16:42 ` tranzystorek-io
2023-02-10 19:21 ` tranzystorek-io
2023-02-15 17:27 ` tranzystorek-io
2023-02-16 19:17 ` tranzystorek-io
2023-02-16 22:44 ` tranzystorek-io
2023-02-18 19:34 ` tranzystorek-io
2023-02-19 22:34 ` simvux
2023-02-20 9:59 ` cmueller-tp
2023-02-22 12:35 ` [PR PATCH] [Updated] " tranzystorek-io
2023-02-22 14:35 ` tranzystorek-io
2023-02-22 19:26 ` tranzystorek-io
2023-02-22 19:41 ` [PR PATCH] [Updated] " tranzystorek-io
2023-02-24 22:55 ` Johnnynator
2023-03-01 14:02 ` [PR PATCH] [Updated] " tranzystorek-io
2023-03-10 14:35 ` tranzystorek-io
2023-03-13 14:25 ` motorto
2023-03-13 14:27 ` tranzystorek-io [this message]
2023-03-18 3:31 ` ihameed
2023-03-18 3:39 ` ihameed
2023-03-18 4:46 ` ihameed
2023-03-18 9:35 ` [PR PATCH] [Updated] " tranzystorek-io
2023-03-18 16:35 ` tranzystorek-io
2023-03-25 6:04 ` oreo639
2023-03-25 13:04 ` [PR PATCH] [Updated] " tranzystorek-io
2023-03-25 13:10 ` tranzystorek-io
2023-03-30 22:02 ` tranzystorek-io
2023-03-31 13:28 ` [PR PATCH] [Closed]: " leahneukirchen
2023-04-02 12:17 ` simvux
2023-04-02 12:18 ` tranzystorek-io
2023-04-02 12:19 ` simvux
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=20230313142740.UwLoOCT-TTdoVIVUpKscN0G-spSxjsc_eaL-H7H4mVE@z \
--to=tranzystorek-io@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).