<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN"> <HTML> <HEAD> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8"> <META NAME="GENERATOR" CONTENT="GtkHTML/3.26.0"> </HEAD> <BODY> On Thu, 2010-11-25 at 11:45 -0800, Dan Nicholson wrote: <BLOCKQUOTE TYPE=CITE> <TT>Some modules have autogen-sh="configure" specified in their definitions.</TT> <TT>This is because jhbuild will run autogen.sh rather than configure if</TT> <TT>it's available. Arguably this is a bug in the module for including</TT> <TT>autogen.sh in the tarball and/or jhbuild for preferring autogen.sh in a</TT> <TT>tarball, but this works around it for now.</TT> </BLOCKQUOTE> I agree with you, unfortunately not everyone does. A janitorial effort was started a couple of years ago to remove autogen.sh from the tarballs. I continued this effort but could not finish due to opposition. There are about 25 modules still distributing this script, and it is totally random. There is no reason for jhbuild to ever consider running this script. The build machine may not have all tools to run autoreconf (lex, yacc, whatever). It's not easy to explain and it is interpreted as a personal preference. This script is not part of the Autotools architecture, none of the GNU packages have it. The jhbuild system should definitely not attempt to run it, unless it can justify why it is required to re-create the configuration. There would be nothing wrong in giving an option to the user to decide one way or another. That's a different discussion. Gaetan </BODY> </HTML>