Use the dedicated function CT_DoConfigSub rather than invoking config.sub directly.
author"Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
Wed Dec 03 22:35:52 2008 +0000 (2008-12-03)
changeset 1089d35c35b77f7a
parent 1088 3c7c98b6cda9
child 1093 de1b8818d39b
Use the dedicated function CT_DoConfigSub rather than invoking config.sub directly.

/trunk/scripts/crosstool.sh | 4 2 2 0 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
scripts/crosstool.sh
     1.1 --- a/scripts/crosstool.sh	Mon Dec 01 18:01:11 2008 +0000
     1.2 +++ b/scripts/crosstool.sh	Wed Dec 03 22:35:52 2008 +0000
     1.3 @@ -303,8 +303,8 @@
     1.4      # Not only will it give us full-qualified tuples, but it will also ensure
     1.5      # that they are valid tuples (in case of typo with user-provided tuples)
     1.6      # That's way better than trying to rewrite config.sub ourselves...
     1.7 -    CT_BUILD=$(./tools/config.sub "${CT_BUILD}")
     1.8 -    CT_HOST=$(./tools/config.sub "${CT_HOST}")
     1.9 +    CT_BUILD=$(CT_DoConfigSub "${CT_BUILD}")
    1.10 +    CT_HOST=$(CT_DoConfigSub "${CT_HOST}")
    1.11  
    1.12      # Modify BUILD and HOST so that gcc always generate a cross-compiler
    1.13      # even if any of the build, host or target machines are the same.