Opened 15 years ago

Closed 15 years ago

Last modified 13 years ago

#2828 closed task (fixed)

GTK-doc needs gnome-doc-utils

Reported by: willimm Owned by: ken@…
Priority: normal Milestone:
Component: BOOK Version: SVN
Severity: normal Keywords:
Cc:

Description

When trying to run GTK-Doc with all the deps listed in the book, configure errors out, saying it needs gnome-doc-utils to contuine.

To prove this is a regression in 6.4, here is the output of configure:

checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether to enable maintainer-specific portions of Makefiles... no
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
configure: error: gnome-doc-utils >= 0.3.2 not found

This should be adressed in the book.

Change History (5)

comment:1 by ken@…, 15 years ago

Owner: changed from blfs-book@… to ken@…
Status: newassigned

comment:2 by ken@…, 15 years ago

Odd, my log is quite different at this point.

checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether to enable maintainer-specific portions of Makefiles... no
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for style of include used by make... GNU
checking for gcc... gcc
checking for C compiler default output file name... a.out

Strange. In what you pasted, the error message is not associated with any 'checking' message. In my log, there is no reference to gnome-doc-utils. The only not-immediately-obvious test I can see in the log is for TEST_DEPS almost at the end, which the configure script shows as glib-2.0 and gobject-2.0 both >= 2.6.0. BUT, I can confirm the problem.

Further examination of the configure script shows the test which gave you this result, at line 2626. I didn't spot it because the configure script is unusual for (at least) this one test: ther is NO preliminary message about what it is testing, and if the test passes it does so in silence and nobody is any the wiser about the requirement. Please report this to upstream (I'm sure they would appreciate a patch to fix configure and configure.in).

Thanks for this report.

comment:3 by ken@…, 15 years ago

Resolution: fixed
Status: assignedclosed

Fixed in r7753.

comment:5 by (none), 13 years ago

Milestone: 6.4

Milestone 6.4 deleted

Note: See TracTickets for help on using tickets.