crosstool-ng - A versatile (cross-)toolchain generator.

Age	Commit message (Collapse)	Author	Files	Lines
2017-07-08	Fix the references to old config variables	Alexey Neyman	1	-1/+1
	Signed-off-by: Alexey Neyman <stilor@att.net>
2017-02-27	Revert "Determine whether -E/-r option selects extended regexp"	Alexey Neyman	1	-1/+1
	This reverts commit 7bcf18bfab84374d3305c7a088f95ac1219ddf93.
2017-02-14	Determine whether -E/-r option selects extended regexp	Alexey Neyman	1	-1/+1
	... and then use the right option. See the note in scripts/functions on where we should use ${foo} and where just 'foo'; this boils down to whether we can expect the build tools override to be in effect (e.g. in the actual build scripts) or not (i.e. outside of scripts/build). While running in scripts/functions, or in scripts/crosstool-NG.sh the build tools override directory (.build/tools/bin) may have not been set up (yet, or at all). Also, modify the installed scripts (populate, xldd) accordingly. Signed-off-by: Alexey Neyman <stilor@att.net>
2016-11-21	Partially revert 6f8e89cb5ca061e899bf3feaaf3fecf30d366c3e.	Alexey Neyman	1	-1/+1
	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-17	consistency: Use exported variables of required tools	Bryan Hundven	1	-1/+1
	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>
2015-06-01	test_suite: Update gcc test_suite for multiple compilers	Ray Donnelly	1	-4/+4
	This commit updates gcc's test suite to use the new config options. Signed-off-by: Ray Donnelly <mingw.android@gmail.com> Reviewed-by: Bryan Hundven <bryanhundven@gmail.com> Reviewed-by: Yann Diorcet <diorcetyann@gmail.com>
2012-01-01	cc/gcc: copy file with 'cp -v', it rotates the progress bar	Yann E. MORIN"	1	-5/+5
	Installing the gcc test-suite can take a bit of time, so the progress bar is currently not rotating because there is no output during the copy. For an unsuspecting user, it could mean the process hung. With 'cp -v', the progress bar now rotates. Signed-off-by: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
2010-05-22	test-suite: apply cleanup pass	Yann E. MORIN"	1	-16/+10
	Remove all non-modifiable items (target tuple, gcc version, toolchain path...) Makefile syntax ( use $(...) instead of ${...} ) Update doc Space-damage cleanups
2010-05-19	test-suite: Added new test suite feature (experimental)	Martin Lund	1	-0/+36
	This patch adds support for installing the gcc test suite. A helper Makefile is provided for building and running the gcc tests. The default configuration runs all gcc tests and requires automatic ssh/scp login access to a networked target board. See README for more details. Note: Current feature is tested with the powerpc-unknown-linux-gnu sample but it should work with others as well. Signed-off-by: Martin Lund <mgl@doredevelopment.dk>