guix-patches
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[bug#71306] [PATCH gnome-team] gnu: gtk: Fix build on i686-linux.


From: Maxim Cournoyer
Subject: [bug#71306] [PATCH gnome-team] gnu: gtk: Fix build on i686-linux.
Date: Sat, 01 Jun 2024 11:04:07 -0400
User-agent: Gnus/5.13 (Gnus v5.13)

Hi Liliana,

Liliana Marie Prikler <liliana.prikler@gmail.com> writes:

> * gnu/packages/gtk.scm (gtk)[#:phases]<patch>: Add section dedicated to
> failures on i686-linux.
> ---
>  gnu/packages/gtk.scm | 15 ++++++++++++++-
>  1 file changed, 14 insertions(+), 1 deletion(-)
>
> diff --git a/gnu/packages/gtk.scm b/gnu/packages/gtk.scm
> index d5777ae67b..1c78a969f6 100644
> --- a/gnu/packages/gtk.scm
> +++ b/gnu/packages/gtk.scm
> @@ -1235,7 +1235,20 @@ (define-public gtk
>                  ;; The inscription-markup.ui fails due to /etc/machine-id
>                  ;; related warnings (see:
>                  ;; https://gitlab.gnome.org/GNOME/gtk/-/issues/5169).
> -                (("[ \t]*'inscription-markup.ui',") ""))))
> +                (("[ \t]*'inscription-markup.ui',") ""))
> +              ;; XXX: These failures appear specific to i686 – investigate 
> them.
> +              #$@(if (target-x86-32?)
> +                     #~((substitute* "testsuite/gsk/meson.build"
> +                          (("'empty-(fill|stroke)\\.node',") "")
> +                          (("'fill2?\\.node',") "")
> +                          (("'stroke\\.node',") "")
> +                          (("'fill-fractional-([a-z-]*)-nogl',") "")
> +                          (("\\[ 'path-special-cases' \\],") "")
> +                          (("\\[ '(path|curve)-special-cases' \\],") "")
> +                          (("\\[ 'path-private' \\],") ""))
> +                        (substitute* "testsuite/a11y/meson.build"
> +                           (("\\{ 'name': 'text(view)?' \\},") "")))
> +                    #~())))

Are you sure these are specific to i686 and not to 32 bit architectures
such as armhf also?

-- 
Thanks,
Maxim





reply via email to

[Prev in Thread] Current Thread [Next in Thread]