summaryrefslogtreecommitdiff
path: root/scripts/build/debug/000-template.sh
AgeCommit message (Collapse)AuthorFilesLines
2017-03-21Move some scripts to a new directory, maintainerAlexey Neyman1-34/+0
... which are not of much interest to the end user. Signed-off-by: Alexey Neyman <stilor@att.net>
2016-11-21Partially revert 6f8e89cb5ca061e899bf3feaaf3fecf30d366c3e.Alexey Neyman1-2/+2
The referenced commit replaced 'make' with '${make}' everywhere. This is wrong for at least the utilities that we may build as companion tools (make, libtool): this will always invoke the version detected by configure by supplying the absolute path. In other words, the wrappers in .build/tools/bin are not fallbacks - they are either temporary (in case a respective companion tool is built) or permanent redirectors. This is the reason why the PATH= has .build/*/buildtools/bin at higher precedence than .build/tools/bin; the latter has the versions detected by configure and the former has the versions built as companion tools. Revert the rest of the gang (grep/sed/...) for consistency. After all, we may decide to supply some of them as well (awk, for instance). Signed-off-by: Alexey Neyman <stilor@att.net>
2015-11-17consistency: Use exported variables of required toolsBryan Hundven1-2/+2
We check for apps: * make * sed * grep * awk * libtool/libtoolize * install * patch * and more ...during configure. Our scripts should be consistent about using the variables that define where the found tool was found. Of course, we do hard-link these tools in buildtools, but that should be a backup for the components we are building. Our scripts should always use the tools we find. Signed-off-by: Bryan Hundven <bryanhundven@gmail.com>
2010-10-22scripts: add "FILE" and "CFG" debug levels.Anthony Foiani1-1/+1
I ran into some minor difficulties looking through the build log for a particular file: I wasn't interested in seeing it unpacked, but only when it is built or installed. Adding these two levels allows me to differentiate between those cases. [Yann E. MORIN: Those are blind log levels, and are used only to search in the build-log afterward.] Signed-off-by: Anthony Foiani <anthony.foiani@gmail.com>
2010-04-11scripts/functions: make CT_Patch dumberYann E. MORIN"1-1/+1
It is the responsibility of the caller to split the package name from its version. It already knows that.
2009-01-05Split CT_ExtractAndPatch in two: CT_Extract and CT_Patch:Yann E. MORIN"1-1/+2
- it is unworkable to have CT_ExtactAndPAtch cope with all those silly glibc addons: - they can have 'short' (as 'ports') or 'long' (as glibc-ports-2.7) names - patches are against eithe the short or long name, but non-uniformly use one or the other - it is the reposibility of the component (glibc in this case) to handle corner cases such as those - update all components to use the new functions /trunk/scripts/build/tools/000-template.sh | 3 2 1 0 +- /trunk/scripts/build/tools/100-libelf.sh | 3 2 1 0 +- /trunk/scripts/build/tools/200-sstrip.sh | 3 2 1 0 +- /trunk/scripts/build/kernel/linux.sh | 3 2 1 0 +- /trunk/scripts/build/binutils.sh | 3 2 1 0 +- /trunk/scripts/build/cc/gcc.sh | 3 2 1 0 +- /trunk/scripts/build/debug/000-template.sh | 3 2 1 0 +- /trunk/scripts/build/debug/100-dmalloc.sh | 3 2 1 0 +- /trunk/scripts/build/debug/400-ltrace.sh | 3 2 1 0 +- /trunk/scripts/build/debug/300-gdb.sh | 9 6 3 0 +++-- /trunk/scripts/build/debug/500-strace.sh | 7 3 4 0 ++-- /trunk/scripts/build/debug/200-duma.sh | 19 8 11 0 ++++------ /trunk/scripts/build/libc/glibc.sh | 14 12 2 0 ++++++- /trunk/scripts/build/libc/uClibc.sh | 13 9 4 0 +++++-- /trunk/scripts/build/libc/eglibc.sh | 14 12 2 0 ++++++- /trunk/scripts/build/gmp.sh | 3 2 1 0 +- /trunk/scripts/build/mpfr.sh | 3 2 1 0 +- /trunk/scripts/functions | 68 36 32 0 +++++++++++++++++++----------------- 18 files changed, 108 insertions(+), 69 deletions(-)
2009-01-03Get rid of all stuff related to building a /delivery' traball:Yann E. MORIN"1-11/+0
- building a delivery tarball has long been broken (since crostool-Ng is installable) - get rid of implied do_print_filename, that can be mis-leading now tarballs can not be built /trunk/scripts/build/kernel/bare-metal.sh | 4 0 4 0 ---- /trunk/scripts/build/kernel/linux.sh | 4 0 4 0 ---- /trunk/scripts/build/tools/000-template.sh | 11 0 11 0 ----------- /trunk/scripts/build/tools/100-libelf.sh | 4 0 4 0 ---- /trunk/scripts/build/tools/200-sstrip.sh | 11 1 10 0 +---------- /trunk/scripts/build/binutils.sh | 4 0 4 0 ---- /trunk/scripts/build/cc/gcc.sh | 5 0 5 0 ----- /trunk/scripts/build/debug/000-template.sh | 11 0 11 0 ----------- /trunk/scripts/build/debug/100-dmalloc.sh | 4 0 4 0 ---- /trunk/scripts/build/debug/400-ltrace.sh | 4 0 4 0 ---- /trunk/scripts/build/debug/300-gdb.sh | 7 0 7 0 ------- /trunk/scripts/build/debug/500-strace.sh | 4 0 4 0 ---- /trunk/scripts/build/debug/200-duma.sh | 4 0 4 0 ---- /trunk/scripts/build/libc/none.sh | 5 0 5 0 ----- /trunk/scripts/build/libc/glibc.sh | 10 0 10 0 ---------- /trunk/scripts/build/libc/uClibc.sh | 6 0 6 0 ------ /trunk/scripts/build/libc/eglibc.sh | 10 0 10 0 ---------- /trunk/scripts/build/gmp.sh | 6 0 6 0 ------ /trunk/scripts/build/mpfr.sh | 6 0 6 0 ------ /trunk/docs/overview.txt | 9 0 9 0 --------- 20 files changed, 1 insertion(+), 128 deletions(-)
2008-10-10Simplify the Tools and Debug facilities menu entries:Yann E. MORIN"1-7/+0
- each config file no longer have to define their own 'menuconfig foo - if FOO - endif' gym - each build script no longer has to say wether they are enabled - generation of the 'menuconfig' entries for the Tools and Debug facilities now uses the same code Some re-ordering of the code to be consistent with the steps ordering (tools, then debug). /trunk/kconfig/kconfig.mk | 66 43 23 0 +++++++++++++++++++++++------------- /trunk/scripts/build/debug.sh | 14 9 5 0 +++++--- /trunk/scripts/build/tools/000-template.sh | 7 0 7 0 ---- /trunk/scripts/build/tools/100-libelf.sh | 3 0 3 0 -- /trunk/scripts/build/tools/200-sstrip.sh | 2 0 2 0 - /trunk/scripts/build/debug/000-template.sh | 7 0 7 0 ---- /trunk/scripts/build/debug/100-dmalloc.sh | 3 0 3 0 -- /trunk/scripts/build/debug/400-ltrace.sh | 3 0 3 0 -- /trunk/scripts/build/debug/300-gdb.sh | 3 0 3 0 -- /trunk/scripts/build/debug/500-strace.sh | 3 0 3 0 -- /trunk/scripts/build/debug/200-duma.sh | 3 0 3 0 -- /trunk/scripts/build/tools.sh | 14 9 5 0 +++++--- /trunk/scripts/crosstool.sh | 2 1 1 0 /trunk/config/debug/ltrace.in | 14 3 11 0 ++------ /trunk/config/debug/dmalloc.in | 9 1 8 0 +---- /trunk/config/debug/gdb.in | 9 1 8 0 +---- /trunk/config/debug/strace.in | 10 1 9 0 ----- /trunk/config/debug/duma.in | 10 1 9 0 ----- /trunk/config/tools/libelf.in | 12 2 10 0 +------ /trunk/config/tools/sstrip.in | 10 1 9 0 ----- /trunk/config/config.in | 4 2 2 0 +- 21 files changed, 74 insertions(+), 134 deletions(-)
2008-07-14Advertise using CT_DoExecLog in the tools and debug templates.Yann E. MORIN"1-2/+3
/trunk/scripts/build/tools/000-template.sh | 5 3 2 0 +++-- /trunk/scripts/build/debug/000-template.sh | 5 3 2 0 +++-- 2 files changed, 6 insertions(+), 4 deletions(-)
2008-05-02For tools/ and debug/ build scripts, annd a numeric prefix, so that they ↵Yann E. MORIN"1-0/+50
always get built in the same order, in case of library dependencies. /trunk/scripts/build/debug.sh | 2 1 1 0 +- /trunk/scripts/build/tools.sh | 2 1 1 0 +- 2 files changed, 2 insertions(+), 2 deletions(-)