From: q66 <q66@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Closed]: llvm: Update to 11.0.0
Date: Tue, 17 Nov 2020 04:16:08 +0100 [thread overview]
Message-ID: <20201117031608.yHlgpG740vCDZuIOnIG-2_LbrP-aWWugGA25AS6SNVs@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-26231@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1067 bytes --]
There's a closed pull request on the void-packages repository
llvm: Update to 11.0.0
https://github.com/void-linux/void-packages/pull/26231
Description:
Update llvm and its subprojects to 11.0.0.
There were a few details i solved as follows:
* For llvm11, files/llvm-Config-config.h was not used, so i removed it. Same for llvm10
* I just copied all patches from llvm10, which yielded a few problems:
- Some code near clang-004-ppc64-musl-elfv2.patch got changed so i re-made the patch
- llvm-007-ppc-d85007.patch [seems to have been implemented upstream](https://github.com/llvm/llvm-project/commit/cbea17568f4301582c1d5d43990f089ca6cff522)
* subpackages (clang, lld, lldb, etc) were removed from llvm10 as they are provided by llvm11 now
* llvm-unwind(-devel) and libcxx(-devel) were updated to 11.0.0
* There was a [sed expression](https://github.com/void-linux/void-packages/blob/4712555551b5140760a17948a5c38eac1cf13ddc/srcpkgs/libcxx/template#L27) in the extract step for libcxx, it seems that this has been changed upstream so i removed it.
prev parent reply other threads:[~2020-11-17 3:16 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-09 0:46 [PR PATCH] " Snektron
2020-11-09 1:05 ` [PR PATCH] [Updated] " Snektron
2020-11-09 1:33 ` [PR REVIEW] [WIP] " fosslinux
2020-11-09 1:33 ` fosslinux
2020-11-09 1:33 ` fosslinux
2020-11-09 1:33 ` fosslinux
2020-11-09 1:33 ` fosslinux
2020-11-09 1:34 ` fosslinux
2020-11-09 1:57 ` [PR REVIEW] " Snektron
2020-11-09 1:58 ` [PR PATCH] [Updated] " Snektron
2020-11-09 2:39 ` Snektron
2020-11-09 3:02 ` [PR REVIEW] " fosslinux
2020-11-09 7:42 ` fosslinux
2020-11-09 7:42 ` fosslinux
2020-11-09 12:11 ` [PR PATCH] [Updated] " Snektron
2020-11-09 12:59 ` Snektron
2020-11-09 13:01 ` Snektron
2020-11-09 13:03 ` Snektron
2020-11-09 14:20 ` Snektron
2020-11-09 16:46 ` Snektron
2020-11-09 16:56 ` q66
2020-11-09 17:14 ` [PR PATCH] [Updated] " Snektron
2020-11-09 17:15 ` Snektron
2020-11-09 18:29 ` Snektron
2020-11-09 19:00 ` Snektron
2020-11-09 19:11 ` Snektron
2020-11-09 19:52 ` Snektron
2020-11-09 20:03 ` Snektron
2020-11-09 20:32 ` Snektron
2020-11-09 20:32 ` Snektron
2020-11-11 11:20 ` Snektron
2020-11-12 6:22 ` fosslinux
2020-11-12 14:06 ` [PR PATCH] [Updated] " Snektron
2020-11-17 3:16 ` q66 [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=20201117031608.yHlgpG740vCDZuIOnIG-2_LbrP-aWWugGA25AS6SNVs@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).