[bootlin/training-materials updates] master: sysdev: update to buildroot 2019.02 (e1594795)

[Alexandre Belloni]

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

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

commit e1594795254b9c9d558ece229076189d0b631481
Author: Alexandre Belloni <alexandre.belloni at bootlin.com>
Date:   Thu Apr 18 17:21:01 2019 +0200

    sysdev: update to buildroot 2019.02
    
    Signed-off-by: Alexandre Belloni <alexandre.belloni at bootlin.com>


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

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

diff --git a/labs/sysdev-application-debugging/sysdev-application-debugging.tex b/labs/sysdev-application-debugging/sysdev-application-debugging.tex
index 22c4e7f2..cfa8670f 100644
--- a/labs/sysdev-application-debugging/sysdev-application-debugging.tex
+++ b/labs/sysdev-application-debugging/sysdev-application-debugging.tex
@@ -18,7 +18,7 @@ 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 2018.08 sources into the current directory.
+Extract the Buildroot 2019.02 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/embedded-linux-labs/debugging} directory
-and extract the \code{buildroot-2018.08/output/images/rootfs.tar}
+and extract the \code{buildroot-2019.02/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:
 \footnotesize
 \begin{verbatim}
-export PATH=$HOME/embedded-linux-labs/debugging/buildroot-2018.08/output/host/bin:$PATH
+export PATH=$HOME/embedded-linux-labs/debugging/buildroot-2019.02/output/host/bin:$PATH
 \end{verbatim}
 \normalsize
 
@@ -155,7 +155,7 @@ variable (on one line):
 
 \begin{verbatim}
 (gdb) set sysroot /home/<user>/embedded-linux-labs/debugging/
-buildroot-2018.08/output/staging
+buildroot-2019.02/output/staging
 \end{verbatim}
 
 And tell \code{gdb} to connect to the remote system:
diff --git a/labs/sysdev-buildroot/sysdev-buildroot.tex b/labs/sysdev-buildroot/sysdev-buildroot.tex
index 7a0609f7..eaa4fc1a 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 2018.08
+\url{https://buildroot.org/}. Download the latest stable 2019.02
 version which we have tested for this lab. Uncompress the tarball
 and go inside the Buildroot source directory.
 
@@ -168,7 +168,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:
 
 \begin{verbatim}
-sudo tar xvf ../buildroot-2018.08/output/images/rootfs.tar
+sudo tar xvf ../buildroot-2019.02/output/images/rootfs.tar
 \end{verbatim}
 
 Add our \code{nfsroot} directory to the list of directories exported