From mboxrd@z Thu Jan 1 00:00:00 1970 From: Marc Kleine-Budde Subject: Re: [patch 01/15] autoreconf doesnt always do the right thing, add manual variant Date: Tue, 24 Jul 2007 22:01:51 +0200 Message-ID: <46A65AAF.2090600@pengutronix.de> References: <20070724092517.390730736@metis.extern.pengutronix.de> <20070724092547.036256900@metis.extern.pengutronix.de> <200707240956.21220.dvhltc@us.ibm.com> <20070724182909.GI1678@pengutronix.de> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit Cc: linux-rt-users@vger.kernel.org To: Robert Schwebel Return-path: Received: from metis.extern.pengutronix.de ([83.236.181.26]:56158 "EHLO metis.extern.pengutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757391AbXGXUgU (ORCPT ); Tue, 24 Jul 2007 16:36:20 -0400 In-Reply-To: <20070724182909.GI1678@pengutronix.de> Sender: linux-rt-users-owner@vger.kernel.org List-Id: linux-rt-users.vger.kernel.org Hi, Robert Schwebel wrote: >>> As autoreconf doesn't always recreate all necessary files, do the steps >>> required to create everything that's needed manually. We also need >>> config/m4 in order to put the autogenerated m4 files there. >> I pretty much have to take your word on that I guess - which I'm happy to do. >> It seems in slight contradiction though to your previous statement >> encouraging us to stick to the autotools defaults for distribution so as to >> allow the tools to do their job and not accidentally miss something by doing >> it manually. Is this just a common exception to that rule? > > We recently tried to use autoreconf to build the config files from > scratch, but although it works much better than before, we've found some > problems, so let's better stay with the proven old method. Yes... > However, Marc may be able to elaborate more about the problems; he is > our autotool wizzard :) I've had problems with the old debian stable a.k.a. sarge and autoreconf with a normal autoconf/automake/libtool package. Robert had problems with autoreconf on debian testing (lenny) with a project using autoconf/automake/libtool + libltdl >>> Index: config/m4/.secret_world_domination_project >>> =================================================================== >>> --- /dev/null >>> +++ config/m4/.secret_world_domination_project >>> @@ -0,0 +1,2 @@ >>> + >>> + >> And what is this all about? :-) > > Psssst, it's secret! :) > It's just to make sure that config/m4/ is not empty, which would mean > that it would sometimes disappear. Right - with "AC_CONFIG_MACRO_DIR([config/m4])" in configure.ac we instruct autoconf to put all autogenerated suff into config/m4, to keep the root of the project clean. If you run autogen or autoreconf this directory must be existent, at least with the tool when I collected our autoconf-skeleton (about 1,5 years ago). This file ensures that this directory is present. Marc -- Dipl.-Ing. Marc Kleine-Budde | http://www.pengutronix.de Pengutronix - Linux Solutions for Science and Industry Handelsregister: Amtsgericht Hildesheim, HRA 2686 Hannoversche Str. 2, 31134 Hildesheim, Germany Phone: +49-5121-206917-0 | Fax: +49-5121-206917-9