File: clang-version-check.patch

package info (click to toggle)
chromium 143.0.7499.169-1
  • links: PTS, VCS
  • area: main
  • in suites: sid
  • size: 5,786,920 kB
  • sloc: cpp: 35,784,218; ansic: 7,477,365; javascript: 3,962,116; python: 1,480,523; xml: 764,832; asm: 710,816; pascal: 188,028; sh: 88,717; perl: 88,692; objc: 79,984; sql: 57,625; cs: 42,265; fortran: 24,101; makefile: 22,509; tcl: 15,277; php: 14,018; yacc: 9,043; ruby: 7,553; awk: 3,720; lisp: 3,233; lex: 1,330; ada: 727; jsp: 228; sed: 36
file content (22 lines) | stat: -rw-r--r-- 844 bytes parent folder | download | duplicates (8) 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
 
description: remove strict clang version check during config
author: Andres Salomon <dilinger@debian.org>

Chromium 107 has a strict clang version check, added in commit
8f23a2c2d14fd799813134e995c160354d75d3a0. This needs a proper fix
upstream; some way to check (or specify) whether it's a distribution
build, and therefore shouldn't require a particular git version of
clang.

For now, let's just get this building in debian.

--- a/tools/clang/scripts/update.py
+++ b/tools/clang/scripts/update.py
@@ -355,7 +355,7 @@ def main():
       return 0
 
     stamp_version = ReadStampFile(STAMP_FILE).partition(',')[0]
-    if PACKAGE_VERSION != stamp_version:
+    if False:
       print('The expected clang version is %s but the actual version is %s' %
             (PACKAGE_VERSION, stamp_version))
       print('Did you run "gclient sync"?')