freebsd-dev/tools
David Chisnall 52b42bace1 On platforms where clang is the default compiler, don't build gcc or libstdc++.
To enable them, set WITH_GCC and WITH_GNUCXX in src.conf.
Make clang default to using libc++ on FreeBSD 10.
Bumped __FreeBSD_version for the change.

GCC is still enabled on PC98, because the PC98 bootloader requires GCC to build
(or, at least, hard-codes the use of gcc into its build).

Thanks to everyone who helped make the ports tree ready for this (and bapt
for coordinating them all).  Also to imp for reviewing this and working on the
forward-porting of the changes in our gcc so that we're getting to a much
better place with regard to external toolchains.

Sorry to all of the people who helped who I forgot to mention by name.

Reviewed by:	bapt, imp, dim, ...
2013-09-06 20:08:03 +00:00
..
bsdbox Do a bunch of fixing and refactoring. 2012-08-29 22:55:50 +00:00
build On platforms where clang is the default compiler, don't build gcc or libstdc++. 2013-09-06 20:08:03 +00:00
debugscripts A number of places in the source tree still reference cuad.* after 2012-12-08 22:16:36 +00:00
diag Remove scripts and tools which only functioned when src was using CVS 2012-09-13 17:49:11 +00:00
kerneldoc Correct double "the the" 2012-09-14 21:28:56 +00:00
KSE
LibraryReport
regression libc/stdio: Allow fopen/freopen modes in any order (except initial r/w/a). 2013-09-06 13:47:16 +00:00
sched
test Add simple test for the read/write/lseek on posix shm filedescriptor. 2013-08-21 17:47:11 +00:00
tools Fix a compiler warning about signed vs unsigned compare. 2013-09-01 14:06:57 +00:00
install.sh Use = not == in test arguments. 2013-01-24 20:47:37 +00:00
make_libdeps.sh Import libyaml as libbsdyml (private brand name) 2013-03-04 11:27:41 +00:00
README
tinder.sh

$FreeBSD$

This directory tree contains tools used for the maintenance and
testing of FreeBSD.  There is no toplevel Makefile structure since
these tools are not meant to be built as part of the standard system,
though there may be individual Makefiles in some of the subdirs.

Please read the README files in the subdirs for further information.