Also set CT_DEBUGROOT_DIR for non sysroot-ed toolchains. 1.4
author"Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
Tue Jun 23 22:52:13 2009 +0200 (2009-06-23)
branch1.4
changeset 1453bfdcc6076d3b
parent 1452 0c021c8900cc
child 1454 5e3ec8c347d6
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>.
(transplanted from 634ffd14d936154464fd714ed29ed44c8e16ae02)
scripts/crosstool-NG.sh.in
     1.1 --- a/scripts/crosstool-NG.sh.in	Wed Jun 17 15:27:55 2009 +0200
     1.2 +++ b/scripts/crosstool-NG.sh.in	Tue Jun 23 22:52:13 2009 +0200
     1.3 @@ -255,6 +255,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.