summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
Diffstat (limited to 'docs')
-rw-r--r--docs/7 - Contributing to crosstool-NG.txt2
-rw-r--r--docs/9 - How is a toolchain constructed.txt2
2 files changed, 2 insertions, 2 deletions
diff --git a/docs/7 - Contributing to crosstool-NG.txt b/docs/7 - Contributing to crosstool-NG.txt
index 5e363a1..2e95daf 100644
--- a/docs/7 - Contributing to crosstool-NG.txt
+++ b/docs/7 - Contributing to crosstool-NG.txt
@@ -34,7 +34,7 @@ Here is the (mostly-complete) list of categories and components:
binutils | binutils, elf2flt, sstrip
libc | uClibc, glibc, newlib, mingw, none
kernel | linux, mingw32, bare-metal
- debug | dmalloc, duma, gdb, ltrace, strace
+ debug | duma, gdb, ltrace, strace
complibs | gmp, mpfr, isl, cloog, mpc, libelf
comptools | make, m4, autoconf, automake, libtool
------------+-------------------------------------------------------
diff --git a/docs/9 - How is a toolchain constructed.txt b/docs/9 - How is a toolchain constructed.txt
index f8e3292..92edc3e 100644
--- a/docs/9 - How is a toolchain constructed.txt
+++ b/docs/9 - How is a toolchain constructed.txt
@@ -246,7 +246,7 @@ strictly required.
Second, crosstool-NG can also build some additional debug utilities to run on
the target. This is where we build, for example, the cross-gdb, the gdbserver
and the native gdb (the last two run on the target, the first runs on the
-same machine as the toolchain). The others (strace, ltrace, DUMA and dmalloc)
+same machine as the toolchain). The others (strace, ltrace and DUMA)
are absolutely not related to the toolchain, but are nice-to-have stuff that
can greatly help when developing, so are included as goodies (and they are
quite easy to build, so it's OK; more complex stuff is not worth the effort