crosstool-ng/config/companion_tools/m4.in
Alexey Neyman 7a94c81e5b Rework configure logic wrt GNU autotools
Rather than requiring them of a certain version, detect if they are present
(and have sufficient version) and select an appropriate companion tool
otherwise. The reason is that, for example, most recent gettext requires
automake 1.15, but the newest available CentOS has 1.13. Hence, the option
to "upgrade your system" does not apply, and the warning comment above
the companion tools is rather scary.

With this approach, it will work out of the box - either by using the host's
tools, or by building them as needed. Note that the user can still change
the setting in the config.

While there, propagate the new version checking macro to awk/bash/host binutils,
and switch from --with-foo=xxx to officially blessed FOO=xxx: the latter
does not require checking for bogus values (i.e., --with-foo, --without-foo)
and AC_PROG_* macros recognize the corresponding settings without further
modifications. For now, I kept --with-foo=, if only to complain and steer
people to the new way. To be cleaned up after a release.

Signed-off-by: Alexey Neyman <stilor@att.net>
2017-01-27 20:40:47 -08:00

35 lines
595 B
Plaintext

# GNU m4
## default y if !CONFIGURE_has_gnu_m4_1_4_12_or_newer
## help GNU m4
choice
bool
prompt "m4 version"
# Don't remove next line
# CT_INSERT_VERSION_BELOW
config M4_V_1_4_18
bool
prompt "1.4.18"
config M4_V_1_4_17
bool
prompt "1.4.17 (OBSOLETE)"
depends on OBSOLETE
config M4_V_1_4_13
bool
prompt "1.4.13 (OBSOLETE)"
depends on OBSOLETE
endchoice
config M4_VERSION
string
# Don't remove next line
# CT_INSERT_VERSION_STRING_BELOW
default "1.4.18" if M4_V_1_4_18
default "1.4.17" if M4_V_1_4_17
default "1.4.13" if M4_V_1_4_13