File: support-i386.patch

package info (click to toggle)
chromium 142.0.7444.134-1~deb13u1
  • links: PTS, VCS
  • area: main
  • in suites: trixie
  • size: 6,295,436 kB
  • sloc: cpp: 35,487,404; ansic: 7,479,680; javascript: 4,259,373; python: 1,466,839; xml: 757,424; asm: 710,716; pascal: 187,980; sh: 89,247; perl: 88,690; objc: 79,984; sql: 56,984; cs: 42,192; fortran: 24,137; makefile: 22,913; tcl: 15,277; php: 14,018; yacc: 9,005; ruby: 7,553; awk: 3,720; lisp: 3,096; lex: 1,330; ada: 727; jsp: 228; sed: 36
file content (25 lines) | stat: -rw-r--r-- 945 bytes parent folder | download | duplicates (5) 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
 
author: Andres Salomon <dilinger@debian.org>
description: don't disable i386 builds on linux

https://chromium-review.googlesource.com/c/chromium/src/+/3583780

Chromium upstream decided to kill off i386 builds on Linux. They were
goin to add a 'force_x86_support' arg, but instead "[distributions that
still support i386] can patch the file."

At this point, i386 on linux is completely unsupported upstream, so
we're on our own with bugs.

--- a/BUILD.gn
+++ b/BUILD.gn
@@ -1500,9 +1500,7 @@ if (use_blink && !is_cronet_build) {
 # modulemaps requires building targets on linux-x86
 if (!running_modularize) {
   # TODO(cassew): Add more OS's that don't support x86.
-  is_valid_x86_target =
-      target_os != "ios" && target_os != "mac" &&
-      (target_os != "linux" || use_libfuzzer || !build_with_chromium)
+  is_valid_x86_target = true
 
   # Note: v8_target_cpu == arm allows using the V8 arm simulator on x86 for fuzzing.
   assert(