Also set CT_DEBUGROOT_DIR for non sysroot-ed toolchains.
author"Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
Tue Jun 23 22:52:13 2009 +0200 (2009-06-23)
changeset 1419634ffd14d936
parent 1418 339c8a5c9797
child 1420 0e49e6eddac4
Also set CT_DEBUGROOT_DIR for non sysroot-ed toolchains.

In the non-sysroot-ed case, the debuf-root directory would not be set;
debug tools would have been installed God-only-knows-where...

Spotted by Bart van der Meulen <bartvdrmeulen@gmail.com>.
scripts/crosstool-NG.sh.in
     1.1 --- a/scripts/crosstool-NG.sh.in	Tue Jun 23 22:52:13 2009 +0200
     1.2 +++ b/scripts/crosstool-NG.sh.in	Tue Jun 23 22:52:13 2009 +0200
     1.3 @@ -272,6 +272,7 @@
     1.4      else
     1.5          # plain old way. All libraries in prefix/target/lib
     1.6          CT_SYSROOT_DIR="${CT_PREFIX_DIR}/${CT_TARGET}"
     1.7 +        CT_DEBUGROOT_DIR="${CT_SYSROOT_DIR}"
     1.8          CT_HEADERS_DIR="${CT_SYSROOT_DIR}/include"
     1.9          # hack!  Always use --with-sysroot for binutils.
    1.10          # binutils 2.14 and later obey it, older binutils ignore it.