GNOME Bugzilla – Bug 660537
Can't get past the autogen stage when building from git
Last modified: 2011-10-25 09:47:11 UTC
Created attachment 197843 [details] Output of the autogen stage When trying to build from git, I can't seem to get past the autogen stage. I'm building in a jhbuild environment by running `jhbuild shell' and running the autogen.sh script as follows: 12:01][jose@jose-desktop: /usr/src/jhbuild-sources/libgda]$ ./autogen.sh --prefix=/opt/usr-jhbuild/ --libdir=/opt/usr-jhbuild/lib --disable-static --disable-gtk-doc --with-ui 2>&1 | tee autogen-output.txt I'm attaching the autogen output.
Strange, it looks like the autogen.sh script does not run the generated configure script. Do you have the NOCONFIGURE environment variable set, and can you try running manually configure with the same arguments as for autogen.sh?
Created attachment 197916 [details] Configure output. The NOCONFIGURE variable is not set. Running configure manually seems to get farther, but it stops with: ... configure: creating ./config.status config.status: error: cannot find input file: `Makefile.in' I've attached the output.
Created attachment 199480 [details] New output of the autogen.sh script I'm reattaching the autogen.sh output because some days have gone by. When I clone from git, there's no configure script, so I use the autogen.sh script, but I do that with other modules such as glib (actually, I build glib using jhbuild, but I think that's what jhbuild does). I really have no idea what could be causing this, but I'd like to get past the error so I can build libgdamm from git and then add a few things to libgda-uimm which depends on it.
For the last few months, I, and some others, have had to do "touch config.rpath" before running autogen.sh in libgda from git. Does that fix this for you? I don't know if it is triggered by a change in jhbuild or in libgda.
For some reason, the file does not exist for me. The autogen stage gets as far as reported. I then try running configure which stops as reported. I just don't see a config.rpath file in libgda.
That's my point. You need to "touch config.rpath" to make configure work. Your output shows this: configure.ac:654: required file `./config.rpath' not found I wish I knew how to avoid this.
Created attachment 199908 [details] [review] touch fongi.rpath in autogen.sh This is caused by the MDB configure check (in m4/mdbtools.m4, line 235) using AM_ICONV. This is a gettext macro, which depends on other gettext macros, including one that requires config.rpath to be present. This file is normally created by autopoint, which is run by gettextize. As intltool is used (IT_PROG_INTLTOOL in configure.ac, line 60), rather than gettext directly, gettextize is not run during autogen.sh, but intltoolize is. This triggers a gettext bug: http://lists.gnu.org/archive/html/bug-gettext/2011-10/msg00012.html The solution is often to either include config.rpath in the git repository, or to create an empty config.rpath in autogen.sh (this is what the attached patch does). It is not possible to use gettext and intltool together, as that is unsupported: https://bugs.launchpad.net/intltool/+bug/654918 Copying (and modifying appropriately) the AM_ICONV macro into libgda would also work to solve the problem.
Thanks. But that line in autogen.sh would need a comment, even if it just points to here.
Created attachment 199910 [details] [review] create config.rpath in autogen.sh, with comment (In reply to comment #8) > Thanks. But that line in autogen.sh would need a comment, even if it just > points to here. It does not need a comment (as it fixes the bug without one), but if you want a comment, then you will like the updated patch.
I do like comments rather than cryptic incantations, yes. Please push.
(In reply to comment #10) > I do like comments rather than cryptic incantations, yes. Next time I will make sure to remove the cryptic incantation. ;) > Please push. Pushed to master as commit c63e9499694627ea43b0f98a87b49fe2519c5bbd.