From: q66 <q66@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Llvm14
Date: Mon, 23 May 2022 17:34:38 +0200 [thread overview]
Message-ID: <20220523153438.iTRenTrniSTbCoZ9pS9UPMN3Md61FOWlSnhILtGQFpM@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-36962@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 427 bytes --]
New comment by q66 on void-packages repository
https://github.com/void-linux/void-packages/pull/36962#issuecomment-1134827093
Comment:
you don't need the last one at all (it's needed for systems that are built with llvm without gcc and bootstrap themselves)
the first one is not strictly needed for the installation location but it's still a good idea to take it
the second one should probably fix the actual locations
next prev parent reply other threads:[~2022-05-23 15:34 UTC|newest]
Thread overview: 71+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-02 20:43 [PR PATCH] Llvm14 prez
2022-05-02 23:21 ` [PR PATCH] [Updated] Llvm14 prez
2022-05-03 9:03 ` Llvm14 ifreund
2022-05-04 12:17 ` [PR PATCH] [Updated] Llvm14 prez
2022-05-04 17:10 ` prez
2022-05-04 20:26 ` prez
2022-05-04 20:50 ` prez
2022-05-05 1:10 ` prez
2022-05-05 1:25 ` prez
2022-05-05 12:31 ` [PR REVIEW] Llvm14 ftrvxmtrx
2022-05-05 13:18 ` [PR PATCH] [Updated] Llvm14 prez
2022-05-05 13:23 ` Llvm14 prez
2022-05-05 16:19 ` Llvm14 q66
2022-05-05 22:45 ` [PR PATCH] [Updated] Llvm14 prez
2022-05-05 22:55 ` Llvm14 q66
2022-05-05 23:08 ` Llvm14 prez
2022-05-05 23:09 ` Llvm14 prez
2022-05-05 23:16 ` Llvm14 prez
2022-05-22 11:20 ` Llvm14 wael444
2022-05-22 16:52 ` Llvm14 motorto
2022-05-23 1:03 ` [PR PATCH] [Updated] Llvm14 prez
2022-05-23 1:20 ` prez
2022-05-23 1:56 ` Llvm14 prez
2022-05-23 1:56 ` Llvm14 prez
2022-05-23 8:34 ` Llvm14 q66
2022-05-23 11:45 ` Llvm14 prez
2022-05-23 13:41 ` Llvm14 q66
2022-05-23 13:50 ` Llvm14 prez
2022-05-23 13:51 ` Llvm14 prez
2022-05-23 15:34 ` q66 [this message]
2022-05-25 1:22 ` [PR PATCH] [Updated] Llvm14 prez
2022-05-25 1:23 ` Llvm14 prez
2022-06-04 20:43 ` Llvm14 motorto
2022-06-05 13:31 ` Llvm14 prez
2022-06-05 13:35 ` Llvm14 prez
2022-06-05 13:51 ` Llvm14 motorto
2022-06-05 16:32 ` Llvm14 wael444
2022-06-07 12:01 ` Llvm14 dkwo
2022-06-07 18:55 ` Llvm14 motorto
2022-06-07 18:56 ` Llvm14 motorto
2022-06-07 20:04 ` [PR PATCH] [Updated] Llvm14 prez
2022-06-07 20:06 ` Llvm14 prez
2022-06-07 20:12 ` Llvm14 prez
2022-06-07 20:26 ` Llvm14 Duncaen
2022-06-08 1:20 ` [PR PATCH] [Updated] Llvm14 prez
2022-06-12 9:17 ` Llvm14 motorto
2022-06-13 5:42 ` Llvm14 motorto
2022-06-13 5:42 ` Llvm14 motorto
2022-06-13 5:43 ` Llvm14 motorto
2022-06-13 11:24 ` [PR REVIEW] Llvm14 q66
2022-06-13 11:24 ` Llvm14 prez
2022-06-13 12:38 ` Llvm14 motorto
2022-06-13 13:39 ` Llvm14 q66
2022-06-13 13:55 ` Llvm14 prez
2022-06-13 14:03 ` [PR REVIEW] Llvm14 prez
2022-06-13 14:07 ` Llvm14 prez
2022-06-13 14:07 ` Llvm14 prez
2022-06-13 16:37 ` Llvm14 q66
2022-07-11 17:03 ` Llvm14 gbrlsnchs
2022-07-14 10:55 ` Llvm14 prez
2022-08-01 11:14 ` Llvm14 JamiKettunen
2022-09-07 1:42 ` Llvm14 prez
2022-09-07 1:42 ` [PR PATCH] [Closed]: Llvm14 prez
2022-09-07 7:21 ` Llvm14 averycoolbean
2022-09-07 7:31 ` Llvm14 wael444
2022-09-07 17:31 ` Llvm14 dkwo
2022-09-08 10:15 ` Llvm14 RicArch97
2022-09-08 10:15 ` Llvm14 RicArch97
2022-09-08 15:27 ` Llvm14 agausmann
2022-10-04 19:51 ` Llvm14 dkwo
2022-10-04 19:53 ` Llvm14 Duncaen
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=20220523153438.iTRenTrniSTbCoZ9pS9UPMN3Md61FOWlSnhILtGQFpM@z \
--to=q66@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).