With libgnome-java-2.8.2-r1 there are two build problems: 1) If Gtk+ 1.2 is not installed? aclocal mysteriously complains "configure.in: 40: macro `AM_PATH_GTK' not found in library". "Fixed" that by adding some empty definition of AM_PATH_GTK to /usr/share/libgtk-java-2.4/macros/jg_common.m4: "AC_DEFUN([AM_PATH_GTK],[])" 2) As "/usr/bin/autoconf" defaults to version 2.13 the "autogen.sh" script fails, as long as "WANT_AUTOCONF=2.5" is not set. Reproducible: Always Steps to Reproduce:
1) Gtk 1.2 ?!?. Whoa. Erum, alright. Oh, I see what you're getting at. You're saying that autoconf macro is only supplied by gtk+ 1.2 . Ok, yeah, on my system, I only get that macro from /usr/share/aclocal/gtk.m4, which is provided by gtk+1.2.10. I'd say this seems like a problem that needs fixing upstream as well, but its easily enough patched. 2) Yeah? How about that. Hm. autoconf 2.12 is ~ masked, and I certainly didn't have it on any of my systems. I'll also discuss this with upstream. I assume this means the package needs to depend >= on a specific version of autoconf? Would you mind pasting the error you got in here so I can show it to others? I can fix it, but I'm curious what other distros are running into and whether or not this is a more widespread problem. Cheers, AfC Sydney
The (2) part is resolved in java-gnome 2.10 (ie, libgtk-java-2.6.1.1) as we no longer run autoconf or re-automake in order to do the build. Looking ahead, the macros are going to be concentrated in a new package, perhaps java-gnome-common, during the 2.11 development cycle. Mathias, when you bring 2.6.1.1 in, do you still run into the same problem? If not, we can close this. AfC Toronto
