scripts/build/tools/000-template.sh
author "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
Tue Oct 14 17:42:10 2008 +0000 (2008-10-14)
changeset 929 7c958fb04f28
parent 664 6d151993e980
child 1112 c72aecd1a9ef
permissions -rw-r--r--
Sample config for e500v2 toolchain

On Tuesday 14 October 2008 17:05:31 Nate Case wrote:
> This is a sample config file for Freescale e500v2 processors (e.g.,
> MPC8548, MPC8572). It uses eglibc (for e500/SPE patches) and a recent
> gcc (4.3.1, for e500v2 DPFP support) and will generate appropriate
> dual-precision floating point instructions by default.
>
> Note: If building a Linux kernel with this toolchain, you will want to
> make sure -mno-spe AND -mspe=no are passed to gcc to prevent SPE
> ABI/instructions from getting into the kernel (which is currently
> unsupported). At this time, the kernel build system only passes
> -mno-spe by default (this should be fixed soon hopefully).
>
> A binutils snapshot is used to fix a bug present in 2.18 preventing
> U-Boot from being compiled (CodeSourcery issue #2297: internal.h
> (ELF_IS_SECTION_IN_SEGMENT): Adjust to cope with segments at the end of
> memory).

Obsoletes the powerpc-unknown-linux-gnuspe sample, so remove it.

/trunk/samples/powerpc-e500v2-linux-gnuspe/crosstool.config | 307 307 0 0 +++++++++++++++++++
1 file changed, 307 insertions(+)
yann@479
     1
# Template file for a tool utility
yann@479
     2
yann@479
     3
# Small function to print the filename
yann@479
     4
# Note that this function gets redefined over and over again for each tool.
yann@479
     5
# It's of no use when building the toolchain proper, but shows all its
yann@479
     6
# usefullness when saving the toolchain and building the tarball.
yann@479
     7
# Echo the name of the file, without the extension, below.
yann@479
     8
do_print_filename() {
yann@479
     9
    # For example:
yann@479
    10
    # echo "foobar-${CT_FOOBAR_VERSION}"
yann@479
    11
    :
yann@479
    12
}
yann@479
    13
yann@479
    14
# Put your download code here
yann@479
    15
do_tools_foobar_get() {
yann@479
    16
    # For example:
yann@479
    17
    # CT_GetFile "foobar-${CT_FOOBAR_VERSION}" http://foobar.com/releases/
yann@479
    18
    :
yann@479
    19
}
yann@479
    20
yann@479
    21
# Put your extract code here
yann@479
    22
do_tools_foobar_extract() {
yann@479
    23
    # For example:
yann@479
    24
    # CT_ExtractAndPatch "foobar-${CT_FOOBAR_VERSION}"
yann@479
    25
    :
yann@479
    26
}
yann@479
    27
yann@479
    28
# Put your build code here
yann@479
    29
do_tools_foobar_build() {
yann@479
    30
    # For example:
yann@479
    31
    # mkdir -p "${CT_BUILD_DIR}/build-foobar"
yann@479
    32
    # CT_Pushd "${CT_BUILD_DIR}/build-foobar"
yann@664
    33
    # CT_DoExecLog ALL                                        \
yann@479
    34
    # "${CT_SRC_DIR}/foobar-${CT_FOOBAR_VERSION}/configure"   \
yann@479
    35
    #     --build=${CT_BUILD}                                 \
yann@479
    36
    #     --host=${CT_TARGET}                                 \
yann@479
    37
    #     --prefix=/usr                                       \
yann@479
    38
    #     --foobar-options
yann@664
    39
    # CT_DoExecLog ALL make
yann@664
    40
    # CT_DoExecLog ALL make DESTDIR="${CT_SYSROOT_DIR}" install
yann@479
    41
    # CT_Popd
yann@479
    42
    :
yann@479
    43
}
yann@479
    44