All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael S. Zick <minimod@morethan.org>
To: buildroot@busybox.net
Subject: [Buildroot] buildroot stops at pango compilation
Date: Sun, 6 Nov 2011 10:02:04 -0600	[thread overview]
Message-ID: <201111061002.06143.minimod@morethan.org> (raw)
In-Reply-To: <CAC=eiqyLq=uBboFLHDNM=ph4m8aOHcZN8799BL+5arheYLbeHw@mail.gmail.com>

On Sun November 6 2011, Daniel Potapov wrote:
> On Sun, Nov 6, 2011 at 10:26 PM, Thomas Petazzoni
> <thomas.petazzoni@free-electrons.com> wrote:
> > Hello,
> >
> > Please do not reply to me directly, but to the list instead. Thanks!
> 
> Yep! Sorry, I forogot it...
> 
> > Your config uses the ARM OABI, can you try with ARM EABI, which is the
> > standard these days ?
> >
> 
> Ok, I've checked EABI in buildroot config and uclibc, but compilation
> fails with messages:
> make: /home/user/buildroot/buildroot-2011.08/output/host/usr/bin/arm-unknown-linux-uclibcgnueabi-gcc:
> Command not found
> make: *** [/home/user/buildroot/buildroot-2011.08/output/toolchain/uClibc-0.9.32/.configured]
> Error 127
> 
> where I can get arm-unknown-linux-uclibcgnueabi-gcc ?
> 
> 

Buildroot should have built it for you.
Did you do a 'make clean' ?

Mike

  reply	other threads:[~2011-11-06 16:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAC=eiqyR36E133EnLBVZNFWsHzx7ayg0Z=4rq2LWOpYE4xTaMw@mail.gmail.com>
2011-11-06 13:20 ` [Buildroot] buildroot stops at pango compilation Daniel Potapov
2011-11-06 13:38   ` Thomas Petazzoni
     [not found]     ` <CAC=eiqwhb=ZknTvjhHPquZ-hhtf6u50vNYn6Nc_EPp-ydMtCkQ@mail.gmail.com>
2011-11-06 15:26       ` Thomas Petazzoni
2011-11-06 15:52         ` Daniel Potapov
2011-11-06 16:02           ` Michael S. Zick [this message]
2011-11-06 16:06           ` Thomas Petazzoni
2011-11-06 16:09             ` Daniel Potapov
2011-11-07  7:32               ` Daniel Potapov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=201111061002.06143.minimod@morethan.org \
    --to=minimod@morethan.org \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.