Re: Bug#1109861: thunderbird: Please build with gcc and g++ on ppc64

John Paul Adrian Glaubitz <[email protected]>
Newsgroups gmane.linux.debian.ports.powerpc
Message-ID <989452bff3f7c7513fdb2a0fe0e81523f87aa615.camel@physik.fu-berlin.de>
Hello,

On Fri, 2025-07-25 at 10:11 +0200, John Paul Adrian Glaubitz wrote:
> on ppc64, Thunderbird currently fails to build from source [1] due to an
> upstream bug in the PowerPC backend in LLVM [2].
> 
> Could you override CC and CXX so Thunderbird is built with GCC instead of
> Clang for the time being?

Attaching an updating patch. We actually need to export CC and CXX so all parts
of the build make use of gcc and g++. This requires an additional patch which
fixes an old keyword in moz.build for skia (see attached).

Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer
`. `'   Physicist
  `-    GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913
thunderbird-override-clang.diff (text/x-patch, 454 B)
--- debian/rules.orig	2025-07-25 01:09:59.688831332 -0700
+++ debian/rules	2025-07-25 02:31:52.730623151 -0700
@@ -46,6 +46,11 @@
 	CFLAGS += -DSQLITE_BYTEORDER=1234
 endif
 
+ifneq (,$(filter ppc64,$(DEB_HOST_ARCH)))
+	export CC := gcc
+	export CXX := g++
+endif
+
 # Reduce memory usage of the linker at the expense of processing time
 # This should help on lower-end architectures like arm and mips, which
 # spend an immense amount of time swapping.
fix-ppc64-moz-build.patch (text/x-patch, 461 B)
--- thunderbird-128.12.0esr.orig/gfx/skia/moz.build
+++ thunderbird-128.12.0esr/gfx/skia/moz.build
@@ -371,7 +371,7 @@ UNIFIED_SOURCES += [
 ]
 
 # Work around https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110606
-if CONFIG['CC_TYPE'] == 'gcc' and CONFIG['CPU_ARCH'] == 'ppc64':
+if CONFIG['CC_TYPE'] == 'gcc' and CONFIG['TARGET_CPU'] == 'ppc64':
     SOURCES += ['skia/src/sksl/SkSLInliner.cpp']
 else:
     UNIFIED_SOURCES += ['skia/src/sksl/SkSLInliner.cpp']
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.