config/kernel/bare-metal.in
author |
"Yann E. MORIN" <yann.morin.1998@free.fr> |
|
Tue May 08 18:31:10 2012 +0200 (2012-05-08) |
changeset 2964 |
d48c03998dc1 |
parent 1030 |
e5bf882d6514
|
permissions |
-rw-r--r-- |
scripts: fix catching failures
POSIX 1003.1-2008 does not say whether "set -e" should catch a sub-shell
that exits with !0 (it has a list of conditions to catch, but no list of
conditions not to catch, and this situation is not listed).
bash-3 does not catch such a failure, but bash-4 does. That why, on my
Squeeze system I did not see the issue, while Thomas did on is Lenny chroot.
Reported-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
yann@861
|
1 |
# Bare metal config options
|
yann@861
|
2 |
|
yann@2444
|
3 |
## select BARE_METAL
|
yann@2444
|
4 |
##
|
yann@2444
|
5 |
## help 'Bare metal' refers to those programs that run without any kernel.
|
yann@2444
|
6 |
## help
|
yann@2444
|
7 |
## help You probably want to say 'y' here if you plan to use your compiler
|
yann@2444
|
8 |
## help to build bootloaders. It is not yet suitable to build Linux kernels,
|
yann@2444
|
9 |
## help though, because the APCI stuff relies on the target C library headers
|
yann@2444
|
10 |
## help being available?!?!...
|