All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marco Trapanese <marcotrapanese@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] Few questions external toolchain
Date: Tue, 25 Feb 2014 11:17:54 +0100	[thread overview]
Message-ID: <530C6DD2.4070605@gmail.com> (raw)
In-Reply-To: <530B8CEA.90306@gmail.com>


After digging a bit more I found the following:

ls -l ~/dev/buildroot/output/host/usr/bin/*gcc

lrwxrwxrwx 1 marco marco     21 feb 25 11:00 arm-fsl-linux-gnueabi-gcc 
-> ext-toolchain-wrapper
-rwxr-xr-x 1 marco marco   5908 feb 25 11:00 ext-toolchain-wrapper


./arm-fsl-linux-gnueabi-gcc
arm-fsl-linux-gnueabi-gcc: fatal error: no input files

it's ok, but:

./ext-toolchain-wrapper
/home/marco/dev/fsl-linaro-toolchain/bin/ext-toolchain-wrapper: No such 
file or directory

I don't understand this behavior and I didn't find any information about 
in the documentation. Did I searched wrong?
Thanks
Marco


Il 24/02/2014 19:18, Marco Trapanese ha scritto:
> Hello,
> after reading the documentation I still have some questions.
> I want to use a Linaro toolchain for an imx6 board.
>
> The toolchain is hosted on a git repository, and I don't understand 
> how to tell this to buildroot. It seems it looks for a tar.gz file.
>
> Anyway I tried to manually git clone the toolchain and I passed the 
> directory of the local repo.
> When it tries to compile something it returns:
>
> checking for arm-buildroot-linux-gnueabi-gcc... 
> /home/marco/dev/buildroot/output/host/usr/bin/arm-fsl-linux-gnueabi-gcc
> checking whether the C compiler works... no
> configure: error: in 
> `/home/marco/dev/buildroot/output/build/alsa-lib-1.0.26':
>
> the path is correct, but why it looks for 
> "arm-buildroot-linux-gnueabi-gcc"? It seems the internal toolchain!
>
> Attached there is my .config file and the buildroot version is: 
> 2014.02-rc2
>
> Thanks!
> Marco
>
>

  reply	other threads:[~2014-02-25 10:17 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-24 18:18 [Buildroot] Few questions external toolchain Marco Trapanese
2014-02-25 10:17 ` Marco Trapanese [this message]
2014-02-25 13:10   ` Thomas De Schampheleire
2014-02-25 13:34     ` Marco Trapanese
2014-02-25 14:11   ` Thomas De Schampheleire
2014-02-26 16:53     ` Marco Trapanese
2014-02-26 19:42       ` Thomas De Schampheleire
2014-02-26 19:53         ` Marco Trapanese
2014-02-26 21:47       ` Arnout Vandecappelle
2014-02-26 22:46         ` Marco Trapanese
2014-03-17 14:59           ` Thomas De Schampheleire

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=530C6DD2.4070605@gmail.com \
    --to=marcotrapanese@gmail.com \
    --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.