scripts/build/arch/arm.sh
author Oron Peled <oron@actcom.co.il>
Mon Aug 03 00:49:25 2009 +0200 (2009-08-03)
branch1.4
changeset 1456 94fc77c37418
parent 903 9fb0f81b4416
child 1591 11460fc587e6
permissions -rw-r--r--
[complib:mpfr] Fix building MPFR in some weird cases

The tmul test uses a compiled-in input file in $(srcdir).
The problem is that the Makefile passes it unquoted. The C code
tries to stringify it using clever macros, which may *usually* work.

In my case the source directory was named:
.../toolchain-powerpc-e500v2-linux-gnuspe-1.0-2.fc10/.../tests
And guess what? During testing I found out the program fails because
it tries to open:
.../toolchain-powerpc-e500v2-1-gnuspe-1.0-2.fc10/.../tests

Yes, CPP tokenized the macro before stringifying it and not surprisingly
the 'linux' part was converted to 1.
[on Fedora-10: cpp (GCC) 4.3.2 20081105 (Red Hat 4.3.2-7)]

So the attached patch simplify the macros and pass the path as string
from the Makefile.

Manually backported from 1449:8ad2773e7ae3
     1 # Compute ARM-specific values
     2 
     3 CT_DoArchTupleValues() {
     4     # The architecture part of the tuple:
     5     CT_TARGET_ARCH="${CT_ARCH}${target_endian_eb}"
     6 
     7     # The system part of the tuple:
     8     case "${CT_LIBC},${CT_ARCH_ARM_EABI}" in
     9         *glibc,y)   CT_TARGET_SYS=gnueabi;;
    10         uClibc,y)   CT_TARGET_SYS=uclibcgnueabi;;
    11         none,y)     CT_TARGET_SYS=eabi;;
    12     esac
    13 
    14     # In case we're EABI, do *not* specify any ABI!
    15     # which means, either we do not have an ABI specified, or we're not EABI.
    16     CT_TestOrAbort "Internal error: CT_ARCH_ABI should not be set for EABI build." -z "${CT_ARCH_ABI}" -o -z "${CT_ARCH_ARM_EABI}"
    17 }