[FE training-materials-updates] Toolchains: correct ABI constraints

[Michael Opdenacker]

Repository : git://git.free-electrons.com/training-materials.git
On branch  : master
Link       : http://git.free-electrons.com/training-materials/commit/?id=8e99d25b9ab701a703669b9a79a38b915792d6a4

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

commit 8e99d25b9ab701a703669b9a79a38b915792d6a4
Author: Michael Opdenacker <michael.opdenacker at free-electrons.com>
Date:   Mon Jun 12 17:50:45 2017 +0200

    Toolchains: correct ABI constraints
    
    - It's too strong to say that all binaries in a filesystem should
      be compiled with the same ABI.
    - You could have static binaries (or even chroots) built with
      a different ABI.
    
    Don't hesitate to rephrase this if you think about a better way
    to express this!
    
    Signed-off-by: Michael Opdenacker <michael.opdenacker at free-electrons.com>


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

8e99d25b9ab701a703669b9a79a38b915792d6a4
 slides/sysdev-toolchains-options/sysdev-toolchains-options.tex | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/slides/sysdev-toolchains-options/sysdev-toolchains-options.tex b/slides/sysdev-toolchains-options/sysdev-toolchains-options.tex
index 82f608c..65675d5 100644
--- a/slides/sysdev-toolchains-options/sysdev-toolchains-options.tex
+++ b/slides/sysdev-toolchains-options/sysdev-toolchains-options.tex
@@ -8,7 +8,7 @@
     calling conventions (how function arguments are passed, how the
     return value is passed, how system calls are made) and the
     organization of structures (alignment, etc.)
-  \item All binaries in a system must be compiled with the same ABI,
+  \item All binaries in a system are typically compiled with the same ABI,
     and the kernel must understand this ABI.
   \item On ARM, two main ABIs: {\em OABI} and {\em EABI}
     \begin{itemize}