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)
1 http://mirror.sh-linux.org/rpm-2003/SRPMS/gcc-3.2.3-3.src.rpm contains the following patches:
3 gcc-20030210-sh-linux-1.patch
4 gcc-3.2.3-libffi-1.patch
5 gcc-3.2.3-sh-linux-dwarf2-1.patch (*not* applied by the spec file, it's in there by accident)
7 gcc-3.2.3-libffi-1.patch was needed just to build, I think.
9 After that was applied, sh4 gcc seemed to compile fine, but c++ programs
10 failed to execute because libstdc++.so.5 was built without version
11 info. This was caused directly by libstdc++-v3/configure setting
12 SYMVER_MAP=config/linker-map.dummy because it sees that
13 no libgcc_s.so was generated; configure says
14 checking for shared libgcc... no.
16 Applying gcc-20030210-sh-linux-1.patch in hopes it makes those problems go away.