[bootlin/training-materials updates] master: labs/buildroot-advanced-packages: post-extract hook is no longer needed (50bfa766)

[Thomas Petazzoni]

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

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

commit 50bfa766ba20a2e7b2d183640d3f3a1671f2025e
Author: Thomas Petazzoni <thomas.petazzoni at bootlin.com>
Date:   Wed Apr 15 07:50:08 2020 +0200

    labs/buildroot-advanced-packages: post-extract hook is no longer needed
    
    Due to changes in the autoreconf machinery in Buildroot (since
    2020.02), the post-extract hook to create the m4 file is no longer
    necessary, so drop this step from the lab.
    
    Signed-off-by: Thomas Petazzoni <thomas.petazzoni at bootlin.com>


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

50bfa766ba20a2e7b2d183640d3f3a1671f2025e
 .../buildroot-advanced-packages.tex                       | 15 +++++----------
 1 file changed, 5 insertions(+), 10 deletions(-)

diff --git a/labs/buildroot-advanced-packages/buildroot-advanced-packages.tex b/labs/buildroot-advanced-packages/buildroot-advanced-packages.tex
index 8153f278..01bffcae 100644
--- a/labs/buildroot-advanced-packages/buildroot-advanced-packages.tex
+++ b/labs/buildroot-advanced-packages/buildroot-advanced-packages.tex
@@ -53,16 +53,11 @@ an error due to the \code{configure} script being missing. What can
 you do about it? Hint: there is one Buildroot variable for {\em
 autotools} packages to solve this problem.
 
-Once this problem is solved, start the build again, you should reach a
-second problem related to a non-existing \code{m4} directory. So, add
-a {\em post-extract hook} to create the \code{m4} directory in
-\code{libfoo} source code.
-
-After this second problem is solved, \code{libfoo} should build
-fine. Look in \code{output/target/usr/lib}, the dynamic version of the
-library should be installed. However, if you look in
-\code{output/staging/}, you will see no sign of \code{libfoo}, neither
-the library in \code{output/staging/usr/lib} or the header file in
+\code{libfoo} should now build fine. Look in
+\code{output/target/usr/lib}, the dynamic version of the library
+should be installed. However, if you look in \code{output/staging/},
+you will see no sign of \code{libfoo}, neither the library in
+\code{output/staging/usr/lib} or the header file in
 \code{output/staging/usr/include}. This is an issue because the
 compiler will only look in \code{output/staging} for libraries and
 headers, so we must change our package so that it also installs to the