Github messages for voidlinux
 help / color / mirror / Atom feed
From: Calandracas606 <Calandracas606@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] chromium: fix build with gcc13
Date: Thu, 01 Feb 2024 15:40:56 +0100	[thread overview]
Message-ID: <20240201144056.1BE0428D80@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-48474@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 1143 bytes --]

There is an updated pull request by Calandracas606 against master on the void-packages repository

https://github.com/Calandracas606/void-packages chromium-gcc13-fix
https://github.com/void-linux/void-packages/pull/48474

chromium: fix build with gcc13
<!-- Uncomment relevant sections and delete options which are not applicable -->

#### Testing the changes
- I tested the changes in this PR: **NO**

<!--
#### New package
- This new package conforms to the [package requirements](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#package-requirements): **YES**|**NO**
-->

<!-- Note: If the build is likely to take more than 2 hours, please add ci skip tag as described in
https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration
and test at least one native build and, if supported, at least one cross build.
Ignore this section if this PR is not skipping CI.
-->

#### Local build testing
- I built this PR locally for my native architecture, x86_64-musl

[ci skip]


A patch file from https://github.com/void-linux/void-packages/pull/48474.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-chromium-gcc13-fix-48474.patch --]
[-- Type: text/x-diff, Size: 1378 bytes --]

From 8195c7dcda73d9ff5fda7eb89f797253bb654fde Mon Sep 17 00:00:00 2001
From: Daniel Martinez <danielmartinez@cock.li>
Date: Wed, 31 Jan 2024 23:27:34 -0500
Subject: [PATCH] chromium: fix build with gcc13

---
 srcpkgs/chromium/patches/gcc13-wnoerror.patch | 21 +++++++++++++++++++
 1 file changed, 21 insertions(+)
 create mode 100644 srcpkgs/chromium/patches/gcc13-wnoerror.patch

diff --git a/srcpkgs/chromium/patches/gcc13-wnoerror.patch b/srcpkgs/chromium/patches/gcc13-wnoerror.patch
new file mode 100644
index 0000000000000..c069aa41b2d09
--- /dev/null
+++ b/srcpkgs/chromium/patches/gcc13-wnoerror.patch
@@ -0,0 +1,21 @@
+https://gn.googlesource.com/gn/+/c7b223bfb225ce87a72a244d016ffdfcf227fa5e%5E%21/
+Ignore build warning -Werror=redundant-move
+
+gcc-13 complains with:
+error: redundant move in return statement [-Werror=redundant-move]
+
+We cannot fix the code, because both old versions of gcc and the windows
+toolchain fails to build.
+index adb622a..232e536 100755
+--- a/tools/gn/build/gen.py
++++ b/tools/gn/build/gen.py
+
+@@ -472,6 +472,8 @@
+     # flags not supported by gcc/g++.
+     if cxx == 'clang++':
+       cflags.extend(['-Wrange-loop-analysis', '-Wextra-semi-stmt'])
++    else:
++      cflags.append('-Wno-redundant-move')
+ 
+     if platform.is_linux() or platform.is_mingw() or platform.is_msys():
+       ldflags.append('-Wl,--as-needed')

  parent reply	other threads:[~2024-02-01 14:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-01  4:39 [PR PATCH] " Calandracas606
2024-02-01 12:35 ` [PR PATCH] [Updated] " Calandracas606
2024-02-01 14:09 ` Duncaen
2024-02-01 14:40 ` Calandracas606 [this message]
2024-02-01 14:46 ` Calandracas606
2024-02-01 15:09 ` [PR PATCH] [Merged]: " 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=20240201144056.1BE0428D80@inbox.vuxu.org \
    --to=calandracas606@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).