1.1 --- a/config/toolchain.in	Wed Aug 15 15:39:44 2007 +0000
     1.2 +++ b/config/toolchain.in	Wed Aug 15 16:18:35 2007 +0000
     1.3 @@ -74,9 +74,9 @@
     1.4      prompt "Vendor string"
     1.5      default "unknown"
     1.6      help
     1.7 -      Vendor part of the machine triplet.
     1.8 +      Vendor part of the target tuple.
     1.9        
    1.10 -      A triplet is of the form arch-vendor-kernel-system.
    1.11 +      A tuple is of the form arch-vendor-kernel-system.
    1.12        You can set the second part, vendor, to whatever you see fit.
    1.13        Use a single word, or use underscores "_" to separate words.
    1.14        
    1.15 @@ -88,7 +88,7 @@
    1.16      default ""
    1.17      help
    1.18        Normaly, you'd call your toolchain components (especially gcc) by
    1.19 -      prefixing the target triplet followed by a dash and the component name
    1.20 +      prefixing the target tuple followed by a dash and the component name
    1.21        (eg. armeb-unknown-linux-uclibc-gcc).
    1.22        
    1.23        You can enter here a sed expression to be applied to ${CT_TARGET} to
    1.24 @@ -107,7 +107,7 @@
    1.25      default ""
    1.26      help
    1.27        Normaly, you'd call your toolchain components (especially gcc) by
    1.28 -      prefixing the target triplet followed by a dash and the component name
    1.29 +      prefixing the target tuple followed by a dash and the component name
    1.30        (eg. armeb-unknown-linux-uclibc-gcc).
    1.31        
    1.32        You can enter a shortcut here. This string will be used to create
    1.33 @@ -167,7 +167,7 @@
    1.34  
    1.35  config BUILD 
    1.36      string
    1.37 -    prompt "Build system triplet"
    1.38 +    prompt "Build system tuple"
    1.39      default ""
    1.40      help
    1.41        Canonical name of the machine building the toolchain.
    1.42 @@ -187,7 +187,7 @@
    1.43  
    1.44  config HOST
    1.45      string
    1.46 -    prompt "Host system triplet"
    1.47 +    prompt "Host system tuple"
    1.48      default ""
    1.49      depends on NATIVE || CANADIAN
    1.50      help

     2.1 --- a/docs/ct-ng.1.in	Wed Aug 15 15:39:44 2007 +0000
     2.2 +++ b/docs/ct-ng.1.in	Wed Aug 15 16:18:35 2007 +0000
     2.3 @@ -49,7 +49,7 @@
     2.4  Save the current
     2.5  .B crosstool-NG
     2.6  configuration, and associated components' config files, into a sample. Samples
     2.7 -are saved in their own sub-directory, named after the target's triplet, in the
     2.8 +are saved in their own sub-directory, named after the target's tuple, in the
     2.9  .I samples
    2.10  sub-directory of the current directory.
    2.11  If that was not clear:
    2.12 @@ -57,7 +57,7 @@
    2.13  
    2.14  Samples can be later recalled by calling
    2.15  .B ct-ng
    2.16 -with the target triplet they represent.
    2.17 +with the target tuple they represent.
    2.18  ."
    2.19  .TP
    2.20  .B build
    2.21 @@ -149,7 +149,7 @@
    2.22  .IR /usr ),
    2.23  although
    2.24  .B crosstool-NG
    2.25 -will refuse to install in some well known critical directories.
    2.26 +will refuse to install toolchains in some well known critical directories.
    2.27  ."
    2.28  .SH AUTHORS
    2.29  .MTO "yann.morin.1998@anciens.enib.fr" "Yann E. MORIN" ""

     3.1 --- a/docs/overview.txt	Wed Aug 15 15:39:44 2007 +0000
     3.2 +++ b/docs/overview.txt	Wed Aug 15 16:18:35 2007 +0000
     3.3 @@ -164,7 +164,7 @@
     3.4  that you can use:
     3.5  
     3.6  CT_TARGET:
     3.7 -  It represents the target triplet you are building for. You can use it for
     3.8 +  It represents the target tuple you are building for. You can use it for
     3.9    example in the installation/prefix directory, such as:
    3.10      /opt/x-tools/${CT_TARGET}
    3.11  
    3.12 @@ -190,13 +190,13 @@
    3.13  
    3.14  CT_PREFIX_DIR:
    3.15    This is where the toolchain will be installed in (and for now, where it
    3.16 -  will run from). Common use it to add the target triplet in the directory
    3.17 +  will run from). Common use it to add the target tuple in the directory
    3.18    path, such as (see above):
    3.19      /opt/x-tools/${CT_TARGET}
    3.20  
    3.21  CT_TARGET_VENDOR:
    3.22    An identifier for your toolchain, will take place in the vendor part of the
    3.23 -  target triplet. It shall *not* contain spaces or dashes. Usually, keep it
    3.24 +  target tuple. It shall *not* contain spaces or dashes. Usually, keep it
    3.25    to a one-word string, or use underscores to separate words if you need.
    3.26    Avoid dots, commas, and special characters.
    3.27  
    3.28 @@ -297,6 +297,21 @@
    3.29  You can test-build all samples; simply call:
    3.30    ct-ng regtest
    3.31  
    3.32 +
    3.33 +Overriding the number of // jobs |
    3.34 +---------------------------------*
    3.35 +
    3.36 +If you want to override the number of jobs to run in // (the -j option to
    3.37 +make), you can either re-enter the menuconfig, or simply add it on the command
    3.38 +line, as such:
    3.39 +  ct-ng build.4
    3.40 +
    3.41 +which tells crosstool-NG to override the number of // jobs to 4.
    3.42 +
    3.43 +You can see the actions that support overriding the number of // jobs in
    3.44 +the help menu. Those are the ones with [.#] after them (eg. build[.#] or
    3.45 +regtest[.#], and so on...).
    3.46 +
    3.47  _______________________
    3.48                        /
    3.49  Using the toolchain  /
    3.50 @@ -306,19 +321,19 @@
    3.51  your PATH, such as:
    3.52    export PATH="${PATH}:/your/toolchain/path/bin"
    3.53  
    3.54 -and then using the target triplet to tell the build systems to use your
    3.55 +and then using the target tuple to tell the build systems to use your
    3.56  toolchain:
    3.57 -  ./configure --target=your-target-triplet
    3.58 +  ./configure --target=your-target-tuple
    3.59  or
    3.60 -  make CC=your-target-triplet-gcc
    3.61 +  make CC=your-target-tuple-gcc
    3.62  or
    3.63 -  make CROSS_COMPILE=your-target-triplet-
    3.64 +  make CROSS_COMPILE=your-target-tuple-
    3.65  and so on...
    3.66  
    3.67  When your root directory is ready, it is still missing some important bits: the
    3.68  toolchain's libraries. To populate your root directory with those libs, just
    3.69  run:
    3.70 -  your-target-triplet-populate -s /your/root -d /your/root-populated
    3.71 +  your-target-tuple-populate -s /your/root -d /your/root-populated
    3.72  
    3.73  This will copy /your/root into /your/root-populated, and put the needed and only
    3.74  the needed libraries there. Thus you don't polute /your/root with any cruft that

     4.1 --- a/scripts/crosstool.sh	Wed Aug 15 15:39:44 2007 +0000
     4.2 +++ b/scripts/crosstool.sh	Wed Aug 15 16:18:35 2007 +0000
     4.3 @@ -72,8 +72,8 @@
     4.4  
     4.5  CT_DoLog INFO "Building environment variables"
     4.6  
     4.7 -# Target triplet: CT_TARGET needs a little love:
     4.8 -CT_DoBuildTargetTriplet
     4.9 +# Target tuple: CT_TARGET needs a little love:
    4.10 +CT_DoBuildTargetTuple
    4.11  
    4.12  # Kludge: If any of the configured options needs CT_TARGET,
    4.13  # then rescan the options file now:

     5.1 --- a/scripts/functions	Wed Aug 15 15:39:44 2007 +0000
     5.2 +++ b/scripts/functions	Wed Aug 15 16:18:35 2007 +0000
     5.3 @@ -480,12 +480,12 @@
     5.4      fi
     5.5  }
     5.6  
     5.7 -# Compute the target triplet from what is provided by the user
     5.8 -# Usage: CT_DoBuildTargetTriplet
     5.9 +# Compute the target tuple from what is provided by the user
    5.10 +# Usage: CT_DoBuildTargetTuple
    5.11  # In fact this function takes the environment variables to build the target
    5.12 -# triplet. It is needed both by the normal build sequence, as well as the
    5.13 +# tuple. It is needed both by the normal build sequence, as well as the
    5.14  # sample saving sequence.
    5.15 -CT_DoBuildTargetTriplet() {
    5.16 +CT_DoBuildTargetTuple() {
    5.17      case "${CT_ARCH_BE},${CT_ARCH_LE}" in
    5.18          y,) target_endian_eb=eb; target_endian_el=;;
    5.19          ,y) target_endian_eb=; target_endian_el=el;;

     6.1 --- a/scripts/saveSample.sh	Wed Aug 15 15:39:44 2007 +0000
     6.2 +++ b/scripts/saveSample.sh	Wed Aug 15 16:18:35 2007 +0000
     6.3 @@ -18,8 +18,8 @@
     6.4  CT_TestOrAbort "Configuration file not found. Please create one." -f "${CT_TOP_DIR}/.config"
     6.5  . "${CT_TOP_DIR}/.config"
     6.6  
     6.7 -# Target triplet: CT_TARGET needs a little love:
     6.8 -CT_DoBuildTargetTriplet
     6.9 +# Target tuple: CT_TARGET needs a little love:
    6.10 +CT_DoBuildTargetTuple
    6.11  
    6.12  # Kludge: if any of the config options needs either CT_TARGET or CT_TOP_DIR,
    6.13  # re-parse them:

     7.1 --- a/scripts/tarball.sh.broken	Wed Aug 15 15:39:44 2007 +0000
     7.2 +++ b/scripts/tarball.sh.broken	Wed Aug 15 16:18:35 2007 +0000
     7.3 @@ -16,7 +16,7 @@
     7.4  # Parse the configuration file:
     7.5  . ${CT_TOP_DIR}/.config
     7.6  
     7.7 -CT_DoBuildTargetTriplet
     7.8 +CT_DoBuildTargetTuple
     7.9  
    7.10  # Kludge: if any of the config options needs either CT_TARGET or CT_TOP_DIR,
    7.11  # re-parse them: