diff --git a/en_US.ISO8859-1/htdocs/news/status/report-2014-10-2014-12.xml b/en_US.ISO8859-1/htdocs/news/status/report-2014-10-2014-12.xml
index e19040d26e..638706ab10 100644
--- a/en_US.ISO8859-1/htdocs/news/status/report-2014-10-2014-12.xml
+++ b/en_US.ISO8859-1/htdocs/news/status/report-2014-10-2014-12.xml
@@ -379,4 +379,91 @@
+ The main goal of the external toolchain project is to be able
+ to build world and kernel with non default toolchain. It can be
+ helpful to:
+
+
+
The initial support for external toolchain only supported + clang. It has been extended to support recent GCC (4.9.1 has + been tested) and recent binutils (2.24 and 2.25).
+ +A large number of fixes have been committed to HEAD to support + incompatible behaviour changes between ld(1) from + binutils 2.17.50 (the version in base) and binutils 2.24+.
+ +A large number of warnings have been deactivated when building + the kernel to make sure it is possible to build the kernel with + recent GCC (first 4.6 and then 4.9.1)
+ +The build system has been changed to build libc++ as a C++ + stack when a recent enough GCC (4.6+) is used to build world. +
+ +To simplify using an external toolchain, the following + pre-seeded configurations have been added to the ports tree: +
Those packages will depend on special version of GCC + (minimalistic cross-built ready GCC) and on binutils. To use + them run: make CROSS_TOOLCHAIN=powerpc64-gcc TARGET=powerpc + TARGET_ARCH=powerpc64
+ +As a result of this effort, it has been possible to + successfully build and run a kernel and world built with GCC + 4.9.1 and binutils 2.24 on sparc64, amd64 (with minor tweaks for + amd64), powerpc and powerpc64.
+ + +