Bugzilla Bug 232417

glib-2.16.5 fails to compile on building documentation:
touch sgml-build.stamp
gtk-doc: Building HTML
rm -rf ./html
mkdir ./html
cd ./html && gtkdoc-mkhtml --path="." glib ../glib-docs.sgml
Usage: gtkdoc-mkhtml MODULE DRIVER_FILE
make[4]: *** [html-build.stamp] Error 1
make[4]: Leaving directory
`/var/tmp/portage/dev-libs/glib-2.16.5/work/glib-2.16.5/docs/reference/glib'

$ emerge --info:
$ emerge --info
Portage 2.2_rc1 (default/linux/amd64/2008.0, gcc-4.3.1, glibc-2.8_p20080602-r0,
2.6.25-gentoo-r5-sheryl x86_64)
=================================================================
System uname:
Linux-2.6.25-gentoo-r5-sheryl-x86_64-Intel-R-_Celeron-R-_CPU_2.53GHz-with-glibc2.2.5
Timestamp of tree: Sun, 20 Jul 2008 08:45:01 +0000
ccache version 2.4 [enabled]
app-shells/bash:     3.2_p39
dev-lang/python:     2.5.2-r5
dev-util/ccache:     2.4-r7
sys-apps/baselayout: 2.0.0
sys-apps/openrc:     0.2.5
sys-apps/sandbox:    1.2.18.1-r3
sys-devel/autoconf:  2.13, 2.62-r1
sys-devel/automake:  1.4_p6, 1.5, 1.8.5-r3, 1.9.6-r2, 1.10.1-r1
sys-devel/binutils:  2.18-r3
sys-devel/gcc-config: 1.4.0-r4
sys-devel/libtool:   2.2.4
virtual/os-headers:  2.6.25-r4
ACCEPT_KEYWORDS="amd64 ~amd64"
CBUILD="x86_64-pc-linux-gnu"
CFLAGS="-march=nocona -O2 -funswitch-loops -fpredictive-commoning
-fgcse-after-reload -ftree-vectorize -fomit-frame-pointer -pipe
-fstack-protector"
CHOST="x86_64-pc-linux-gnu"
CONFIG_PROTECT="/etc"
CONFIG_PROTECT_MASK="/etc/ca-certificates.conf /etc/env.d /etc/fonts/fonts.conf
/etc/gconf /etc/gentoo-release /etc/revdep-rebuild /etc/terminfo
/etc/texmf/web2c /etc/udev/rules.d"
CXXFLAGS="-march=nocona -O2 -funswitch-loops -fpredictive-commoning
-fgcse-after-reload -ftree-vectorize -fomit-frame-pointer -pipe
-fstack-protector"
DISTDIR="/usr/portage/distfiles"
FEATURES="ccache collision-protect distlocks parallel-fetch preserve-libs
sandbox sfperms strict unmerge-orphans userfetch userpriv"
GENTOO_MIRRORS="ftp://ftp.chg.ru/pub/Linux/gentoo
http://mirror.yandex.ru//gentoo-distfiles  http://distfiles.gentoo.org
http://www.ibiblio.org/pub/Linux/distributions/gentoo"
LANG="ru_RU.UTF-8"
LC_ALL=""
LDFLAGS="-Wl,-O1"
LINGUAS="ru en"
MAKEOPTS="-j2"
PKGDIR="/usr/portage/packages"
PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress
--force --whole-file --delete --stats --timeout=180 --exclude=/distfiles
--exclude=/local --exclude=/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY="/usr/local/portage"
SYNC="rsync://rsync.europe.gentoo.org/gentoo-portage"
USE="aalib acl acpi adns amd64 apache2 bash-completion berkdb blas bluetooth
bzip2 caps cdb cli clisp cracklib crypt cscope ctype cups curl curlwrappers cxx
cyrillic djvu doc editor encode enscript examples exif expat foomaticdb fortran
ftp gdbm geoip gif ginac gmp gnutls gpgme gpm gsl hardened iconv idn imap ipv6
isdnlog javascript jpeg jpeg2k lapack latex libcaca libwww lm_sensors lzo
maildir mailwrapper mbox mhash midi mime mmap mmx mng mudflap multilib mysql
mysqli ncurses netcdf nls nntp nocd nptl nptlonly offensive openexr openmp pam
pch pcntl pcre pdf perl png pop posix ppds pppd python raw readline recode
reflection samba scanner session sharedmem slang slp smtp sockets socks5 spell
spl sse sse2 sse3 ssl syslog szip tcpd threads tiff unicode usb vim-syntax wifi
xattr xorg xpm yaz zlib" ALSA_PCM_PLUGINS="adpcm alaw asym copy dmix dshare
dsnoop empty extplug file hooks iec958 ioplug ladspa lfloat linear meter mulaw
multi null plug rate route share shm softvol" ELIBC="glibc"
INPUT_DEVICES="keyboard mouse evdev" KERNEL="linux" LCD_DEVICES="bayrad cfontz
cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses text" LINGUAS="ru en"
USERLAND="GNU"
Unset:  CPPFLAGS, CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, PORTAGE_COMPRESS,
PORTAGE_COMPRESS_FLAGS, PORTAGE_RSYNC_EXTRA_OPTS

same here

Created an attachment (id=160905) [details]
documentation build fix

The following patch fixes problem described above.

Created an attachment (id=160906) [details]
ebuild for the patch

For those waiting on a fix - until there is one committed to tree (I'm waiting
on upstream until later today before proceeding with a patch), you can simply
emerge without using the doc USE flag, because all it really does is rebuild
docs for minimal benefit. You should even have all the cross-linking to other
modules docs work fine without rebuilding the gtk-docs.

touch scan-build.stamp
gtk-doc: Rebuilding template files
cd . && gtkdoc-mktmpl --module=glib 
###Can't parse args for function guint64: *g_thread_gettime) (void

###Can't parse args for function G_LIKELY: g_atomic_pointer_get
((void*volatile*) value_location) != NULL)return FALSE;elsereturn
g_once_init_enter_impl (value_location

WARNING: No declaration found for: tm
WARNING: No declaration found for: g_test_config_vars
=============================================================================
WARNING: 3 unused declarations.
  These can be found in glib-unused.txt.
  They should be added to glib-sections.txt in the appropriate place.
=============================================================================
touch tmpl-build.stamp
gtk-doc: Building XML
cd . && \
        gtkdoc-mkdb --module=glib --source-dir=../../.. --output-format=xml
--expand-content-files="" --main-sgml-file=glib-docs.sgml --sgml-mode
--output-format=xml 
###Can't parse args for function guint64: *g_thread_gettime) (void

###Can't parse args for function G_LIKELY: g_atomic_pointer_get
((void*volatile*) value_location) != NULL)return FALSE;elsereturn
g_once_init_enter_impl (value_location

Use of uninitialized value in concatenation (.) or string at
/usr/bin/gtkdoc-mkdb line 1392, <INPUT> line 2561.
Use of uninitialized value in concatenation (.) or string at
/usr/bin/gtkdoc-mkdb line 1392, <INPUT> line 2562.
98% symbol docs coverage (1813 symbols documented, 10 symbols incomplete, 33
not documented)
See glib-undocumented.txt for a list of missing docs.
The doc coverage percentage doesn't include intro sections.
touch sgml-build.stamp
gtk-doc: Building HTML


Patch works to make the build to continue.

Is anyone working on this, or are we still waiting for upstream? I still get
the problem as of today.

I have the same problem.

Thanks for the fix. It fixed this problem on x86_64 for me.

the use flag has been removed for stabilization purpose, it will be back with
2.16.6 and 2.18.0