.version
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 1075 61bfa38f2174
child 1565 a32dc48671c3
child 1793 5cd3dd909770
child 1944 3a7ac3dd859d
child 2057 8398f0469d6a
child 2175 bde8f1be2511
child 2296 d18cc3da3879
child 2427 5a725fbda9e0
child 2582 7c5f0c6ddac1
child 2729 adc12224e93c
child 2863 1081af8ee469
child 2954 b005740d1473
child 3029 06cf4f81a5a2
child 3108 f36a98f63749
child 3177 47a7a813b589
child 3236 b83e6d31adba
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@1409
     1
hg