Source: webkit2gtk
Version: 2.40.4-1
Severity: normal
Tags: patch
User: debian-ia64@lists.debian.org
Usertags: ia64
X-Debbugs-Cc: debian-ia64@lists.debian.org

Hi!

On ia64, webkit2gtk FTBFS due to g-ir-scanner not understading the syntax used
in the <sys/uncontext.h> header [1]:

/usr/include/ia64-linux-gnu/sys/ucontext.h:92: syntax error, unexpected 
typedef-name in '     \
unsigned long _pad[__builtin_offsetof (mcontext_t, sc_gr[0])/8];' at 
'mcontext_t'
/usr/include/ia64-linux-gnu/sys/ucontext.h:94: syntax error, unexpected '}' in 
'   }' at '}'

To work around this, webkit2gtk should be built with introspection disabled:

--- old/webkit2gtk-2.40.4/debian/rules  2023-07-06 11:51:25.000000000 +0200
+++ new/webkit2gtk-2.40.4/debian/rules  2023-07-29 10:35:19.934123170 +0200
@@ -55,6 +55,11 @@
        EXTRA_CMAKE_ARGUMENTS += -DENABLE_WEBGL=OFF
 endif
 
+# https://gitlab.gnome.org/GNOME/gobject-introspection/-/issues/471
+ifneq (,$(filter $(DEB_HOST_ARCH),ia64))
+       EXTRA_CMAKE_ARGUMENTS += -DENABLE_INTROSPECTION=OFF
+endif
+
 # libgbm-dev is not available in the Hurd (#1033999)
 ifneq (,$(filter $(DEB_HOST_ARCH),hurd-i386))
        EXTRA_CMAKE_ARGUMENTS += -DUSE_GBM=OFF

Can you apply this change for the next upload of webkit2gtk?

Thanks,
Adrian

[1] https://gitlab.gnome.org/GNOME/gobject-introspection/-/issues/471

--
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer
`. `'   Physicist
  `-    GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913
--- old/webkit2gtk-2.40.4/debian/rules  2023-07-06 11:51:25.000000000 +0200
+++ new/webkit2gtk-2.40.4/debian/rules  2023-07-29 10:35:19.934123170 +0200
@@ -55,6 +55,11 @@
        EXTRA_CMAKE_ARGUMENTS += -DENABLE_WEBGL=OFF
 endif
 
+# https://gitlab.gnome.org/GNOME/gobject-introspection/-/issues/471
+ifneq (,$(filter $(DEB_HOST_ARCH),ia64))
+       EXTRA_CMAKE_ARGUMENTS += -DENABLE_INTROSPECTION=OFF
+endif
+
 # libgbm-dev is not available in the Hurd (#1033999)
 ifneq (,$(filter $(DEB_HOST_ARCH),hurd-i386))
        EXTRA_CMAKE_ARGUMENTS += -DUSE_GBM=OFF

Reply via email to