#1062783 libxfce4ui FTCBFS: fails running gtk-doc scanner

#1062783#5
Date:
2024-02-03 09:34:12 UTC
From:
To:
libxfce4ui fails to cross build from source, because it fails running
the gtk-doc scanner with an Exec format error. This is fairly usual.
Fortunately, it also splits out its documentation to an Arch:all
package. Hence, we can disable gtk-doc in arch-only builds and thus
side-step this problem making the cross build succeed. I'm attaching a
patch for your convenience.

Helmut

#1062783#10
Date:
2024-02-05 15:40:38 UTC
From:
To:
Hi Helmut, thanks for the report and the patch.

The patch looks small, and I don't know a lot about cross-building, but would
it be better to use something like:

 ifneq (,$(filter cross,$(DEB_BUILD_PROFILES))

inside override_dh_auto_configure to only add gtk-doc when not cross-building?

Regards,

#1062783#15
Date:
2024-02-05 15:40:38 UTC
From:
To:
Hi Helmut, thanks for the report and the patch.

The patch looks small, and I don't know a lot about cross-building, but would
it be better to use something like:

 ifneq (,$(filter cross,$(DEB_BUILD_PROFILES))

inside override_dh_auto_configure to only add gtk-doc when not cross-building?

Regards,

#1062783#20
Date:
2024-02-05 19:38:40 UTC
From:
To:
Hi,

While that might technically work, such cross vs native differences are
fragile and in a lot of cases, I've had to fix them, so I strongly
prefer to not add cross vs native differences to the build unless
necessary.

Here, no part of an arch-only build needs gtk-doc. For this, it does not
matter whether the build is cross or native. It applies to any arch-only
build. In particular, disabling gtk-doc, also speeds up the build. I
actually performed an arch-only and a full build to verify that no
files go missing by this change using reproducible builds.

Is this line of reasoning convincing to you?

Helmut

#1062783#25
Date:
2024-02-06 19:41:42 UTC
From:
To:
Yes indeed, thanks for the explanation then. I'll import the diff to our
repository.

Regards,