Le 02/08/2022 à 11:27, Dmitry Smirnov a écrit :
Hi Ludovic,
On Sunday, 31 July 2022 12:36:04 AM AEST Ludovic Rousseau wrote:
I am the Debian maintainer of the package grisbi that depends on
libgoffice-0.10-10
I see no update on this bug since 3 weeks.
It looks like the fix is proposed upstream at
https://gitlab.gnome.org/GNOME/goffice/-/issues/59#note_1495045
Sorry, I'm being very slow lately...
I've applied the upstream patch but unfortunately it did not fix the
problem...
I think we now have a *different* issue.
The initial build failure
https://buildd.debian.org/status/fetch.php?pkg=goffice&arch=mips64el&ver=0.10.52-2&stamp=1656999642&raw=0
was during execution of dh_auto_build command:
/usr/bin/ld: .libs/goffice-0.10-scan.o: in function `get_object_types':
./docs/reference/goffice-0.10-scan.c:207: undefined reference to
`go_complexl_get_type'
/usr/bin/ld: ./docs/reference/goffice-0.10-scan.c:207: undefined reference to
`go_complexl_get_type'
collect2: error: ld returned 1 exit status
2022-07-05 05:40:30,271:scangobj.py:execute_command:1289:WARNING:Linking scanner failed: 1,
command: /bin/bash ../../libtool --tag=CC --mode=link mips64el-linux-gnuabi64-gcc
-lgobject-2.0 -lglib-2.0 -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=.
-fstack-protector-strong -Wformat -Werror=format-security -Wall -g -Wall -Werror=init-self
-Werror=missing-include-dirs -Wsign-compare -Werror=pointer-arith -Wchar-subscripts
-Wwrite-strings -Wdeclaration-after-statement -Wnested-externs -Wmissing-noreturn
-Werror=missing-prototypes -Werror=implicit-function-declaration -Wmissing-declarations
-Wno-pointer-sign -Werror=format-security -Wstrict-prototypes -Wno-error=format-nonliteral
-Wl,-z,relro -Wl,-z,now -Wl,-z,defs -Wl,-O1 -Wl,--as-needed -L/usr/X11R6/lib
goffice-0.10-scan.lo ../../goffice/libgoffice-0.10.la -Wl,--export-dynamic -lgmodule-2.0
-pthread -lgsf-1 -lrsvg-2 -lm -lxslt -lxml2 -lgtk-3 -lgdk-3 -lpangocairo-1.0 -lpango-1.0
-lharfbuzz -latk-1.0 -lcairo-gobject -lcairo -lgdk_pixbuf-2.0 -lgio-2.0 -lgobject-2.0
-lglib-2.0 -Wl,-z,relro -Wl,-z,now -Wl,-z,defs -Wl,-O1 -Wl,--as-needed -L/usr/X11R6/lib -o
goffice-0.10-scan
make[3]: *** [Makefile:695: scan-build.stamp] Error 1
make[3]: Leaving directory '/<<PKGBUILDDIR>>/docs/reference'
make[2]: *** [Makefile:438: all-recursive] Error 1
make[2]: Leaving directory '/<<PKGBUILDDIR>>/docs'
make[1]: *** [Makefile:552: all-recursive] Error 1
make[1]: Leaving directory '/<<PKGBUILDDIR>>'
dh_auto_build: error: make -j4 returned exit code 2
make: *** [debian/rules:70: binary-arch] Error 25
dpkg-buildpackage: error: debian/rules binary-arch subprocess returned exit
status 2
With the new upstream patch the build failure is during ecxecution of
dpkg-gensymbols command:
dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols
file: see diff output below
dpkg-gensymbols: warning: debian/libgoffice-0.10-10/DEBIAN/symbols doesn't
match completely debian/libgoffice-0.10-10.symbols
--- debian/libgoffice-0.10-10.symbols (libgoffice-0.10-10_0.10.52-3_mips64el)
+++ dpkg-gensymbolsz0mJDF 2022-08-02 08:51:19.169391884 +0000
@@ -60,22 +60,22 @@
go__VOID__INT_BOOLEAN_BOOLEAN_BOOLEAN@Base 0.9.0
go_accumulator_add@Base 0.9.0
go_accumulator_add_quad@Base 0.9.1
- go_accumulator_add_quadl@Base 0.9.1
- go_accumulator_addl@Base 0.9.0
+#MISSING: 0.10.52-3# go_accumulator_add_quadl@Base 0.9.1
+#MISSING: 0.10.52-3# go_accumulator_addl@Base 0.9.0
go_accumulator_clear@Base 0.9.0
- go_accumulator_clearl@Base 0.9.0
+#MISSING: 0.10.52-3# go_accumulator_clearl@Base 0.9.0
[...]
Some symbols, ending with "l", were previously defined but are no more present.
From the header file
https://gitlab.gnome.org/GNOME/goffice/-/blob/master/goffice/math/go-accumulator.h#L29
we see that the symbol go_accumulator_addl() is defined only if
GOFFICE_WITH_LONG_DOUBLE is defined.
But in debian/rules we still have "--without-long-double" option for mips64el.
I think that is the source of the new problem.
Have you tried to *revert*
https://salsa.debian.org/debian/goffice/-/commit/3cd973d85f5b6d337100270e068f09fd30d8cea5
and keep only the new upstream patch?
Hope this helps.
--
Dr. Ludovic Rousseau
