[FE training-materials-updates] sysdev-toolchain: switch to crosstool-ng 1.16

[Thomas Petazzoni]

Repository : git://git.free-electrons.com/training-materials.git

On branch  : master
Link       : http://git.free-electrons.com/training-materials/commit/?id=a6204036b656283a4a99488893701baa8db3eba6

>---------------------------------------------------------------

commit a6204036b656283a4a99488893701baa8db3eba6
Author: Thomas Petazzoni <thomas.petazzoni at free-electrons.com>
Date:   Thu Oct 4 18:09:44 2012 +0200

    sysdev-toolchain: switch to crosstool-ng 1.16
    
    Two advantages:
    
     * It fixes the sourceforge download problem.
    
     * The number of parallel jobs is automatically chosen, so we no
       longer have to tell the user to configure this.
    
    Signed-off-by: Thomas Petazzoni <thomas.petazzoni at free-electrons.com>


>---------------------------------------------------------------

a6204036b656283a4a99488893701baa8db3eba6
 labs/sysdev-toolchain/sysdev-toolchain.tex |    4 +---
 1 file changed, 1 insertion(+), 3 deletions(-)

diff --git a/labs/sysdev-toolchain/sysdev-toolchain.tex b/labs/sysdev-toolchain/sysdev-toolchain.tex
index 6379961..18c2bfa 100644
--- a/labs/sysdev-toolchain/sysdev-toolchain.tex
+++ b/labs/sysdev-toolchain/sysdev-toolchain.tex
@@ -28,7 +28,7 @@ sudo apt-get clean
 
 \section{Getting Crosstool-ng}
 
-Get the latest 1.15.x release of Crosstool-ng at
+Get the latest 1.16.x release of Crosstool-ng at
 \url{http://crosstool-ng.org}. Expand the archive right in the current
 directory, and enter the Crosstool-ng source directory.
 
@@ -79,8 +79,6 @@ In \code{Path and misc options}:
 \item Change \code{Prefix directory} to
   \code{/usr/local/xtools/${CT_TARGET}}. This is the place where
   the toolchain will be installed.
-\item Set \code{Number of parallel jobs} to 2 times the number of CPU cores
-  in your workstation\footnote{You can find this number by running \code{cat /proc/cpuinfo}}. Building your toolchain will be faster.
 \item Change \code{Maximum log level to see} to \code{DEBUG} so that we can have more
   details on what happened during the build in case something went wrong.
 \end{itemize}