[bootlin/training-materials updates] master: labs/buildroot-*: toolchain prefix is now arm-none-linux-gnueabihf (5c79f015)

Thomas Petazzoni thomas.petazzoni at bootlin.com
Sat May 29 17:00:36 CEST 2021

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


commit 5c79f015bdc53519ab90f459561931badfc2017a
Author: Thomas Petazzoni <thomas.petazzoni at bootlin.com>
Date:   Sat May 29 15:37:26 2021 +0200

    labs/buildroot-*: toolchain prefix is now arm-none-linux-gnueabihf
    Signed-off-by: Thomas Petazzoni <thomas.petazzoni at bootlin.com>


 .../buildroot-advanced-packages.tex                            |  2 +-
 labs/buildroot-appdev/buildroot-appdev.tex                     | 10 +++++-----
 2 files changed, 6 insertions(+), 6 deletions(-)

diff --git a/labs/buildroot-advanced-packages/buildroot-advanced-packages.tex b/labs/buildroot-advanced-packages/buildroot-advanced-packages.tex
index 01bffcae..f229518a 100644
--- a/labs/buildroot-advanced-packages/buildroot-advanced-packages.tex
+++ b/labs/buildroot-advanced-packages/buildroot-advanced-packages.tex
@@ -192,7 +192,7 @@ You can even check that \code{bar} is linked against
 \code{libconfig.so} by doing:
-./output/host/usr/bin/arm-linux-gnueabihf-readelf -d output/target/usr/bin/bar
+./output/host/usr/bin/arm-none-linux-gnueabihf-readelf -d output/target/usr/bin/bar
 On the target, test \code{bar}. Then, create a file called
diff --git a/labs/buildroot-appdev/buildroot-appdev.tex b/labs/buildroot-appdev/buildroot-appdev.tex
index d9521546..11bbc5ec 100644
--- a/labs/buildroot-appdev/buildroot-appdev.tex
+++ b/labs/buildroot-appdev/buildroot-appdev.tex
@@ -35,7 +35,7 @@ export PATH=$HOME/__SESSION_NAME__-labs/buildroot/output/host/bin:$PATH
 Now you can build your application easily:
-arm-linux-gnueabihf-gcc -o myapp myapp.c
+arm-none-linux-gnueabihf-gcc -o myapp myapp.c
 Copy the myapp binary to your target using scp:
@@ -54,14 +54,14 @@ this lab data directory, \code{myapp.c}.
 If you try to build this application with just:
-arm-linux-gnueabihf-gcc -o myapp myapp.c
+arm-none-linux-gnueabihf-gcc -o myapp myapp.c
 It fails to build because it does not link with \code{libconfig}. So
 you can manually do:
-arm-linux-gnueabihf-gcc -o myapp myapp.c -lconfig
+arm-none-linux-gnueabihf-gcc -o myapp myapp.c -lconfig
 Since \code{libconfig.so} is in \code{output/staging/usr/lib} and the
@@ -87,7 +87,7 @@ pkg-config --cflags --libs libconfig
 And use that to build your application:
-arm-linux-gnueabihf-gcc -o myapp myapp.c $(pkg-config --cflags --libs libconfig)
+arm-none-linux-gnueabihf-gcc -o myapp myapp.c $(pkg-config --cflags --libs libconfig)
 In the case of \code{libconfig}, it doesn't simplify a lot because the
@@ -146,7 +146,7 @@ Back on the host, run the cross-gdb with the \code{myapp} application
 as argument:
-arm-linux-gnueabihf-gdb myapp
+arm-none-linux-gnueabihf-gdb myapp
 We need to tell \code{gdb} where the libraries can be found:

More information about the training-materials-updates mailing list