Re: crosstool-ng 1.18.0 build fails for armv6-rpi-linux-gnueabi

["Yann E. MORIN" <yann dot morin dot 1998 at free dot fr>]

Nuri, All,

On Thursday 07 March 2013 M. Nuri ERTEM wrote:
> I tried to build a toolchain for Raspberry Pi using the sample
> configuration 'armv6-rpi-linux-gnueabi' with crosstool-ng 1.18.0.
> 
> I modified only the target path (the '.config' file used is included
> in the attached zip).

You also unset the set-jump/long-jump option

> After building for about 110 minutes, the build failed with the
> following output:

Hmm. I just tried to rebuild that sample, and it builds here. I also used
your .config (except for the install path), and it builds OK, too. Weird...

I'll try to setup a Ubuntu 11.10 chroot-jail here and test in there...

> ...
> [ERROR]    /home/ertemn/Belgeler/toolchain/raspberrypi/.build/src/ppl-0.11.2/src/Variable.inlines.hh:43:
> undefined reference to `std::length_error::~length_error()'
[--SNIP--]

Smells like, but is not, an incorrect ppl version.

> As is evident from the attached .config file, the packages I used
> (which are also the defaults of the sample configuration
> 'armv6-rpi-linux-gnueabi') are:
> 
> binutils-2.22
> cloog-ppl-0.15.11
> eglibc-2_16
> eglibc-ports-2_16
> gcc-linaro-4.7-2013.01
> gmp-5.0.2
> linux-3.6.11
> mpc-0.9
> mpfr-3.1.0
> ppl-0.11.2 (also tried ppl-0.10.2 before: fails also)

Exactly the same as the sample... :-/

I'll see if I can reproduce in a Ubuntu jail...

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

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