unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Marius Bakke <marius@gnu.org>
To: 54725@debbugs.gnu.org
Subject: [bug#54725] [PATCH 0/2] LLVM 14 and Chromium 99
Date: Tue,  5 Apr 2022 14:18:11 +0200	[thread overview]
Message-ID: <20220405121811.26289-1-marius@gnu.org> (raw)

Long time no see...  I have been battling poor health and injuries for
a while, but am slowly recovering.

First on my agenda is a long-overdue Chromium update.  It requires a newer
LLVM, which can not be built from individual tarballs due to
<https://github.com/llvm/llvm-project/issues/53281> and other problems
(likely fixed in 14.0.1).

This patch makes small adjustments to the LLVM and Clang build procedures
so they can be built from the LLVM "monorepo" instead of tarballs.

Feedback wanted!  I'm hoping to "fast track" these patches as Chromium 100
is already released with another slew of security fixes.  I will start
working on that next.

Marius Bakke (2):
  gnu: LLVM, Clang: Add 14.0.0.
  gnu: ungoogled-chromium: Update to 99.0.4844.84-1.

 gnu/local.mk                                  |   1 +
 gnu/packages/chromium.scm                     |  34 ++-
 gnu/packages/llvm.scm                         | 229 ++++++++++++------
 .../patches/clang-14.0-libc-search-path.patch |  94 +++++++
 gnu/packages/zig.scm                          |   2 +-
 5 files changed, 280 insertions(+), 80 deletions(-)
 create mode 100644 gnu/packages/patches/clang-14.0-libc-search-path.patch

-- 
2.34.0





             reply	other threads:[~2022-04-05 12:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-05 12:18 Marius Bakke [this message]
2022-04-05 12:20 ` [bug#54725] [PATCH 1/2] gnu: LLVM, Clang: Add 14.0.0 Marius Bakke
2022-04-05 12:20   ` [bug#54725] [PATCH 2/2] gnu: ungoogled-chromium: Update to 99.0.4844.84-1 Marius Bakke
2022-04-07 21:19 ` bug#54725: [PATCH 0/2] LLVM 14 and Chromium 99 Marius Bakke

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20220405121811.26289-1-marius@gnu.org \
    --to=marius@gnu.org \
    --cc=54725@debbugs.gnu.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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).