GNOME Bugzilla – Bug 107984
make atk HEAD branch use automake 1.7
Last modified: 2004-12-22 21:47:04 UTC
Attached is a patch to make ATK use automake-1.7 (to go along with the glib and pango patches already posted).
Created attachment 14889 [details] [review] Use automake 1.7
I have been trying out this patch without success so far: After updating my version of autoconf and automake I have found that the latest relerase of gtk-doc (1.0) does not seem to work as it does not contain gtkdocize. After getting gtk-doc from CVS HEAD my configure command fails looking for XML catalog. It seems to be looking for /etc/xml/catalog which does not exist on my Solaris system. What location can I specify for the XML catalog. I have tried /opt/gnome-2.0/share/xml without success.
These are the steps markmc used to set up the XML catalog on his machine: How about adding steps like: 1) download http://www.oasis-open.org/docbook/xml/4.1.2/docbkx412.zip 2) install it in /usr/share/sgml/docbook/xml-dtd-4.1.2 3) Download docbook-xsl from docbook.sf.net and install it in /usr/share/sgml 4) download and run http://xmlsoft.org/buildDocBookCatalog I'll add some docs to gtk-doc's README.
I think I now have an XML catalog set up correctly on my system. At least I have moved on to other errors: autogen.sh --prefix=/opt/gnome-2.0 aclocal: configure.in: 97: macro `AM_DISABLE_STATIC' not found in library aclocal: configure.in: 99: macro `AM_PROG_LIBTOOL' not found in library These macros are defined in aclocal.m4 but aclocal-1.7 call in autogen.sh does not seem to be picking them up. aclocal-1.7 -I /opt/gnome-2.0/share/aclocal This seems to be different behaviour that occurs with aclocal-1.4. I get the same error messages when I try to build pango from CVS HEAD.
aclocal from automake 1.7 should act the same as 1.4. When generating aclocal.m4, it will get macros from any directories passed on the command line with -I arguments, and its builtin directory, which can be found by running "aclocal-1.7 --print-ac-dir". If you have installed automake 1.4 and 1.7 in different prefixes, you would have different macro search paths, which might account for the difference.
Thanks. My problem was that I had installed automake-1.7 in a different location to automake-1.4 so the builtin directory was different. Once I sorted that out autogen.sh ran to completion.
I have noticed that after doing a make clean in the docs directory a make command does not make anything. Is this the expected behavior? How should the documentation be generated?
I needed to set PKG_CONFIG_PATH so that gtk-doc is found by pkg-config. I have committed the patch.