patches/glibc/2.7/140-i386-preferred-stack-boundary.patch
author "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
Sun Sep 12 23:51:25 2010 +0200 (2010-09-12)
changeset 2123 ff2181adbd28
parent 744 4bf8448536d5
permissions -rw-r--r--
cc/gcc: disable complibs if not selected

Force gcc to not link with some companion libraries when
there are not needed (because selected-out).

There is no option to tell gcc *not* to build the Graphite and/or
LTO stuff. They *will* be built if gcc finds the suitable companion
libraries. If we do not provide them, but the host has them, then
gcc *will* find them, and link with them.

Consider the following:
- host has suitable PPL and CLooG (eg. Debian Squeeze)
- user wants to build gcc>=4.4
- user de-selects GRAPHITE
- gcc will find the hosts PPL and CLooG, and will use them
- the user moves the toolchain to an older host that does
not have them (eg. Debian Lenny)
- the toolchain fails, when it was properly setup not to

So, explicitly tell gcc *not* to use unneeded companion libs.

Signed-off-by: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
yann@434
     1
(C) 2007 Yann E. MORIN <yann.morin.1998@anciens.enib.fr>
yann@434
     2
License: LGPL v2.1
yann@434
     3
yann@434
     4
Shut off a stupid warning: preffered-stack-boundary must be between 4 ad 12,
yann@434
     5
and 2 is not.
yann@434
     6
yann@434
     7
diff -dur glibc-2.5.orig/sysdeps/i386/Makefile glibc-2.5/sysdeps/i386/Makefile
yann@434
     8
--- glibc-2.5.orig/sysdeps/i386/Makefile	2005-03-06 01:18:16.000000000 +0100
yann@434
     9
+++ glibc-2.5/sysdeps/i386/Makefile	2007-05-27 17:49:37.000000000 +0200
yann@434
    10
@@ -36,7 +36,7 @@
yann@434
    11
 ifeq ($(subdir),csu)
yann@434
    12
 sysdep-CFLAGS += -mpreferred-stack-boundary=4
yann@434
    13
 else
yann@434
    14
-sysdep-CFLAGS += -mpreferred-stack-boundary=2
yann@434
    15
+sysdep-CFLAGS += -mpreferred-stack-boundary=4
yann@434
    16
 # Likewise, any function which calls user callbacks
yann@434
    17
 uses-callbacks += -mpreferred-stack-boundary=4
yann@434
    18
 # Likewise, any stack alignment tests