Mercurialcrosstool-ng / file revision
summary | shortlog | changelog | graph | tags | branches | files | changeset | file | latest | revisions | annotate | diff | raw | help
docs/7 - Contributing to crosstool-NG.txt
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 2076 b58109b7b321
child 2563 e17f35b05539
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> 
     1 File.........: 7 - Contributing to crosstool-NG.txt

     2 Copyrigth....: (C) 2010 Yann E. MORIN <yann.morin.1998@anciens.enib.fr>

     3 License......: Creative Commons Attribution Share Alike (CC-by-sa), v2.5

     4 

     5 

     6 Contributing to crosstool-NG  /

     7 _____________________________/

     8 

     9 

    10 Sending a bug report |

    11 ---------------------+

    12 

    13 If you need to send a bug report, please send a mail with subject

    14 prefixed with "[CT_NG]" with to following destinations:

    15     TO: yann.morin.1998 (at) anciens.enib.fr

    16     CC: crossgcc (at) sourceware.org

    17 

    18 

    19 Sending patches |

    20 ----------------+

    21 

    22 If you want to enhance crosstool-NG, there's a to-do list in the TODO file.

    23 

    24 Patches should come with the appropriate SoB line. A SoB line is typically

    25 something like:

    26    Signed-off-by: John DOE <john.doe@somewhere.net>

    27 

    28 The SoB line is clearly described in Documentation/SubmittingPatches , section

    29 12, of your favourite Linux kernel source tree.

    30 

    31 

    32 For larger or more frequent contributions, mercurial should be used.

    33 There is a nice, complete and step-by-step tutorial in section 'C'.
crosstool-ng