From: sbromberger <sbromberger@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New package: llvm17
Date: Sun, 03 Dec 2023 02:49:10 +0100 [thread overview]
Message-ID: <20231203014910.mo34UpiKxBi7lWKOoZEI2CFTOq0BzVWa4gqoufm_SoE@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-46935@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 890 bytes --]
New comment by sbromberger on void-packages repository
https://github.com/void-linux/void-packages/pull/46935#issuecomment-1837306811
Comment:
I tried building this tonight on `Linux hydrogen 6.5.12_1 #1 SMP PREEMPT_DYNAMIC Mon Nov 20 18:31:50 UTC 2023 x86_64 GNU/Linux`
Results:
```console
...
Making all in debuginfod
CXXLD debuginfod
/usr/bin/ld: ../libelf/libelf.so: undefined reference to symbol 'inflateEnd'
/usr/bin/ld: /lib64/libz.so.1: error adding symbols: DSO missing from command line
collect2: error: ld returned 1 exit status
make[2]: *** [Makefile:618: debuginfod] Error 1
make[1]: *** [Makefile:537: all-recursive] Error 1
make: *** [Makefile:453: all] Error 2
=> ERROR: elfutils-0.189_1: do_build: '${make_cmd} ${makejobs} ${make_build_args} ${make_build_target}' exited with 2
=> ERROR: in do_build() at common/build-style/gnu-configure.sh:15
```
next prev parent reply other threads:[~2023-12-03 1:49 UTC|newest]
Thread overview: 120+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-28 1:03 [PR PATCH] WIP: " Calandracas606
2023-10-28 1:20 ` [PR PATCH] [Updated] " Calandracas606
2023-10-28 1:29 ` [PR REVIEW] " Calandracas606
2023-10-28 1:29 ` Calandracas606
2023-10-28 1:29 ` Calandracas606
2023-10-28 1:29 ` Calandracas606
2023-10-28 1:29 ` Calandracas606
2023-10-28 1:29 ` Calandracas606
2023-10-28 17:34 ` [WIP] " Calandracas606
2023-10-28 22:20 ` [PR REVIEW] " mhmdanas
2023-10-29 14:50 ` sh1r4s3
2023-10-29 14:53 ` sh1r4s3
2023-10-29 14:56 ` [PR PATCH] [Updated] " Calandracas606
2023-10-29 14:57 ` [PR REVIEW] " Calandracas606
2023-10-29 15:00 ` Calandracas606
2023-10-29 15:05 ` Calandracas606
2023-10-29 17:47 ` Calandracas606
2023-10-31 3:33 ` [PR PATCH] [Updated] " Calandracas606
2023-10-31 14:48 ` Calandracas606
2023-10-31 14:49 ` Calandracas606
2023-10-31 14:50 ` [PR PATCH] [Updated] " Calandracas606
2023-10-31 14:52 ` [PR REVIEW] " Calandracas606
2023-10-31 14:52 ` Calandracas606
2023-10-31 19:17 ` [PR PATCH] [Updated] " Calandracas606
2023-10-31 20:09 ` [PR REVIEW] " Calandracas606
2023-10-31 20:09 ` Calandracas606
2023-10-31 20:09 ` Calandracas606
2023-11-02 15:37 ` [PR PATCH] [Updated] " Calandracas606
2023-11-03 2:53 ` Calandracas606
2023-11-03 2:59 ` [PR REVIEW] " Calandracas606
2023-11-03 3:14 ` [PR PATCH] [Updated] " Calandracas606
2023-11-03 3:18 ` Calandracas606
2023-11-03 13:03 ` Calandracas606
2023-11-03 15:11 ` Calandracas606
2023-11-03 19:18 ` [PR REVIEW] " Calandracas606
2023-11-03 19:18 ` Calandracas606
2023-11-03 20:48 ` [PR PATCH] [Updated] " Calandracas606
2023-11-03 21:49 ` Calandracas606
2023-11-03 22:51 ` Calandracas606
2023-11-04 2:04 ` Calandracas606
2023-11-04 2:20 ` [PR REVIEW] " Calandracas606
2023-11-04 2:23 ` Calandracas606
2023-11-05 2:47 ` Calandracas606
2023-11-05 15:49 ` Calandracas606
2023-11-07 18:33 ` [PR PATCH] [Updated] " Calandracas606
2023-11-07 18:37 ` [PR REVIEW] " Calandracas606
2023-11-07 20:45 ` [PR PATCH] [Updated] " Calandracas606
2023-11-16 13:34 ` [PR REVIEW] " ahesford
2023-11-16 16:33 ` Calandracas606
2023-11-16 20:52 ` tranzystorekk
2023-12-02 23:43 ` [PR PATCH] [Updated] " Calandracas606
2023-12-03 1:49 ` sbromberger [this message]
2023-12-03 13:36 ` sbromberger
2023-12-03 13:37 ` sbromberger
2023-12-03 18:45 ` [PR PATCH] [Updated] " Calandracas606
2023-12-06 3:38 ` Calandracas606
2023-12-06 18:38 ` Calandracas606
2023-12-07 0:48 ` Calandracas606
2023-12-08 4:12 ` Calandracas606
2023-12-12 17:29 ` Calandracas606
2023-12-16 19:01 ` Calandracas606
2023-12-16 19:39 ` Calandracas606
2023-12-17 0:29 ` Calandracas606
2023-12-26 16:34 ` Calandracas606
2023-12-31 3:58 ` Calandracas606
2024-01-03 21:22 ` Calandracas606
2024-01-03 21:24 ` Calandracas606
2024-01-08 13:37 ` [PR PATCH] [Updated] " Calandracas606
2024-01-09 5:08 ` Calandracas606
2024-01-09 5:14 ` sbromberger
2024-01-09 5:59 ` Calandracas606
2024-01-09 6:00 ` Calandracas606
2024-01-10 3:31 ` [PR PATCH] [Updated] " Calandracas606
2024-01-10 19:51 ` Calandracas606
2024-01-11 12:27 ` Luciogi
2024-01-11 12:39 ` [PR PATCH] [Updated] " Calandracas606
2024-01-11 12:40 ` Calandracas606
2024-01-11 13:02 ` Calandracas606
2024-01-12 13:07 ` Luciogi
2024-01-12 13:07 ` Luciogi
2024-01-12 13:23 ` Calandracas606
2024-01-16 19:43 ` [PR REVIEW] " Calandracas606
2024-01-17 16:30 ` Luciogi
2024-01-17 16:30 ` Luciogi
2024-01-17 17:09 ` Calandracas606
2024-01-26 0:03 ` [PR PATCH] [Updated] " Calandracas606
2024-01-26 0:06 ` Calandracas606
2024-01-30 13:23 ` [PR PATCH] [Updated] " Calandracas606
2024-01-30 13:26 ` Calandracas606
2024-01-30 22:17 ` Calandracas606
2024-01-30 22:18 ` Calandracas606
2024-01-31 2:35 ` [PR PATCH] [Updated] " Calandracas606
2024-01-31 3:01 ` Calandracas606
2024-01-31 4:50 ` [PR PATCH] [Updated] " Calandracas606
2024-01-31 17:38 ` Calandracas606
2024-01-31 20:58 ` Calandracas606
2024-01-31 21:42 ` Calandracas606
2024-02-01 3:41 ` Calandracas606
2024-02-01 4:01 ` Calandracas606
2024-02-01 17:39 ` [PR PATCH] [Updated] " Calandracas606
2024-02-01 17:49 ` Calandracas606
2024-02-01 20:43 ` Calandracas606
2024-02-01 20:58 ` Calandracas606
2024-02-01 22:52 ` [PR PATCH] [Updated] " Calandracas606
2024-02-01 23:03 ` Calandracas606
2024-02-02 4:14 ` Calandracas606
2024-02-02 4:15 ` Calandracas606
2024-02-02 5:00 ` [PR PATCH] [Updated] " Calandracas606
2024-02-03 19:42 ` Calandracas606
2024-02-03 19:45 ` Calandracas606
2024-02-05 23:33 ` Calandracas606
2024-02-07 15:38 ` Calandracas606
2024-02-07 23:54 ` Calandracas606
2024-02-08 0:02 ` Calandracas606
2024-02-08 0:05 ` Calandracas606
2024-02-08 0:17 ` Calandracas606
2024-02-08 21:40 ` dkwo
2024-02-08 21:47 ` dkwo
2024-02-12 3:49 ` Calandracas606
2024-02-12 13:13 ` [PR PATCH] [Closed]: " leahneukirchen
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=20231203014910.mo34UpiKxBi7lWKOoZEI2CFTOq0BzVWa4gqoufm_SoE@z \
--to=sbromberger@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).