here's my info:
%automake --version
automake (GNU automake) 1.4-p5
<snip>
%autoconf --version
Autoconf version 2.13
%aclocal --version
aclocal (GNU automake) 1.4-p5
<snip>
aclocal runs fine.
automake has this error:
%automake
configure.ac: 9: required file `./[config.h].in' not found
conf/Makefile.am:3: invalid variable `dist_sysconf_DATA'
trying autoconf anyway produces this output:
% autoconf
autoconf: configure.in: No such file or directory
due to some sad constraints, i can't get autoconf 2.57 or higher installed
on my machine (php requires 2.13). is there any chance we can reduce the
autoconf prereq to 2.13?
dave
-----Original Message-----
From: Danny Milosavljevic [mailto:danny.milo@xxxxxxx]
Sent: Saturday, January 17, 2004 4:00 AM
To: Viner, David
Subject: RE: compiling fam
Hi,
Am Sam, den 17.01.2004 schrieb Viner, David um 01:53:
> ok... so the goal here is to run:
> aclocal
> autoconf
> automake
aclocal, then automake, then autoconf :)
[except for the very first time the project is created, but thats beside
the point :)]
>
> ./configure
> make
>
> steps 1-3 are done only by developers before release.
>
> from reading
> http://sources.redhat.com/autobook/autobook/autobook_24.html#SEC24 it
looks
> like we need a configure.in to be used by autoconf. But our cvs doesn't
> have this: http://cvs.sourceforge.net/viewcvs.py/fam/fam/
>
> so, when I run autoconf, i just get:
> >autoconf
> autoconf: configure.in: No such file or directory
Hmm, "aclocal", "automake", "autoconf" works fine here... afaik autoconf
needs either configure.ac *or* configure.in and Makefile.in to generate
the configure script.
For reference, I have aclocal 1.7.8, automake 1.7.8, autoconf 2.58
The fam stuff in cvs seems to have been generated by automake 1.6.3...
it works fine with my versions though... (checked out fam cvs, ran
aclocal-1.7, automake-1.7, autoconf-1.7, ./configure, make, and apart
from loads of "old c++" warnings, it works just fine)
So in an attempt to remember how it was:
aclocal:
input: configure.ac, m4
output: aclocal.m4
automake:
input: aclocal.m4, configure.ac, optional config.h.in
output: (loads of aux files like install-sh,...), Makefile.in
autoconf:
input: Makefile.in?, optional config.h.in
output: configure
---
configure:
input: config.h.in, Makefile.in
output: config.h, Makefile
I *think* it was like that :)
Especially the "autoconf" description part is blurry since it never made
problems so I never needed to know :)
>
> This seems bad to me. We can't regen the configure script. Is there to
> work backwards from a configure to a configure.in?
Not that I know of. configure.ac is enough either way since it is the
first step (the source).
I remember that older versions of automake used to have
configure.ac->configure.in->configure instead of
configure.ac->configure like it is now...
If you happen to have one of these, try cp configure.ac configure.in,
maybe it helps... Though I enter the world of speculation here, since I
cant remember what configure.in was at all...
and it is not created in the test cvs fam co I compiled either (which
works fine without it), so hey :)
cheers,
Danny
|