2010-01-12 20:09:30 +00:00
|
|
|
# Companion tools config options
|
|
|
|
|
|
|
|
|
|
menu "Companion tools"
|
|
|
|
|
|
2016-11-29 00:55:22 +00:00
|
|
|
config COMP_TOOLS_FOR_HOST
|
|
|
|
|
bool
|
|
|
|
|
prompt "Install companion tools for host"
|
|
|
|
|
help
|
|
|
|
|
Enable this option if you want to include the selected companion
|
|
|
|
|
tools into the final toolchain (rather than just using them
|
|
|
|
|
to build it).
|
|
|
|
|
|
Give companion tools some love.
Allow selection of make/m4/... version. Support imports of new versions
via addToolVersion.sh. Import newest versions of the companion tools.
One non-trivial change is the handling of make versions. Existing code
was not handling make companion tool as described (see the previous
commit). However, since most modern systems have make 4.x, that previous
commit made crosstool-ng always build make as a companion tool.
This traces back to the commit dd15c93 from 2014. That commit's log message
says that actually it was 3.81 which broke the build for certain component
(it was originally breaking eglibc, but I noticed it was breaking current
glibc on powerpc64), and introduced an option to force using 3.81 by
"components that really need it". It looks like in 2.5 years we haven't
seen any such components that really need make 3.81, and (given that make
has already had a few releases since 3.81) we're unlikely to see them
in the future.
Hence, the configure check is changed from "exactly 3.81" to "3.81 or newer".
In its current form, configure will accept make 3.80+, and will not require
make as a companion tool for 3.81+. We might want to bump the latter check
to even newer version given the claim from dd15c93. Killed
COMP_TOOLS_make_3_81_NEEDED.
Anyway, I retained 3.81 just in case; ditto for m4 1.14.3, autoconf 2.65
and automake 1.11.1.
Signed-off-by: Alexey Neyman <stilor@att.net>
2016-11-21 20:09:54 +00:00
|
|
|
source "config.gen/companion_tools.in"
|
2010-01-12 20:09:30 +00:00
|
|
|
|
|
|
|
|
endmenu
|
