Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.bugs.dist > #1222861 > unrolled thread

Bug#1089122: udisks2 FTCBFS: gtk-doc scanner fails

Started byHelmut Grohne <helmut@subdivi.de>
First post2024-12-05 22:30 +0100
Last post2024-12-05 22:30 +0100
Articles 1 — 1 participant

Back to article view | Back to linux.debian.bugs.dist


Contents

  Bug#1089122: udisks2 FTCBFS: gtk-doc scanner fails Helmut Grohne <helmut@subdivi.de> - 2024-12-05 22:30 +0100

#1222861 — Bug#1089122: udisks2 FTCBFS: gtk-doc scanner fails

FromHelmut Grohne <helmut@subdivi.de>
Date2024-12-05 22:30 +0100
SubjectBug#1089122: udisks2 FTCBFS: gtk-doc scanner fails
Message-ID<JQrA5-e04Z-13@gated-at.bofh.it>

[Multipart message — attachments visible in raw view] — view raw

Source: udisks2
Version: 2.10.1-11
Tags: patch
User: debian-cross@lists.debian.org
Usertags: ftcbfs

udisks2 fails to cross build from source, because running the gtk-doc
scanner fails. This is a common problem and the solution usually is not
to run it as the documentation usually resides in an arch:all package
and we actually don't have to generate it during an arch-only build.
This is mostly implemented in udisks2 via the nodoc build profile
already and a cross build specifying nodoc actually works. So rather
than making this conditional on the nodoc build profile, I recommend
skipping gtk-doc in arch-only builds. As a result a nodoc build simply
becomes an arch-only build and the build profile becomes redundant. The
attached patch takes the liberty to simply discard the now unused
profile. I hope you like it, but if you prefer keeping the profile,
that's fine as well.

Helmut

[toc] | [standalone]


Back to top | Article view | linux.debian.bugs.dist


csiph-web