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

Age	Commit message (Collapse)	Author	Files	Lines
2016-12-02	Fix use of custom location if it is a directory.	Alexey Neyman	1	-1/+1
	In that case, CT_GetCustom just creates a symlink to the original. In that case, 'cp -a <path> .' gives an error and 'cp -a <path> <newdir>' creates <newdir> as a symlink (which will then run the build inside the shared directory, .build/src/<package>). Signed-off-by: Alexey Neyman <stilor@att.net>
2016-11-21	Partially revert 6f8e89cb5ca061e899bf3feaaf3fecf30d366c3e.	Alexey Neyman	1	-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-17	consistency: Use exported variables of required tools	Bryan Hundven	1	-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>
2015-11-15	file modes: Fix file modes... again.	Bryan Hundven	1	-0/+0
	These files are sourced, not executed, and do not need to be executable. Signed-off-by: Bryan Hundven <bryanhundven@gmail.com>
2015-11-13	Update new companion libs with *_for_target.	Alexey Neyman	1	-0/+1
	Signed-off-by: Alexey Neyman <stilor@att.net>
2015-11-13	Add gettext and libiconv as companion libs	Ray Donnelly	1	-0/+136
	.. they're needed for the RPC generation in glibc on both Cygwin and MinGW-w64. Neither are built on GNU/Linux and iconv is not built on Darwin. Two patches for gettext are needed, one so that -O0 works and one so that static builds can be made. They can take a good while to build, so if not needed for_host or for_build then they are not built. Signed-off-by: Ray Donnelly <mingw.android@gmail.com>