Hello Kamaljit,
* Kamaljit Singh wrote on Fri, Jan 25, 2008 at 04:45:56PM CET:
> Couldnt it be that some option maybe added to the
> configure/environment variable that it could detect autoconf from the
> build area, too. That way we could have a linear build invocation
> where autoconf is built f
Couldnt it be that some option maybe added to the configure/environment variable
that it could detect autoconf from the build area, too. That way we could have
a linear build invocation where autoconf is built first (not yet installed) and
then
automake maybe equally happy ?
I think this should b
Hello Kamaljit,
* Kamaljit Singh wrote on Fri, Jan 25, 2008 at 01:00:52AM CET:
>
> Moreover automake1.9 is dependent on autoconf2.58+ to be present in
> the path that I cant have them in the same sandbox at all !!! I need
> to install autoconf first and then try configuring automake. That
> doesn
You missed the point.
I am trying to write a "super" configure.ac and create a sandbox that tries
to create automake and autoconf and m4. This just calls
AC_CONFIG_SUBDIRS() with the appropriate directories (automake,autoconf
and m4).
What you told me is to script this rather than use AC_CONFIG_
Kamaljit Singh wrote:
> I was hoping to create a src tree which would build automake1.9 and
automake-1.9 has been replaced with automake-1.10.1. You should use
the later version.
ftp://ftp.gnu.org/gnu/automake/automake-1.10.1.tar.gz
> autoconf2.61 and install them in a central place. Writing
Hi,
I was hoping to create a src tree which would build automake1.9 and autoconf2.61
and install them in a central place. Writing a configure.ac for this is quite
hard if
not impossible. The automake expects and depends on that the directory where
its untarred should be called automake-1.9, which
