yann@1: When configuring canadian cross toolchain and you're unlucky enough to be
yann@1: using a build and host that are different, but that config.sub thinks mean the same thing,
yann@1: you might end up without BUILD_CC being defined as 'cc' or 'gcc',
yann@1: which might cause $CC to be used instead, which would be wrong...
yann@1: 
yann@1: Dan Kegel
yann@1: 
yann@1: --- glibc-2.3.2/configure.old	2004-05-26 19:46:43.000000000 -0700
yann@1: +++ glibc-2.3.2/configure	2004-05-26 19:52:47.000000000 -0700
yann@1: @@ -3323,7 +3323,7 @@
yann@1:  ac_link='$CC -o conftest$ac_exeext $CFLAGS $CPPFLAGS $LDFLAGS conftest.$ac_ext $LIBS >&5'
yann@1:  ac_compiler_gnu=$ac_cv_c_compiler_gnu
yann@1:  
yann@1: -if test $host != $build; then
yann@1: +if test "$cross_compiling" = yes; then
yann@1:    for ac_prog in gcc cc
yann@1:  do
yann@1:    # Extract the first word of "$ac_prog", so it can be a program name with args.