[bootlin/training-materials updates] master: labs: replace embedded-linux-labs by __SESSION_NAME__-labs (70fca2db)
Thomas Petazzoni
thomas.petazzoni at bootlin.com
Wed Jan 29 15:36:11 CET 2020
Repository : https://github.com/bootlin/training-materials
On branch : master
Link : https://github.com/bootlin/training-materials/commit/70fca2dbe11383390aaaa5ce2cd1279d315a0339
>---------------------------------------------------------------
commit 70fca2dbe11383390aaaa5ce2cd1279d315a0339
Author: Thomas Petazzoni <thomas.petazzoni at bootlin.com>
Date: Wed Jan 29 15:33:17 2020 +0100
labs: replace embedded-linux-labs by __SESSION_NAME__-labs
Signed-off-by: Thomas Petazzoni <thomas.petazzoni at bootlin.com>
>---------------------------------------------------------------
70fca2dbe11383390aaaa5ce2cd1279d315a0339
.../sysdev-application-debugging.tex | 10 ++--
.../sysdev-application-development.tex | 4 +-
.../sysdev-block-filesystems-stm32.tex | 2 +-
.../sysdev-block-filesystems.tex | 2 +-
labs/sysdev-buildroot/sysdev-buildroot.tex | 4 +-
.../sysdev-flash-filesystems.tex | 4 +-
.../sysdev-kernel-cross-compiling-stm32.tex | 4 +-
.../sysdev-kernel-cross-compiling.tex | 2 +-
.../sysdev-kernel-fetch-and-patch.tex | 4 +-
labs/sysdev-real-time/sysdev-real-time.tex | 14 ++---
labs/sysdev-thirdparty/sysdev-thirdparty.tex | 68 +++++++++++-----------
labs/sysdev-tinysystem/sysdev-tinysystem.tex | 8 +--
labs/sysdev-toolchain/sysdev-toolchain.tex | 2 +-
labs/sysdev-u-boot/sysdev-u-boot.tex | 2 +-
14 files changed, 65 insertions(+), 65 deletions(-)
diff --git a/labs/sysdev-application-debugging/sysdev-application-debugging.tex b/labs/sysdev-application-debugging/sysdev-application-debugging.tex
index 5dabdada..153548db 100644
--- a/labs/sysdev-application-debugging/sysdev-application-debugging.tex
+++ b/labs/sysdev-application-debugging/sysdev-application-debugging.tex
@@ -4,7 +4,7 @@
\section{Setup}
-Go to the \code{$HOME/embedded-linux-labs/debugging} directory.
+Go to the \code{$HOME/__SESSION_NAME__-labs/debugging} directory.
Create an \code{nfsroot} directory.
\section{Debugging setup}
@@ -57,7 +57,7 @@ target packages differently:
Now, build your root filesystem.
-Go back to the \code{$HOME/embedded-linux-labs/debugging} directory
+Go back to the \code{$HOME/__SESSION_NAME__-labs/debugging} directory
and extract the \code{buildroot-2019.02/output/images/rootfs.tar}
archive in the \code{nfsroot} directory.
@@ -69,7 +69,7 @@ kernel as before.
\section{Using strace}
-Now, go to the \code{$HOME/embedded-linux-labs/debugging} directory.
+Now, go to the \code{$HOME/__SESSION_NAME__-labs/debugging} directory.
\code{strace} allows to trace all the system calls made by a process:
opening, reading and writing files, starting other processes,
@@ -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-2019.02/output/host/bin:$PATH
+export PATH=$HOME/__SESSION_NAME__-labs/debugging/buildroot-2019.02/output/host/bin:$PATH
\end{verbatim}
\normalsize
@@ -154,7 +154,7 @@ your workstation. This is done by setting the \code{gdb} \code{sysroot}
variable (on one line):
\begin{verbatim}
-(gdb) set sysroot /home/<user>/embedded-linux-labs/debugging/
+(gdb) set sysroot /home/<user>/__SESSION_NAME__-labs/debugging/
buildroot-2019.02/output/staging
\end{verbatim}
diff --git a/labs/sysdev-application-development/sysdev-application-development.tex b/labs/sysdev-application-development/sysdev-application-development.tex
index f51170c1..bd5fb6b8 100644
--- a/labs/sysdev-application-development/sysdev-application-development.tex
+++ b/labs/sysdev-application-development/sysdev-application-development.tex
@@ -3,7 +3,7 @@
\section{Setup}
-Go to the \code{$HOME/embedded-linux-labs/appdev} directory.
+Go to the \code{$HOME/__SESSION_NAME__-labs/appdev} directory.
\section{Compile your own application}
@@ -25,7 +25,7 @@ Let's add this directory to our \code{PATH}:
\footnotesize
\begin{verbatim}
-export PATH=$HOME/embedded-linux-labs/buildroot/buildroot-XXXX.YY/output/host/usr/bin:$PATH
+export PATH=$HOME/__SESSION_NAME__-labs/buildroot/buildroot-XXXX.YY/output/host/usr/bin:$PATH
\end{verbatim}
\normalsize
diff --git a/labs/sysdev-block-filesystems-stm32/sysdev-block-filesystems-stm32.tex b/labs/sysdev-block-filesystems-stm32/sysdev-block-filesystems-stm32.tex
index b5a59fdc..836118bf 100644
--- a/labs/sysdev-block-filesystems-stm32/sysdev-block-filesystems-stm32.tex
+++ b/labs/sysdev-block-filesystems-stm32/sysdev-block-filesystems-stm32.tex
@@ -19,7 +19,7 @@ with this SD card, without using NFS anymore.
\section{Setup}
Throughout this lab, we will continue to use the root filesystem we
-have created in the \code{$HOME/embedded-linux-labs/tinysystem/nfsroot}
+have created in the \code{$HOME/__SESSION_NAME__-labs/tinysystem/nfsroot}
directory, which we will progressively adapt to use block filesystems.
\section{Filesystem support in the kernel}
diff --git a/labs/sysdev-block-filesystems/sysdev-block-filesystems.tex b/labs/sysdev-block-filesystems/sysdev-block-filesystems.tex
index 248ef3bf..42e22042 100644
--- a/labs/sysdev-block-filesystems/sysdev-block-filesystems.tex
+++ b/labs/sysdev-block-filesystems/sysdev-block-filesystems.tex
@@ -19,7 +19,7 @@ be booted with this SD card, without using NFS anymore.
\section{Setup}
Throughout this lab, we will continue to use the root filesystem we
-have created in the \code{$HOME/embedded-linux-labs/tinysystem/nfsroot}
+have created in the \code{$HOME/__SESSION_NAME__-labs/tinysystem/nfsroot}
directory, which we will progressively adapt to use block filesystems.
\section{Filesystem support in the kernel}
diff --git a/labs/sysdev-buildroot/sysdev-buildroot.tex b/labs/sysdev-buildroot/sysdev-buildroot.tex
index 7f8ec724..41538e5b 100644
--- a/labs/sysdev-buildroot/sysdev-buildroot.tex
+++ b/labs/sysdev-buildroot/sysdev-buildroot.tex
@@ -5,7 +5,7 @@
\section{Setup}
-Create the \code{$HOME/embedded-linux-labs/buildroot} directory and
+Create the \code{$HOME/__SESSION_NAME__-labs/buildroot} directory and
go into it.
\section{Get Buildroot and explore the source code}
@@ -171,7 +171,7 @@ explore its contents:
\section{Run the generated system}
-Go back to the \code{$HOME/embedded-linux-labs/buildroot/} directory. Create
+Go back to the \code{$HOME/__SESSION_NAME__-labs/buildroot/} directory. Create
a new \code{nfsroot} directory that is going to hold our system,
exported over NFS. Go into this directory, and untar the rootfs using:
diff --git a/labs/sysdev-flash-filesystems/sysdev-flash-filesystems.tex b/labs/sysdev-flash-filesystems/sysdev-flash-filesystems.tex
index 5199d2d3..ad02b3ed 100644
--- a/labs/sysdev-flash-filesystems/sysdev-flash-filesystems.tex
+++ b/labs/sysdev-flash-filesystems/sysdev-flash-filesystems.tex
@@ -8,7 +8,7 @@ After this lab, you will be able to:
\section{Setup}
-Stay in \code{$HOME/embedded-linux-labs/tinysystem}. Install the
+Stay in \code{$HOME/__SESSION_NAME__-labs/tinysystem}. Install the
\code{mtd-utils} package, which will be useful to create UBIFS and
UBI images.
@@ -50,7 +50,7 @@ in the next section.
To prepare filesystem images, we won't use what you stored on the SD
card during the previous lab. We will get back to the filesystem sources
-that you have in \code{$HOME/embedded-linux-labs/tinysystem/nfsroot}.
+that you have in \code{$HOME/__SESSION_NAME__-labs/tinysystem/nfsroot}.
To run \code{mkfs.ubifs}, you will need to find the Logical Erase
Block (LEB) size that UBI will use. To find out this information,
diff --git a/labs/sysdev-kernel-cross-compiling-stm32/sysdev-kernel-cross-compiling-stm32.tex b/labs/sysdev-kernel-cross-compiling-stm32/sysdev-kernel-cross-compiling-stm32.tex
index 6f7c2749..2faaa10d 100644
--- a/labs/sysdev-kernel-cross-compiling-stm32/sysdev-kernel-cross-compiling-stm32.tex
+++ b/labs/sysdev-kernel-cross-compiling-stm32/sysdev-kernel-cross-compiling-stm32.tex
@@ -12,7 +12,7 @@ After this lab, you will be able to:
\section{Setup}
-Go to the \code{$HOME/embedded-linux-labs/kernel} directory.
+Go to the \code{$HOME/__SESSION_NAME__-labs/kernel} directory.
\section{Target system}
@@ -48,7 +48,7 @@ Also, don't forget to either:
We could use the \code{multi_v7_defconfig} default configuration to
build a working kernel but to save time and compile less code, we
provide in
-\code{$HOME/embedded-linux-labs/linux-stm32/} a minimal configuration
+\code{$HOME/__SESSION_NAME__-labs/linux-stm32/} a minimal configuration
file, named \code{stm31mp157_defconfig}. Copy it to \code{.config} and
then run either \code{make olddefconfig} or \code{make oldconfig} if
you want to get asked for all the possible choices.
diff --git a/labs/sysdev-kernel-cross-compiling/sysdev-kernel-cross-compiling.tex b/labs/sysdev-kernel-cross-compiling/sysdev-kernel-cross-compiling.tex
index 84269217..7c7aa763 100644
--- a/labs/sysdev-kernel-cross-compiling/sysdev-kernel-cross-compiling.tex
+++ b/labs/sysdev-kernel-cross-compiling/sysdev-kernel-cross-compiling.tex
@@ -12,7 +12,7 @@ After this lab, you will be able to:
\section{Setup}
-Go to the \code{$HOME/embedded-linux-labs/kernel} directory.
+Go to the \code{$HOME/__SESSION_NAME__-labs/kernel} directory.
\section{Target system}
diff --git a/labs/sysdev-kernel-fetch-and-patch/sysdev-kernel-fetch-and-patch.tex b/labs/sysdev-kernel-fetch-and-patch/sysdev-kernel-fetch-and-patch.tex
index 8454c0a3..d4d757ec 100644
--- a/labs/sysdev-kernel-fetch-and-patch/sysdev-kernel-fetch-and-patch.tex
+++ b/labs/sysdev-kernel-fetch-and-patch/sysdev-kernel-fetch-and-patch.tex
@@ -9,7 +9,7 @@ After this lab, you will be able to:
\section{Setup}
-Create the \code{$HOME/embedded-linux-labs/kernel} directory and go into it.
+Create the \code{$HOME/__SESSION_NAME__-labs/kernel} directory and go into it.
\section{Get the sources}
@@ -50,7 +50,7 @@ source directory.
of Linux 4.19.
Apply the patch named
- \code{$HOME/embedded-linux-labs/linux-stm32/stm31mp157_support.patch}}{}
+ \code{$HOME/__SESSION_NAME__-labs/linux-stm32/stm31mp157_support.patch}}{}
View one of the patch files with \code{vi} or \code{gvim}
(if you prefer a graphical editor), to understand the information carried
diff --git a/labs/sysdev-real-time/sysdev-real-time.tex b/labs/sysdev-real-time/sysdev-real-time.tex
index 7a205693..827886d9 100644
--- a/labs/sysdev-real-time/sysdev-real-time.tex
+++ b/labs/sysdev-real-time/sysdev-real-time.tex
@@ -15,7 +15,7 @@ POSIX real-time API, and against Xenomai's POSIX skin.
\section{Setup}
-Go to the \code{$HOME/embedded-linux-labs/realtime/} directory.
+Go to the \code{$HOME/__SESSION_NAME__-labs/realtime/} directory.
Install the \code{netcat} package.
@@ -138,7 +138,7 @@ Let's configure our \code{PATH} to use this toolchain:
\scriptsize
\begin{verbatim}
-export PATH=$HOME/embedded-linux-labs/realtime/buildroot-YYYY.MM/output/host/usr/bin:$PATH
+export PATH=$HOME/__SESSION_NAME__-labs/realtime/buildroot-YYYY.MM/output/host/usr/bin:$PATH
\end{verbatim}
\normalsize
@@ -204,7 +204,7 @@ improvement in the maximum latency.
\section{Testing Xenomai scheduling latency}
-Stay in \code{$HOME/embedded-linux-labs/realtime}.
+Stay in \code{$HOME/__SESSION_NAME__-labs/realtime}.
Download the 2.6.4 release of Xenomai (that's what our version of
Buildroot supports by default), and extract it.
@@ -219,7 +219,7 @@ and extract them.
Now, prepare our kernel for Xenomai compilation:
\begin{verbatim}
-cd $HOME/embedded-linux-labs/realtime
+cd $HOME/__SESSION_NAME__-labs/realtime
./xenomai-2.6.4/scripts/prepare-kernel.sh --arch=arm \
--linux=linux-3.14.17 \
--adeos=xenomai-2.6.4/ksrc/arch/arm/patches/ipipe-core-3.14.17-arm-4.patch
@@ -246,7 +246,7 @@ So go in your Buildroot source directory, and force Buildroot to build
the host variant of {\em pkg-config}:
\begin{verbatim}
-cd $HOME/embedded-linux-labs/realtime/buildroot-YYYY.MM/
+cd $HOME/__SESSION_NAME__-labs/realtime/buildroot-YYYY.MM/
make host-pkgconf
\end{verbatim}
@@ -254,8 +254,8 @@ We can now compile \code{rttest} for the Xenomai POSIX skin:
\scriptsize
\begin{verbatim}
-cd $HOME/embedded-linux-labs/realtime/nfsroot/root
-export PATH=$HOME/embedded-linux-labs/realtime/buildroot-YYYY.MM/output/host/usr/bin:$PATH
+cd $HOME/__SESSION_NAME__-labs/realtime/nfsroot/root
+export PATH=$HOME/__SESSION_NAME__-labs/realtime/buildroot-YYYY.MM/output/host/usr/bin:$PATH
arm-none-linux-gnueabi-gcc -o rttest rttest.c \
$(pkg-config --libs --cflags libxenomai_posix)
\end{verbatim}
diff --git a/labs/sysdev-thirdparty/sysdev-thirdparty.tex b/labs/sysdev-thirdparty/sysdev-thirdparty.tex
index e6909560..486c6382 100644
--- a/labs/sysdev-thirdparty/sysdev-thirdparty.tex
+++ b/labs/sysdev-thirdparty/sysdev-thirdparty.tex
@@ -93,7 +93,7 @@ To sum up, the {\em staging} space will contain everything that's
needed for compilation, while the {\em target} space will contain only
what's needed for execution.
-So, in \code{$HOME/embedded-linux-labs/thirdparty}, create two
+So, in \code{$HOME/__SESSION_NAME__-labs/thirdparty}, create two
directories: \code{staging} and \code{target}.
For the target, we need a basic system with BusyBox and
@@ -102,7 +102,7 @@ initialization scripts. We will re-use the system built in the {\em A
directory:
\begin{verbatim}
-cp -a $HOME/embedded-linux-labs/tinysystem/nfsroot/* target/
+cp -a $HOME/__SESSION_NAME__-labs/tinysystem/nfsroot/* target/
\end{verbatim}
Note that for this lab, a lot of typing will be required. To save time
@@ -122,7 +122,7 @@ Make your board boot from this new directory through NFS.
\code{alsa-lib} is a library supposed to handle the interaction with
the ALSA subsystem. It is available at
\url{http://alsa-project.org}. Download version 1.1.6, and extract it
-in \code{$HOME/embedded-linux-labs/thirdparty/}.
+in \code{$HOME/__SESSION_NAME__-labs/thirdparty/}.
By looking at the \code{configure} script, we see that it has
been generated by \code{autoconf} (the header contains a
@@ -295,14 +295,14 @@ application or library will be installed on your host while building
the root filesystem.
For example, libasound will be installed in
-\code{$HOME/embedded-linux-labs/thirdparty/target/usr/lib/} because this is
+\code{$HOME/__SESSION_NAME__-labs/thirdparty/target/usr/lib/} because this is
the directory where we are building the root filesystem, but once our
target system will be running, it will see libasound in
\code{/usr/lib}.
The prefix corresponds to the path in the target system and {\bf
never} on the host. So, one should {\bf never} pass a prefix like
-\code{$HOME/embedded-linux-labs/thirdparty/target/usr}, otherwise at
+\code{$HOME/__SESSION_NAME__-labs/thirdparty/target/usr}, otherwise at
runtime, the application or library may look for files inside this
directory on the target system, which obviously doesn't exist! By
default, most build systems will install the application or library in
@@ -314,7 +314,7 @@ We now only have the installation process left to do.
First, let's make the installation in the {\em staging} space:
\begin{verbatim}
-make DESTDIR=$HOME/embedded-linux-labs/thirdparty/staging install
+make DESTDIR=$HOME/__SESSION_NAME__-labs/thirdparty/staging install
\end{verbatim}
Now look at what has been installed by alsa-lib:
@@ -396,7 +396,7 @@ can be found: there are not in the default directory
Let's use it:
\begin{verbatim}
-CPPFLAGS=-I$HOME/embedded-linux-labs/thirdparty/staging/usr/include \
+CPPFLAGS=-I$HOME/__SESSION_NAME__-labs/thirdparty/staging/usr/include \
CC=arm-linux-gcc \
./configure --host=arm-linux --prefix=/usr
\end{verbatim}
@@ -427,8 +427,8 @@ help text of the \code{configure} script:
Let's use this \code{LDFLAGS} variable:
\begin{verbatim}
-LDFLAGS=-L$HOME/embedded-linux-labs/thirdparty/staging/usr/lib \
-CPPFLAGS=-I$HOME/embedded-linux-labs/thirdparty/staging/usr/include \
+LDFLAGS=-L$HOME/__SESSION_NAME__-labs/thirdparty/staging/usr/lib \
+CPPFLAGS=-I$HOME/__SESSION_NAME__-labs/thirdparty/staging/usr/include \
CC=arm-linux-gcc \
./configure --host=arm-linux --prefix=/usr
\end{verbatim}
@@ -445,8 +445,8 @@ just like we built {\em alsa-lib}. We will also need to disable support
for {\em xmlto} that generates the documentation.
\begin{verbatim}
-LDFLAGS=-L$HOME/embedded-linux-labs/thirdparty/staging/usr/lib \
-CPPFLAGS=-I$HOME/embedded-linux-labs/thirdparty/staging/usr/include \
+LDFLAGS=-L$HOME/__SESSION_NAME__-labs/thirdparty/staging/usr/lib \
+CPPFLAGS=-I$HOME/__SESSION_NAME__-labs/thirdparty/staging/usr/include \
CC=arm-linux-gcc \
./configure --host=arm-linux --prefix=/usr \
--disable-alsamixer --disable-xmlto
@@ -540,7 +540,7 @@ So, we have:
Now, let's make the installation in the {\em staging} space:
\begin{verbatim}
-make DESTDIR=$HOME/embedded-linux-labs/thirdparty/staging/ install
+make DESTDIR=$HOME/__SESSION_NAME__-labs/thirdparty/staging/ install
\end{verbatim}
Then, let's install only the necessary files in the {\em target}
@@ -597,7 +597,7 @@ Installation to the {\em staging} space can be done using the
classical \code{DESTDIR} mechanism:
\begin{verbatim}
-make DESTDIR=$HOME/embedded-linux-labs/thirdparty/staging/ install
+make DESTDIR=$HOME/__SESSION_NAME__-labs/thirdparty/staging/ install
\end{verbatim}
And finally, only install manually in the {\em target} space the files
@@ -638,8 +638,8 @@ Use these:
\begin{verbatim}
CC=arm-linux-gcc ./configure --host=arm-linux --prefix=/usr \
- --with-ogg-includes=$HOME/embedded-linux-labs/thirdparty/staging/usr/include \
- --with-ogg-libraries=$HOME/embedded-linux-labs/thirdparty/staging/usr/lib
+ --with-ogg-includes=$HOME/__SESSION_NAME__-labs/thirdparty/staging/usr/include \
+ --with-ogg-libraries=$HOME/__SESSION_NAME__-labs/thirdparty/staging/usr/lib
\end{verbatim}
Then, compile the library:
@@ -651,7 +651,7 @@ make
Install it in the {\em staging} space:
\begin{verbatim}
-make DESTDIR=$HOME/embedded-linux-labs/thirdparty/staging/ install
+make DESTDIR=$HOME/__SESSION_NAME__-labs/thirdparty/staging/ install
\end{verbatim}
And install only the required files in the {\em target} space:
@@ -675,8 +675,8 @@ Configuring {\em libao} is once again fairly easy, and similar to
every sane autotools based build system:
\begin{verbatim}
-LDFLAGS=-L$HOME/embedded-linux-labs/thirdparty/staging/usr/lib \
-CPPFLAGS=-I$HOME/embedded-linux-labs/thirdparty/staging/usr/include \
+LDFLAGS=-L$HOME/__SESSION_NAME__-labs/thirdparty/staging/usr/lib \
+CPPFLAGS=-I$HOME/__SESSION_NAME__-labs/thirdparty/staging/usr/include \
CC=arm-linux-gcc ./configure --host=arm-linux \
--prefix=/usr
\end{verbatim}
@@ -691,7 +691,7 @@ Installation to the {\em staging} space can be done using the
classical \code{DESTDIR} mechanism:
\begin{verbatim}
-make DESTDIR=$HOME/embedded-linux-labs/thirdparty/staging/ install
+make DESTDIR=$HOME/__SESSION_NAME__-labs/thirdparty/staging/ install
\end{verbatim}
And finally, install manually the only needed files at runtime in the
@@ -736,8 +736,8 @@ configuration options:
So, let's begin with our usual \code{configure} line:
\begin{verbatim}
-LDFLAGS=-L$HOME/embedded-linux-labs/thirdparty/staging/usr/lib \
-CPPFLAGS=-I$HOME/embedded-linux-labs/thirdparty/staging/usr/include \
+LDFLAGS=-L$HOME/__SESSION_NAME__-labs/thirdparty/staging/usr/lib \
+CPPFLAGS=-I$HOME/__SESSION_NAME__-labs/thirdparty/staging/usr/include \
CC=arm-linux-gcc \
./configure --host=arm-linux --prefix=/usr
\end{verbatim}
@@ -794,7 +794,7 @@ explained in the manual page of \code{pkg-config}.
Moreover, the \code{.pc} files contain references to paths. For
example, in
-\code{$HOME/embedded-linux-labs/thirdparty/staging/usr/lib/pkgconfig/ao.pc},
+\code{$HOME/__SESSION_NAME__-labs/thirdparty/staging/usr/lib/pkgconfig/ao.pc},
we can see:
\begin{verbatim}
@@ -817,10 +817,10 @@ environment variables:
\small
\begin{verbatim}
-LDFLAGS=-L$HOME/embedded-linux-labs/thirdparty/staging/usr/lib \
-CPPFLAGS=-I$HOME/embedded-linux-labs/thirdparty/staging/usr/include \
-PKG_CONFIG_LIBDIR=$HOME/embedded-linux-labs/thirdparty/staging/usr/lib/pkgconfig \
-PKG_CONFIG_SYSROOT_DIR=$HOME/embedded-linux-labs/thirdparty/staging \
+LDFLAGS=-L$HOME/__SESSION_NAME__-labs/thirdparty/staging/usr/lib \
+CPPFLAGS=-I$HOME/__SESSION_NAME__-labs/thirdparty/staging/usr/include \
+PKG_CONFIG_LIBDIR=$HOME/__SESSION_NAME__-labs/thirdparty/staging/usr/lib/pkgconfig \
+PKG_CONFIG_SYSROOT_DIR=$HOME/__SESSION_NAME__-labs/thirdparty/staging \
CC=arm-linux-gcc \
./configure --host=arm-linux --prefix=/usr
\end{verbatim}
@@ -835,8 +835,8 @@ make
It should fail with the following cryptic message:
\footnotesize
\begin{verbatim}
-make[2]: Entering directory '/home/tux/embedded-linux-labs/thirdparty/vorbis-tools-1.4.0/ogg123'
-if arm-linux-gcc -DSYSCONFDIR=\"/usr/etc\" -DLOCALEDIR=\"/usr/share/locale\" -DHAVE_CONFIG_H -I. -I. -I.. -I/usr/include -I../include -I../intl -I/home/tux/embedded-linux-labs/thirdparty/staging/usr/include -O2 -Wall -ffast-math -fsigned-char -g -O2 -MT audio.o -MD -MP -MF ".deps/audio.Tpo" -c -o audio.o audio.c; \
+make[2]: Entering directory '/home/tux/__SESSION_NAME__-labs/thirdparty/vorbis-tools-1.4.0/ogg123'
+if arm-linux-gcc -DSYSCONFDIR=\"/usr/etc\" -DLOCALEDIR=\"/usr/share/locale\" -DHAVE_CONFIG_H -I. -I. -I.. -I/usr/include -I../include -I../intl -I/home/tux/__SESSION_NAME__-labs/thirdparty/staging/usr/include -O2 -Wall -ffast-math -fsigned-char -g -O2 -MT audio.o -MD -MP -MF ".deps/audio.Tpo" -c -o audio.o audio.c; \
then mv -f ".deps/audio.Tpo" ".deps/audio.Po"; else rm -f ".deps/audio.Tpo"; exit 1; fi
In file included from audio.c:22:
/usr/include/stdio.h:27:10: fatal error: bits/libc-header-start.h: No such file or directory
@@ -866,10 +866,10 @@ flags.
Add this to the \code{configure} command line to get
\begin{verbatim}
-LDFLAGS=-L$HOME/embedded-linux-labs/thirdparty/staging/usr/lib \
-CPPFLAGS=-I$HOME/embedded-linux-labs/thirdparty/staging/usr/include \
-PKG_CONFIG_LIBDIR=$HOME/embedded-linux-labs/thirdparty/staging/usr/lib/pkgconfig \
-PKG_CONFIG_SYSROOT_DIR=$HOME/embedded-linux-labs/thirdparty/staging \
+LDFLAGS=-L$HOME/__SESSION_NAME__-labs/thirdparty/staging/usr/lib \
+CPPFLAGS=-I$HOME/__SESSION_NAME__-labs/thirdparty/staging/usr/include \
+PKG_CONFIG_LIBDIR=$HOME/__SESSION_NAME__-labs/thirdparty/staging/usr/lib/pkgconfig \
+PKG_CONFIG_SYSROOT_DIR=$HOME/__SESSION_NAME__-labs/thirdparty/staging \
LIBS=-lm \
CC=arm-linux-gcc \
./configure --host=arm-linux --prefix=/usr --without-curl
@@ -880,7 +880,7 @@ Finally, it builds!
Now, install the vorbis-tools to the {\em staging} space using:
\begin{verbatim}
-make DESTDIR=$HOME/embedded-linux-labs/thirdparty/staging/ install
+make DESTDIR=$HOME/__SESSION_NAME__-labs/thirdparty/staging/ install
\end{verbatim}
And then install them in the {\em target} space:
@@ -918,7 +918,7 @@ open("/lib/ld-uClibc.so.1", O_RDONLY) = -1 ENOENT (No such file or directory)
open("/lib/ld-uClibc.so.1", O_RDONLY) = -1 ENOENT (No such file or directory)
open("/usr/lib/ld-uClibc.so.1", O_RDONLY) = -1 ENOENT (No such file or directory)
open("/usr/X11R6/lib/ld-uClibc.so.1", O_RDONLY) = -1 ENOENT (No such file or directory)
-open("/home/tux/embedded-linux-labs/thirdparty/staging/usr/lib/ld-uClibc.so.1", O_RDONLY) = -1 ENOENT (No such file or directory)
+open("/home/tux/__SESSION_NAME__-labs/thirdparty/staging/usr/lib/ld-uClibc.so.1", O_RDONLY) = -1 ENOENT (No such file or directory)
write(2, "ERROR: Failed to load plugin ", 29ERROR: Failed to load plugin ) = 29
write(2, "/usr/lib/ao/plugins-4/libalsa.so", 32/usr/lib/ao/plugins-4/libalsa.so) = 32
write(2, " => dlopen() failed\n", 20 => dlopen() failed
diff --git a/labs/sysdev-tinysystem/sysdev-tinysystem.tex b/labs/sysdev-tinysystem/sysdev-tinysystem.tex
index 48dcca01..766a73f6 100644
--- a/labs/sysdev-tinysystem/sysdev-tinysystem.tex
+++ b/labs/sysdev-tinysystem/sysdev-tinysystem.tex
@@ -34,12 +34,12 @@ target to test the impact of script or application updates.
\section{Setup}
-Go to the \code{$HOME/embedded-linux-labs/tinysystem/} directory.
+Go to the \code{$HOME/__SESSION_NAME__-labs/tinysystem/} directory.
\section{Kernel configuration}
We will re-use the kernel sources from our previous lab, in
-\code{$HOME/embedded-linux-labs/kernel/}.
+\code{$HOME/__SESSION_NAME__-labs/kernel/}.
In the kernel configuration built in the previous lab, verify that you
have all options needed for booting the system using a root filesystem
@@ -59,7 +59,7 @@ IP address of your board will be \code{192.168.0.100}:
\footnotesize
\begin{verbatim}
-/home/<user>/embedded-linux-labs/tinysystem/nfsroot 192.168.0.100(rw,no_root_squash,no_subtree_check)
+/home/<user>/__SESSION_NAME__-labs/tinysystem/nfsroot 192.168.0.100(rw,no_root_squash,no_subtree_check)
\end{verbatim}
\normalsize
@@ -86,7 +86,7 @@ Use the following U-Boot command to do so, {\bf in just 1 line}
\begin{verbatim}
setenv bootargs root=/dev/nfs ip=192.168.0.100:::::eth0
- nfsroot=192.168.0.1:/home/<user>/embedded-linux-labs/tinysystem/nfsroot,nfsvers=3 rw
+ nfsroot=192.168.0.1:/home/<user>/__SESSION_NAME__-labs/tinysystem/nfsroot,nfsvers=3 rw
\end{verbatim}
Once again, replace \code{<user>} by your actual user name.
diff --git a/labs/sysdev-toolchain/sysdev-toolchain.tex b/labs/sysdev-toolchain/sysdev-toolchain.tex
index ec996ef3..5f52f4d0 100644
--- a/labs/sysdev-toolchain/sysdev-toolchain.tex
+++ b/labs/sysdev-toolchain/sysdev-toolchain.tex
@@ -11,7 +11,7 @@ After this lab, you will be able to:
\section{Setup}
-Go to the \code{$HOME/embedded-linux-labs/toolchain} directory.
+Go to the \code{$HOME/__SESSION_NAME__-labs/toolchain} directory.
\section{Install needed packages}
diff --git a/labs/sysdev-u-boot/sysdev-u-boot.tex b/labs/sysdev-u-boot/sysdev-u-boot.tex
index 6aef65a5..db7010e3 100644
--- a/labs/sysdev-u-boot/sysdev-u-boot.tex
+++ b/labs/sysdev-u-boot/sysdev-u-boot.tex
@@ -31,7 +31,7 @@ without having anything installed on it.
\section{Downloading Microchip's flashing tool}
-Go to the \code{~/embedded-linux-labs/bootloader} directory.
+Go to the \code{~/__SESSION_NAME__-labs/bootloader} directory.
We're going to use that fallback mode, and its associated tool,
\code{sam-ba}.
More information about the training-materials-updates
mailing list