Allow user to add a directory component in the sys-root path.
Rename CT_DEBUG_INSTALL_DIR to CT_DEBUGROOT_DIR (to match CT_SYSROOT_DIR).
As a side effect, fix creating lib64->lib symlinks.
/trunk/scripts/build/debug/100-dmalloc.sh | 2 1 1 0 +-
/trunk/scripts/build/debug/400-ltrace.sh | 2 1 1 0 +-
/trunk/scripts/build/debug/300-gdb.sh | 6 3 3 0 +++---
/trunk/scripts/build/debug/500-strace.sh | 2 1 1 0 +-
/trunk/scripts/build/debug/200-duma.sh | 6 3 3 0 +++---
/trunk/scripts/crosstool-NG.sh.in | 16 7 9 0 +++++++---------
/trunk/scripts/functions | 2 1 1 0 +-
/trunk/config/toolchain.in | 17 17 0 0 +++++++++++++++++
8 files changed, 34 insertions(+), 19 deletions(-)
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.