Building toolchain for ARM 64bit as the target

[Anup Ghatage <ghatageanup at gmail dot com>]

Hello,

I've been trying to build the toolchain using crosstool-ng for ARM
64bit as the target.
I'm using crosstool-ng 1.20.0

Also here is some info about the host I'm building it on:
ghatage@ubuntu:~/crosstool-ng-1.20.0$ uname -a
Linux ubuntu 3.13.0-29-generic #53-Ubuntu SMP Wed Jun 4 21:00:20 UTC
2014 x86_64 x86_64 x86_64 GNU/Linux

Here is what I've done so far:

> ct-ng menuconfig
> Select Target Options
>> Target Architecture
>>> Selected arm
>> Selected Bitness to 64 bit
> Selected C-library, set it to use glibc

So I'm building the toolchain which has glibc (instead of eglibc) for
target ARM 64bit

-------------------------------------------------------------------
This is how it looks on the console
-------------------------------------------------------------------
ghatage@ubuntu:~/crosstool-ng-1.20.0$ ct-ng build
[INFO ]  Performing some trivial sanity checks
[INFO ]  Build started 20141113.012340
[INFO ]  Building environment variables
[INFO ]  =================================================================
[INFO ]  Retrieving needed toolchain components' tarballs
[INFO ]  Retrieving needed toolchain components' tarballs: done in
0.20s (at 00:13)
[INFO ]  =================================================================
[INFO ]  Extracting and patching toolchain components
[INFO ]  Extracting and patching toolchain components: done in 0.59s (at 00:14)
[INFO ]  =================================================================
[INFO ]  Installing GMP for host
[INFO ]  Installing GMP for host: done in 246.20s (at 04:20)
[INFO ]  =================================================================
[INFO ]  Installing MPFR for host
[INFO ]  Installing MPFR for host: done in 93.85s (at 05:54)
[INFO ]  =================================================================
[INFO ]  Installing ISL for host
[INFO ]  Installing ISL for host: done in 157.00s (at 08:31)
[INFO ]  =================================================================
[INFO ]  Installing CLooG for host
[INFO ]  Installing CLooG for host: done in 17.61s (at 08:48)
[INFO ]  =================================================================
[INFO ]  Installing MPC for host
[INFO ]  Installing MPC for host: done in 27.69s (at 09:16)
[INFO ]  =================================================================
[INFO ]  Installing binutils for host
[ERROR]    checking for strings.h... make[2]: *** [configure-binutils] Error 1
[ERROR]    make[2]: *** [configure-gas] Error 1
[ERROR]    make[1]: *** [all] Error 2
[ERROR]
[ERROR]  >>
[ERROR]  >>  Build failed in step 'Installing binutils for host'
[ERROR]  >>        called in step '(top-level)'
[ERROR]  >>
[ERROR]  >>  Error happened in: CT_DoExecLog[scripts/functions@257]
[ERROR]  >>        called from:
do_binutils_backend[scripts/build/binutils/binutils.sh@229]
[ERROR]  >>        called from:
do_binutils_for_host[scripts/build/binutils/binutils.sh@94]
[ERROR]  >>        called from: main[scripts/crosstool-NG.sh@638]
[ERROR]  >>
[ERROR]  >>  For more info on this error, look at the file: 'build.log'
[ERROR]  >>  There is a list of known issues, some with workarounds, in:
[ERROR]  >>      '/usr/local/share/doc/crosstool-ng/ct-ng.1.20.0/B -
Known issues.txt'
[ERROR]
[ERROR]  (elapsed: 10:37.77)
[10:39] / make: *** [build] Error 2
ghatage@ubuntu:~/crosstool-ng-1.20.0$

More info in the build log
-------------------------------------------------------------------
build.log
-------------------------------------------------------------------
[ALL  ]    checking if x86_64-build_unknown-linux-gnu-gcc supports -c
-o file.o... yes
[ALL  ]    checking if x86_64-build_unknown-linux-gnu-gcc supports -c
-o file.o... (cached) yes
[ALL  ]    checking whether the x86_64-build_unknown-linux-gnu-gcc
linker (x86_64-build_unknown-linux-gnu-ld -m elf_x86_64) supports
shared libraries... yes
[ALL  ]    checking whether -lc should be explicitly linked in... no
[ALL  ]    checking dynamic linker characteristics... GNU/Linux ld.so
[ALL  ]    checking how to hardcode library paths into programs... immediate
[ALL  ]    checking whether stripping libraries is possible... yes
[ALL  ]    checking if libtool supports shared libraries... yes
[ALL  ]    checking whether to build shared libraries... yes
[ALL  ]    checking whether to build static libraries... yes
[ALL  ]    Setting warning flags = -W -Wall -Wstrict-prototypes
-Wmissing-prototypes -Wshadow
[ALL  ]    checking whether byte ordering is bigendian... no
[ALL  ]    This target is no longer supported in gas
            <--- This seems to be the place where it fails
[ERROR]    make[2]: *** [configure-gas] Error 1
[ALL  ]    make[2]: Leaving directory
`/home/ghatage/crosstool-ng-1.20.0/.build/aarch64-unknown-linux-gnueabi/build/build-binutils-host-x86_64-build_unknown-linux-gnu'
[ERROR]    make[1]: *** [all] Error 2
[ALL  ]    make[1]: Leaving directory
`/home/ghatage/crosstool-ng-1.20.0/.build/aarch64-unknown-linux-gnueabi/build/build-binutils-host-x86_64-build_unknown-linux-gnu'
[ERROR]
[ERROR]  >>
[ERROR]  >>  Build failed in step 'Installing binutils for host'
[ERROR]  >>        called in step '(top-level)'
[ERROR]  >>
[ERROR]  >>  Error happened in: CT_DoExecLog[scripts/functions@257]
[ERROR]  >>        called from:
do_binutils_backend[scripts/build/binutils/binutils.sh@229]
[ERROR]  >>        called from:
do_binutils_for_host[scripts/build/binutils/binutils.sh@94]
[ERROR]  >>        called from: main[scripts/crosstool-NG.sh@638]
[ERROR]  >>
[ERROR]  >>  For more info on this error, look at the file: 'build.log'
[ERROR]  >>  There is a list of known issues, some with workarounds, in:
[ERROR]  >>      '/usr/local/share/doc/crosstool-ng/ct-ng.1.20.0/B -
Known issues.txt'
[ERROR]
[ERROR]  (elapsed: 10:37.77)

I checked the crosstool-ng website and the table where shows a '?' for
ARM 64 .. I'm guessing that it might be untested.. Is this the reason
why?
If so, has anyone had a successful build of the toolchain for ARM 64?
Any help / replies will be appreciated!

Regards,
Anup

--
For unsubscribe information see http://sourceware.org/lists.html#faq