Brett I. Holcomb wrote:
This brings up a question. Is this the best way to do this - simply put
WANT_AUTOMAKE="1.7" in my build script or is there a better way to fix it.
I would guess it is the best way - don't know exactly, though.
But the other options that would come to my mind for a workaround
would involve using at least two different autotools versions during
packaging - one configuration set for "old" autotools and one for
the new stuff. Not really a good way ...
Actually two questions <G> - what makes autogen so touch about versions
and what does it take to fix it?
I think, so far it doesn't really "fix" it, it's just that new
versions address design issues, particularly with the usage of
m4 macros etc. (like different macros using identical names) -
that's also the reason why you'd usually receive many "warnings"
when using a current autotools package with scripts that were
generated by older versions (and macro sets) - e.g. you get to
read numerous lines with stuff like
"Warning: underquoted definition of..."
So, what the autotools people finally want to achieve is to
unclutter all this stuff, without having colliding namespaces
anymore - but that takes of course some time.
The whole issue is quite frequently brought up on different
mailing lists, so maybe one could find some clarifying information
on the autotools webpage - or in the autotools online book
(http://sources.redhat.com/autobook/)
good luck
--------
Boris
_______________________________________________
Flightgear-users mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-users
2f585eeea02e2c79d7b1d8c4963bae2d
