linux-rt-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marc Kleine-Budde <mkl@pengutronix.de>
To: Robert Schwebel <r.schwebel@pengutronix.de>
Cc: linux-rt-users@vger.kernel.org
Subject: Re: [patch 01/15] autoreconf doesnt always do the right thing, add manual variant
Date: Tue, 24 Jul 2007 22:01:51 +0200	[thread overview]
Message-ID: <46A65AAF.2090600@pengutronix.de> (raw)
In-Reply-To: <20070724182909.GI1678@pengutronix.de>

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

  reply	other threads:[~2007-07-24 20:36 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-24  9:25 [patch 00/15] fixes for rt-test build system Robert Schwebel
2007-07-24  9:25 ` [patch 01/15] autoreconf doesnt always do the right thing, add manual variant Robert Schwebel
2007-07-24 16:56   ` Darren Hart
2007-07-24 18:29     ` Robert Schwebel
2007-07-24 20:01       ` Marc Kleine-Budde [this message]
2007-07-25 15:54         ` Darren Hart
2007-07-25 20:07           ` Marc Kleine-Budde
2007-07-24  9:25 ` [patch 06/15] fix cppflags vs. cflags issues Robert Schwebel
2007-07-24 20:29   ` Darren Hart
2007-07-24  9:25 ` [patch 07/15] distribute all necessary files Robert Schwebel
2007-07-24 20:51   ` Darren Hart
2007-07-24  9:25 ` [patch 08/15] use static libs for supportlibs Robert Schwebel
2007-07-24 20:59   ` Darren Hart
2007-07-24 21:14     ` Robert Schwebel
2007-07-25 15:49       ` Darren Hart
2007-07-24  9:25 ` [patch 09/15] add a makefile for stress/pi-tests Robert Schwebel
2007-07-24 21:00   ` Darren Hart
2007-07-24  9:25 ` [patch 10/15] fixup maintainerclean Robert Schwebel
2007-07-24 21:27   ` Darren Hart
2007-07-24 23:11     ` Robert Schwebel
2007-07-25 15:47       ` Darren Hart
2007-07-24  9:25 ` [patch 11/15] periodic_cpuload_single needs support libs Robert Schwebel
2007-07-24 21:07   ` Darren Hart
2007-07-24  9:25 ` [patch 12/15] fix version and contact information Robert Schwebel
2007-07-24 21:07   ` Darren Hart
2007-07-24  9:25 ` [patch 13/15] cleanup makefile generation Robert Schwebel
2007-07-24 21:08   ` Darren Hart
2007-07-24  9:25 ` [patch 14/15] remove bogus characters from makefile Robert Schwebel
2007-07-24 21:10   ` Darren Hart
2007-07-24  9:25 ` [patch 15/15] coding style fixes Robert Schwebel
2007-07-24 21:26   ` Darren Hart
2007-07-24 23:07     ` Robert Schwebel
2007-07-24 16:52 ` [patch 00/15] fixes for rt-test build system Darren Hart
2007-07-24 17:09   ` Robert Schwebel
2007-07-24 19:14     ` Josh Triplett
2007-07-24 19:53       ` Robert Schwebel
     [not found] ` <20070724092556.384375980@metis.extern.pengutronix.de>
     [not found]   ` <200707241046.29386.dvhltc@us.ibm.com>
2007-07-24 18:22     ` [patch 05/15] remove autogenerated files Robert Schwebel

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=46A65AAF.2090600@pengutronix.de \
    --to=mkl@pengutronix.de \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=r.schwebel@pengutronix.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).