[1] https://buildd.debian.org/status/fetch.php?pkg=libreoffice&arch=powerpc&ver=4%3A26.2.0%7Ebeta1-1&stamp=1765108295&raw=0
[2] https://lists.freedesktop.org/archives/libreoffice/2025-December/094089.html
[3] https://lists.freedesktop.org/archives/libreoffice/2025-December/094090.html
Thus, we need to figure out why the build doesn't actually generated the wrapper scriptSo, it turns out that the wrapper script wasn't copied because hppa, m68k and powerpc
for hppa, powerpc (and probably m68k) in order to fix the smokeest on these targets.
On Wed, 2025-12-10 at 08:40 +0100, John Paul Adrian Glaubitz wrote:
Thus, we need to figure out why the build doesn't actually generated the wrapper scriptSo, it turns out that the wrapper script wasn't copied
for hppa, powerpc (and probably m68k) in order to fix the smokeest on these targets.
because hppa, m68k and powerpc are listed in OOO_NOGUI_ARCHS which the following patch fixes:
--- debian/rules.orig 2025-12-11 15:56:17.424880233 +0000
+++ debian/rules 2025-12-10 11:19:19.696634221 +0000
@@ -775,7 +775,7 @@
$(eval $(call gen_no_archs,OOO_REPORTBUILDER_ARCHS))
OOO_FIREBIRD_ARCHS := $(filter-out m68k,$(OOO_BASE_ARCHS))
$(eval $(call gen_no_archs,OOO_FIREBIRD_ARCHS))
-OOO_NOGUI_ARCHS := $(filter amd64 i386 arm64 armhf s390x ppc64 ppc64el,$(OOO_ARCHS))
+OOO_NOGUI_ARCHS := $(filter alpha amd64 i386 arm64 armhf s390x hppa m68k powerpc ppc64 ppc64el sparc64,$(OOO_ARCHS))
$(eval $(call gen_no_archs,OOO_NOGUI_ARCHS))
OOO_PDFIUM_ARCHS := $(OOO_ARCHS)
$(eval $(call gen_no_archs,OOO_PDFIUM_ARCHS))
While this change makes sure the script is generated, the script itself still missing the
executable flag meaning that the smoketest will still fail.
Running
chmod 755 instdir/program/soffice
manually allows the smoketest to pass.
(experimental_powerpc-dchroot)rene@perotto:~/libreoffice-26.2.0~beta1$ diff -u instdir/program/soffice.old instdir/program/soffice
--- instdir/program/soffice.old 2025-12-11 01:55:33.611241288 +0000683 +0000
+++ instdir/program/soffice˙ ˙ ˙2025-12-11 06:08:10.728584
@@ -37,7 +37,7 @@on your system
˙# uncomment line below if you encounter problems starting soffice
˙# SAL_NO_XINITTHREADS=true; export SAL_NO_XINITTHREADS
-export JITC_PROCESSOR_TYPE=6
+#@JITC_PROCESSOR_TYPE_EXPORT@
˙# resolve installation directory
˙sd_cwd=$(pwd)
which is powerpc-specific, indeed. From configure.ac:
JITC_PROCESSOR_TYPE=""
if test "$_os" = "Linux" -a "$host_cpu" = "powerpc"; then
˙ ˙ # IBMs JDK needs this...
˙ ˙ JITC_PROCESSOR_TYPE=6
˙ ˙ export JITC_PROCESSOR_TYPE
fi
AC_SUBST([JITC_PROCESSOR_TYPE])
So it means hppa is something different.
Running
˙˙˙˙chmod 755 instdir/program/soffice
manually allows the smoketest to pass.
Which would also be solved by removing the JITC_PROCESSOR_TYPE thingy and relying on cp which would copy the +x instead
of relying on sed which dosn't create it +x.
Hi,
Am 11.12.25 um 17:03 schrieb John Paul Adrian Glaubitz:
On Wed, 2025-12-10 at 08:40 +0100, John Paul Adrian Glaubitz wrote:
Thus, we need to figure out why the build doesn't actually generated the wrapper scriptSo, it turns out that the wrapper script wasn't copied
for hppa, powerpc (and probably m68k) in order to fix the smokeest on these targets.
But the file is there as perotto shows.
On Thu, 2025-12-11 at 07:15 +0100, Rene Engelhard wrote:
(experimental_powerpc-dchroot)rene@perotto:~/libreoffice-26.2.0~beta1$ diff -u instdir/program/soffice.old instdir/program/sofficeWhether it sets "export JITC_PROCESSOR_TYPE=6" or not in the script shouldn't make any
--- instdir/program/soffice.old 2025-12-11 01:55:33.611241288 +0000
+++ instdir/program/soffice˙ ˙ ˙2025-12-11 06:08:10.728584683 +0000
@@ -37,7 +37,7 @@
˙# uncomment line below if you encounter problems starting soffice on your system
˙# SAL_NO_XINITTHREADS=true; export SAL_NO_XINITTHREADS
-export JITC_PROCESSOR_TYPE=6
+#@JITC_PROCESSOR_TYPE_EXPORT@
˙# resolve installation directory
˙sd_cwd=$(pwd)
which is powerpc-specific, indeed. From configure.ac:
JITC_PROCESSOR_TYPE=""
if test "$_os" = "Linux" -a "$host_cpu" = "powerpc"; then
˙ ˙ # IBMs JDK needs this...
˙ ˙ JITC_PROCESSOR_TYPE=6
˙ ˙ export JITC_PROCESSOR_TYPE
fi
AC_SUBST([JITC_PROCESSOR_TYPE])
So it means hppa is something different.
difference unless I'm missing something. This just seems to be an environment variable
that is required when using a JDK provided by IBM but should be safe to ignore otherwise.
OK, was wondering whether OpenJDK choked on it. Then the fix would be to either
a)
$ cat remove-JITC_PROCESSOR_TYPE-setting.diff
[...]
thus triggering the cp or
b)
˙ git˙diff˙desktop/CustomTarget_soffice.mk
[...]
b) is cleaner and minimal-invasive.
OK, was wondering whether OpenJDK choked on it. Then the fix would be toeither
a)AGER_DISALLOWED_FOR_BUILD@
$ cat remove-JITC_PROCESSOR_TYPE-setting.diff
diff --git a/config_host.mk.in b/config_host.mk.in
index 3452ad8fde5d..ece7d18116b5 100644
--- a/config_host.mk.in
+++ b/config_host.mk.in
@@ -390,7 +395,6 @@ export JDK=@JDK@
˙export JDK_FOR_BUILD=@JDK_FOR_BUILD@
˙export JDK_SECURITYMANAGER_DISALLOWED_FOR_BUILD=@JDK_SECURITYMAN
˙export JFREEREPORT_JAR=@JFREEREPORT_JAR@POSIX_FALLOCATE=NO])
-export JITC_PROCESSOR_TYPE=@JITC_PROCESSOR_TYPE@
˙JOM=@JOM@
˙export JQ=@JQ@
˙export JVM_ONE_PATH_CHECK=@JVM_ONE_PATH_CHECK@
diff --git a/configure.ac b/configure.ac
index c1baba596656..04d0db7bd7d3 100644
--- a/configure.ac
+++ b/configure.ac
@@ -9101,14 +9140,6 @@ AC_SUBST(LD_PLUGIN)
˙AC_CHECK_FUNCS(posix_fallocate, HAVE_POSIX_FALLOCATE=YES, [HAVE_
˙AC_SUBST(HAVE_POSIX_FALLOCATE)ce.mk
-JITC_PROCESSOR_TYPE=""
-if test "$_os" = "Linux" -a "$host_cpu" = "powerpc"; then
-˙ ˙ # IBMs JDK needs this...
-˙ ˙ JITC_PROCESSOR_TYPE=6
-˙ ˙ export JITC_PROCESSOR_TYPE
-fi
-AC_SUBST([JITC_PROCESSOR_TYPE])
- git diff desktop/CustomTarget_soffice.mk
diff --git a/desktop/CustomTarget_soffice.mk b/desktop/CustomTarget_soffi
index 26e661ec39dc..91c06870725a 100644\
--- a/desktop/CustomTarget_soffice.mk
+++ b/desktop/CustomTarget_soffice.mk
@@ -36,7 +36,7 @@ $(gb_CustomTarget_workdir)/desktop/soffice/soffice.sh :
˙ ˙ ˙ ˙ $(call gb_Output_announce,$(subst $(WORKDIR)/,,$@),$(true),SED,1)
˙ ˙ ˙ ˙ $(call gb_Trace_StartRange,$(subst $(WORKDIR)/,,$@),SED)
˙ifneq ($(JITC_PROCESSOR_TYPE),)rt JITC_PROCESSOR_TYPE=$(JITC_PROCESSOR_TYPE)/" $< > $@
-˙ ˙ ˙ ˙sed -e "s/^#@JITC_PROCESSOR_TYPE_EXPORT@/expo
+˙ ˙ ˙ ˙sed -e "s/^#@JITC_PROCESSOR_TYPE_EXPORT@/export JITC_PROCESSOR_TYPE=$(JITC_PROCESSOR_TYPE)/" $< > $@ && chmod 755 $@
˙elsece.mk
˙ ˙ ˙ ˙ cp $< $@
˙endif
˙if test $_os = "WINNT"; then
˙ ˙ ˙for i in $PKGFORMAT; do
˙ ˙ ˙ ˙ ˙if test "$i" = msi; then
diff --git a/desktop/CustomTarget_soffice.mk b/desktop/CustomTarget_soffi
index 26e661ec39dc..0c895c77afc0 100644: \
--- a/desktop/CustomTarget_soffice.mk
+++ b/desktop/CustomTarget_soffice.mk
@@ -35,11 +35,7 @@ $(gb_CustomTarget_workdir)/desktop/soffice/soffice.sh
˙ ˙ ˙ ˙ ˙| $(gb_CustomTarget_workdir)/desktop/soffice/.dir
˙ ˙ ˙$(call gb_Output_announce,$(subst $(WORKDIR)/,,$@),$(true),SED,1)
˙ ˙ ˙$(call gb_Trace_StartRange,$(subst $(WORKDIR)/,,$@),SED)
-ifneq ($(JITC_PROCESSOR_TYPE),)SSOR_TYPE=$(JITC_PROCESSOR_TYPE)/" $< > $@
-˙ ˙ sed -e "s/^#@JITC_PROCESSOR_TYPE_EXPORT@/export JITC_PROCE
-elseD)
˙ ˙ ˙cp $< $@
-endif
˙ ˙ ˙$(call gb_Trace_EndRange,$(subst $(WORKDIR)/,,$@),SE
˙endifon your system
diff --git a/desktop/scripts/soffice.sh b/desktop/scripts/soffice.sh
index 7188f393e140..1f3c4cd1f0ec 100755
--- a/desktop/scripts/soffice.sh
+++ b/desktop/scripts/soffice.sh
@@ -37,8 +37,6 @@ export SAL_ENABLE_FILE_LOCKING
˙# uncomment line below if you encounter problems starting soffice
˙# SAL_NO_XINITTHREADS=true; export SAL_NO_XINITTHREADS
-#@JITC_PROCESSOR_TYPE_EXPORT@
-
˙# resolve installation directory
˙sd_cwd=$(pwd)
˙sd_res="$0"
thus triggering the cp or
b)ce.mk
˙git diff desktop/CustomTarget_soffice.mk
diff --git a/desktop/CustomTarget_soffice.mk b/desktop/CustomTarget_soffi
index 26e661ec39dc..91c06870725a 100644\
--- a/desktop/CustomTarget_soffice.mk
+++ b/desktop/CustomTarget_soffice.mk
@@ -36,7 +36,7 @@ $(gb_CustomTarget_workdir)/desktop/soffice/soffice.sh :
˙ ˙ ˙ ˙ $(call gb_Output_announce,$(subst $(WORKDIR)/,,$@),$(true),SED,1)
˙ ˙ ˙ ˙ $(call gb_Trace_StartRange,$(subst $(WORKDIR)/,,$@),SED)
˙ifneq ($(JITC_PROCESSOR_TYPE),)rt JITC_PROCESSOR_TYPE=$(JITC_PROCESSOR_TYPE)/" $< > $@
-˙ ˙ ˙ ˙sed -e "s/^#@JITC_PROCESSOR_TYPE_EXPORT@/expo
+˙ ˙ ˙ ˙sed -e "s/^#@JITC_PROCESSOR_TYPE_EXPORT@/export JITC_PROCESSOR_TYPE=$(JITC_PROCESSOR_TYPE)/" $< > $@ && chmod 755 $@
˙else
˙ ˙ ˙ ˙ cp $< $@
˙endif
b) is cleaner and minimal-invasive.
Hello,
On Thu, 2025-12-11 at 17:45 +0100, Rene Engelhard wrote:
OK, was wondering whether OpenJDK choked on it. Then the fix would be to eitherI think it should be safe to drop the complete handling for JITC_PROCESSOR_TYPE_EXPORT.
a)
$ cat remove-JITC_PROCESSOR_TYPE-setting.diff
[...]
thus triggering the cp or
There is no JDK by IBM for 32-bit anymore, so all of this has become cruft. [...]
b) is cleaner and minimal-invasive.Yes, but we can just drop all of this. I don't think that upstream is interested in keeping this.
Am 11.12.25 um 17:53 schrieb John Paul Adrian Glaubitz:
Hello,
On Thu, 2025-12-11 at 17:45 +0100, Rene Engelhard wrote:
OK, was wondering whether OpenJDK choked on it. Then the fix would be to eitherI think it should be safe to drop the complete handling for JITC_PROCESSOR_TYPE_EXPORT.
a)
$ cat remove-JITC_PROCESSOR_TYPE-setting.diff
[...]
thus triggering the cp or
There is no JDK by IBM for 32-bit anymore, so all of this has become cruft. >> [...]
b) is cleaner and minimal-invasive.Yes, but we can just drop all of this. I don't think that upstream is interested in keeping this.
OK.
| Sysop: | Jacob Catayoc |
|---|---|
| Location: | Pasay City, Metro Manila, Philippines |
| Users: | 5 |
| Nodes: | 4 (0 / 4) |
| Uptime: | 22:23:29 |
| Calls: | 117 |
| Calls today: | 117 |
| Files: | 367 |
| D/L today: |
560 files (257M bytes) |
| Messages: | 70,893 |
| Posted today: | 26 |