pushing the limits: armeb with new components

["Robert P. J. Day" <rpjday at crashcourse dot ca>]

  i'm going to be pushing the envelope today, seeing how well really
new software components work with CT-ng.  and here's the first
misstep, trying to build an armeb toolchain with glibc:

...
[INFO ]  Extracting and patching toolchain components
[EXTRA]    Extracting "linux-2.6.24.2"
[EXTRA]    Patching "linux-2.6.24.2"
[EXTRA]    Extracting "binutils-2.18"
[EXTRA]    Patching "binutils-2.18"
[EXTRA]    Extracting "gcc-4.2.3"
[EXTRA]    Patching "gcc-4.2.3"
[EXTRA]    Extracting "glibc-2.6.1"
[EXTRA]    Patching "glibc-2.6.1"
[EXTRA]    Extracting "glibc-ports-2.6.1"
[EXTRA]    Patching "glibc-ports-2.6.1"
[EXTRA]    Extracting "duma-2_5_1"
[EXTRA]    Patching "duma-2_5_1"
[EXTRA]    Extracting "gdb-6.6"
[EXTRA]    Patching "gdb-6.6"
[EXTRA]    Extracting "strace-4.5.15"
[EXTRA]    Patching "strace-4.5.15"
[INFO ]  Extracting and patching toolchain components: done in 255.38s
...
[INFO ]  Installing C library headers
[EXTRA]    Configuring C library
[ERROR]    configure: error: Need linker with .init_array/.fini_array support.
[ERROR]    Build failed in step "Installing C library headers"
...

  before i start collecting up voluminous log files, is there a simple
fix to the above?  has anyone seen it before?  thanks.

rday
--

========================================================================
Robert P. J. Day
Linux Consulting, Training and Annoying Kernel Pedantry:
    Have classroom, will lecture.

http://crashcourse.ca                          Waterloo, Ontario, CANADA
========================================================================

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