Julian Foad writes:
> "Curtis L. Olson" wrote:
> >
> > These are actually harmless error messages for lines that aren't even
> > executed by your version of automake, but the error checker isn't as
> > smart as it could be and doesn't know about automake conditionals.
>
> Are you referring to th
Alexander Kappes wrote:
>
> Thanks for the information Julian. Yes, I removed the old config.cache
> file.
>
> Did I get this right, the only way to make it work again is reverting to
> the old version?
The old version of the auto-tools will probably work, but I don't know for sure. And
I don
"Curtis L. Olson" wrote:
>
> These are actually harmless error messages for lines that aren't even
> executed by your version of automake, but the error checker isn't as
> smart as it could be and doesn't know about automake conditionals.
Are you referring to this message (running automake):
Alexander,
It's ok to be seeing this error messages about = vs +=. They are
annoying, but harmless.
Curt.
Alexander Kappes writes:
>
> Thanks for the information Julian. Yes, I removed the old config.cache
> file.
>
> Did I get this right, the only way to make it work again is reverting to
Thanks for the information Julian. Yes, I removed the old config.cache
file.
Did I get this right, the only way to make it work again is reverting to
the old version?
Cheers Alexander
On Fri, 19 Apr 2002, Julian Foad wrote:
> configure.in includes a fix to make it work with both versions of t
Julian Foad writes:
> configure.in includes a fix to make it work with both versions of
> the auto-tools:
>
> if OLD_AUTOMAKE
> INCLUDES += -I$(top_srcdir)
> else
> INCLUDES = -I$(top_srcdir)
> endif
>
> But
> (1) If "=" is good enough in the new version, isn't it good enough
> in both versions
Julian Foad writes:
> This is what you get if the wrong version of automake/autoconf is used.
>Unfortunately the old and new versions are not compatible. SimGear needs the old
>version. The automake/autoconf supplied with CygWin automatically detects which
>version to use, and it might be po
configure.in includes a fix to make it work with both versions of the auto-tools:
if OLD_AUTOMAKE
INCLUDES += -I$(top_srcdir)
else
INCLUDES = -I$(top_srcdir)
endif
But
(1) If "=" is good enough in the new version, isn't it good enough in both versions?
(Not necessarily: maybe the meaning has c
This is what you get if the wrong version of automake/autoconf is used. Unfortunately
the old and new versions are not compatible. SimGear needs the old version. The
automake/autoconf supplied with CygWin automatically detects which version to use, and
it might be possible to get these auto-
I recently upgraded from SuSE 7.2 to 8.0 and since then I get strange
error messages when I try to run autogen for SimGear (and also
FlightGear):
---
Host info: Linux i686
automake: 1.5 (15)
Running aclocal
Running autoheader
10 matches
Mail list logo