patches/gcc/4.2.1/180-c99-snprintf.patch
| author |
"Yann E. MORIN" <yann.morin.1998@free.fr> |
|
Tue May 08 18:31:10 2012 +0200 (2012-05-08) |
| changeset 2964 |
d48c03998dc1 |
| parent 313 |
2f223aafc7cb
|
| 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@313
|
1 |
diff -durN gcc-4.2.1.orig/libstdc++-v3/include/c_std/std_cstdio.h gcc-4.2.1/libstdc++-v3/include/c_std/std_cstdio.h
|
|
yann@313
|
2 |
--- gcc-4.2.1.orig/libstdc++-v3/include/c_std/std_cstdio.h 2006-12-07 10:33:51.000000000 +0100
|
|
yann@313
|
3 |
+++ gcc-4.2.1/libstdc++-v3/include/c_std/std_cstdio.h 2007-08-03 20:33:24.000000000 +0200
|
|
yann@313
|
4 |
@@ -144,7 +144,7 @@
|
|
yann@313
|
5 |
|
|
yann@313
|
6 |
_GLIBCXX_END_NAMESPACE
|
|
yann@313
|
7 |
|
|
yann@313
|
8 |
-#if _GLIBCXX_USE_C99
|
|
yann@313
|
9 |
+#if _GLIBCXX_USE_C99 || defined(__UCLIBC__)
|
|
yann@313
|
10 |
|
|
yann@313
|
11 |
#undef snprintf
|
|
yann@313
|
12 |
#undef vfscanf
|