[bootlin/training-materials updates] master: Embedded Linux labs: update Buildroot version (f47ab3de)

Michael Opdenacker michael.opdenacker at bootlin.com
Fri May 8 10:26:58 CEST 2020

Repository : https://github.com/bootlin/training-materials
On branch  : master
Link       : https://github.com/bootlin/training-materials/commit/f47ab3de6103386f06960cca0760881a999c2f69


commit f47ab3de6103386f06960cca0760881a999c2f69
Author: Michael Opdenacker <michael.opdenacker at bootlin.com>
Date:   Fri May 8 10:26:58 2020 +0200

    Embedded Linux labs: update Buildroot version
    Signed-off-by: Michael Opdenacker <michael.opdenacker at bootlin.com>


 .../sysdev-application-debugging.tex                           | 10 +++++-----
 labs/sysdev-buildroot/sysdev-buildroot.tex                     |  8 ++++----
 2 files changed, 9 insertions(+), 9 deletions(-)

diff --git a/labs/sysdev-application-debugging/sysdev-application-debugging.tex b/labs/sysdev-application-debugging/sysdev-application-debugging.tex
index 153548db..aa949d6d 100644
--- a/labs/sysdev-application-debugging/sysdev-application-debugging.tex
+++ b/labs/sysdev-application-debugging/sysdev-application-debugging.tex
@@ -13,12 +13,12 @@ Because of issues in {\em gdb} and {\em ltrace} in the uClibc version
 that we are using in our toolchain, we will use a different toolchain
 in this lab, based on {\em glibc}. 
-As {\em glibc} has more complete features that lighter libraries,
+As {\em glibc} has more complete features than lighter libraries,
 it looks like a good idea to do your application debugging work
 with a {\em glibc} toolchain first, and then switch to lighter libraries
 once your application and software stack is production ready. 
-Extract the Buildroot 2019.02 sources into the current directory.
+Extract the Buildroot 2020.02.<n> sources into the current directory.
 Then, in the \code{menuconfig} interface, configure the target
 architecture as done previously but configure the toolchain and
@@ -58,7 +58,7 @@ target packages differently:
 Now, build your root filesystem.
 Go back to the \code{$HOME/__SESSION_NAME__-labs/debugging} directory
-and extract the \code{buildroot-2019.02/output/images/rootfs.tar}
+and extract the \code{buildroot-2020.02.<n>/output/images/rootfs.tar}
 archive in the \code{nfsroot} directory.
 Add this directory to the \code{/etc/exports} file and restart
@@ -81,7 +81,7 @@ you don't have the source code.
 Update the PATH:
-export PATH=$HOME/__SESSION_NAME__-labs/debugging/buildroot-2019.02/output/host/bin:$PATH
+export PATH=$HOME/__SESSION_NAME__-labs/debugging/buildroot-2020.02.<n>/output/host/bin:$PATH
@@ -155,7 +155,7 @@ variable (on one line):
 (gdb) set sysroot /home/<user>/__SESSION_NAME__-labs/debugging/
 Of course, replace \code{<user>} by your actual user name.
diff --git a/labs/sysdev-buildroot/sysdev-buildroot.tex b/labs/sysdev-buildroot/sysdev-buildroot.tex
index 41538e5b..fac3e948 100644
--- a/labs/sysdev-buildroot/sysdev-buildroot.tex
+++ b/labs/sysdev-buildroot/sysdev-buildroot.tex
@@ -11,7 +11,7 @@ go into it.
 \section{Get Buildroot and explore the source code}
 The official Buildroot website is available at
-\url{https://buildroot.org/}. Download the latest stable 2019.02
+\url{https://buildroot.org/}. Download the latest stable 2020.02.<n>
 version which we have tested for this lab. Uncompress the tarball
 and go inside the Buildroot source directory.
@@ -89,8 +89,8 @@ button whenever you need more details about a given option:
   \item \code{Toolchain path}: use the toolchain you built:
     (replace \code{<user>} by your actual user name)
-  \item \code{External toolchain gcc version}: \code{8.x}
-  \item \code{External toolchain kernel headers series}: \code{4.16.x}
+  \item \code{External toolchain gcc version}: \code{9.x}
+  \item \code{External toolchain kernel headers series}: \code{5.4.x or later}
   \item \code{External toolchain C library}: \code{uClibc/uClibc-ng}
   \item We must tell Buildroot about our toolchain configuration, so
     select \code{Toolchain has WCHAR support?},
@@ -176,7 +176,7 @@ a new \code{nfsroot} directory that is going to hold our system,
 exported over NFS. Go into this directory, and untar the rootfs using:
-sudo tar xvf ../buildroot-2019.02/output/images/rootfs.tar
+sudo tar xvf ../buildroot-2020.02.<n>/output/images/rootfs.tar
 Add our \code{nfsroot} directory to the list of directories exported

More information about the training-materials-updates mailing list