Build error 2.3 on Ubuntu lucid beta

[Derek Atkins]

Hi,

Please remember to CC to list on all replies..

Colin Law <clanlaw at googlemail.com> writes:

> On 25 March 2010 18:08, Derek Atkins <warlord at mit.edu> wrote:
>> Colin Law <clanlaw at googlemail.com> writes:
>>
>>> On 25 March 2010 15:31, John Ralls <jralls at ceridwen.us> wrote:
>>>>..
>>>> You need to run autogen.sh if a Makefile.am is changed. Autogen runs automake which makes Makefile.in from Makefile.am; configure uses Makefile.in, not Makefile.am, for input to create Makefile.
>>>
>>> Would it be possible to have a top level make that ran autogen and
>>> configure when appropriate?  One would have to provide the params for
>>> configure somehow of course.
>>
>> Generally the auto-tools will re-run it for you in maintainer mode.
>> I honestly don't know why it didn't re-run for you.  It certainly does
>> it for me on Linux.
>
> Sorry I don't know what you mean by that, could you explain in more
> detail?  I can't see how configure can run automatically at the moment
> as you have to supply parameters.

No, you don't.  config.status knows how you called configure.  C.f.:

  ./config.status --version

The auto tools are set up such that it should notice that the
Makefile.am is newer than the Makefile.in and rerun automake, or that
the configure.in is newer than configure and rerun autoconf.  It's
supposed to all just work (and it works just fine for me here on Linux).

In the case of rerunning configure, it just calls ./config.status --recheck

> Colin

-derek
-- 
       Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
       Member, MIT Student Information Processing Board  (SIPB)
       URL: http://web.mit.edu/warlord/    PP-ASEL-IA     N1NWH
       warlord at MIT.EDU                        PGP key available