Hi.
I cannot create configure with autoconf 2.59, error:
configure.in:362: warning: AC_CANONICAL_HOST invoked multiple times
autoconf/specific.m4:363: AC_CYGWIN is expanded from...
configure.in:362: the top level
configure.in:44: error: possibly undefined macro: AC_MSG_ERROR
If this token and others are legitimate, please use m4_pattern_allow.
See the Autoconf documentation.
The reason I need to create configure is that macro
LOC_CHECK_VERSION_INT fails on crosscompiler,
patch is attached.
On Wed, Sep 20, 2006 at 07:03:44PM +0200, Radim Blazek wrote:
Hi.
I cannot create configure with autoconf 2.59, error:
configure.in:362: warning: AC_CANONICAL_HOST invoked multiple times
autoconf/specific.m4:363: AC_CYGWIN is expanded from...
configure.in:362: the top level
configure.in:44: error: possibly undefined macro: AC_MSG_ERROR
If this token and others are legitimate, please use m4_pattern_allow.
See the Autoconf documentation.
hi Radim,
so far I always used autoconf-2.13 (which still works).
Could you try that version as well? Or do you eed to
use 2.59?
Markus
The reason I need to create configure is that macro
LOC_CHECK_VERSION_INT fails on crosscompiler,
patch is attached.
--
Markus Neteler <neteler itc it> http://mpa.itc.it/markus/
ITC-irst - Centro per la Ricerca Scientifica e Tecnologica
MPBA - Predictive Models for Biol. & Environ. Data Analysis
Via Sommarive, 18 - 38050 Povo (Trento), Italy
On 9/20/06, Markus Neteler <neteler@itc.it> wrote:
On Wed, Sep 20, 2006 at 07:03:44PM +0200, Radim Blazek wrote:
> Hi.
> I cannot create configure with autoconf 2.59, error:
>
> configure.in:362: warning: AC_CANONICAL_HOST invoked multiple times
> autoconf/specific.m4:363: AC_CYGWIN is expanded from...
> configure.in:362: the top level
> configure.in:44: error: possibly undefined macro: AC_MSG_ERROR
> If this token and others are legitimate, please use m4_pattern_allow.
> See the Autoconf documentation.
hi Radim,
so far I always used autoconf-2.13 (which still works).
Could you try that version as well? Or do you eed to
use 2.59?
Yes, I forgot that it must be 2.13.
Radim
Markus
> The reason I need to create configure is that macro
> LOC_CHECK_VERSION_INT fails on crosscompiler,
> patch is attached.
>
> Radim
--
Markus Neteler <neteler itc it> http://mpa.itc.it/markus/
ITC-irst - Centro per la Ricerca Scientifica e Tecnologica
MPBA - Predictive Models for Biol. & Environ. Data Analysis
Via Sommarive, 18 - 38050 Povo (Trento), Italy
I was trying to emerge GRASS 6.1.0 and 6.2.0 on my freshly installed
Gentoo ~x86 box, but it stopped on following error:
***** autoconf *****
configure.in:44: error: possibly undefined macro: AC_MSG_ERROR
If this token and others are legitimate, please use m4_pattern_allow.
See the Autoconf documentation.
As Radim also had following problem, I wan to ask:
1) is autoconf-2.1x required to compile GRASS and autoconf-2.61
currently banned?
2) if it is fixed in 6.3, is possible to backport this fix before 6.2.1 release?
3) is easy to fix this autoconf problem? I mean like changing one line
in configure from ebuild, if it is not fixed before 6.2.1 release.
You may ask - why I use autoconf-2.61? My answer - it's just default
on my Gentoo system
WBR,
Maris.
2006/9/22, Radim Blazek <radim.blazek@gmail.com>:
On 9/20/06, Markus Neteler <neteler@itc.it> wrote:
> On Wed, Sep 20, 2006 at 07:03:44PM +0200, Radim Blazek wrote:
> > Hi.
> > I cannot create configure with autoconf 2.59, error:
> >
> > configure.in:362: warning: AC_CANONICAL_HOST invoked multiple times
> > autoconf/specific.m4:363: AC_CYGWIN is expanded from...
> > configure.in:362: the top level
> > configure.in:44: error: possibly undefined macro: AC_MSG_ERROR
> > If this token and others are legitimate, please use
m4_pattern_allow.
> > See the Autoconf documentation.
>
> hi Radim,
>
> so far I always used autoconf-2.13 (which still works).
> Could you try that version as well? Or do you eed to
> use 2.59?
Yes, I forgot that it must be 2.13.
Radim
>
> Markus
>
> > The reason I need to create configure is that macro
> > LOC_CHECK_VERSION_INT fails on crosscompiler,
> > patch is attached.
> >
> > Radim
>
> > _______________________________________________
> > grass-dev mailing list
> > grass-dev@grass.itc.it
> > http://grass.itc.it/mailman/listinfo/grass-dev
>
> --
> Markus Neteler <neteler itc it> http://mpa.itc.it/markus/
> ITC-irst - Centro per la Ricerca Scientifica e Tecnologica
> MPBA - Predictive Models for Biol. & Environ. Data Analysis
> Via Sommarive, 18 - 38050 Povo (Trento), Italy
>
> _______________________________________________
> grass-dev mailing list
> grass-dev@grass.itc.it
> http://grass.itc.it/mailman/listinfo/grass-dev
>
I was trying to emerge GRASS 6.1.0 and 6.2.0 on my freshly installed
Gentoo ~x86 box, but it stopped on following error:
***** autoconf *****
configure.in:44: error: possibly undefined macro: AC_MSG_ERROR
If this token and others are legitimate, please use m4_pattern_allow.
See the Autoconf documentation.
As Radim also had following problem, I wan to ask:
1) is autoconf-2.1x required to compile GRASS and autoconf-2.61
currently banned?
GRASS' configure.in script assumes 2.13. However, we keep the
generated configure script in CVS, so you don't need to run autoconf
as part of the build process. You only need to run autoconf if you
modify the configure.in script, in which case you need to use 2.13.
2) if it is fixed in 6.3, is possible to backport this fix before 6.2.1 release?
3) is easy to fix this autoconf problem? I mean like changing one line
in configure from ebuild, if it is not fixed before 6.2.1 release.
You may ask - why I use autoconf-2.61? My answer - it's just default
on my Gentoo system
On Gentoo, the auto* commands are symlinks to ac-wrapper.sh. This uses
$WANT_AUTOCONF to determine which version to use. If it's unset, if
configure already exists and was built with 2.13 then it uses 2.13,
otherwise it defaults to a newer version.
