Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] [USER] buildroot install external toolchains
Date: Tue, 12 Jan 2016 09:49:38 +0200	[thread overview]
Message-ID: <20160112074938.GB1937@tarshish> (raw)
In-Reply-To: <CAJJ6jxvGYN8Pd-8GwzVHSZWKc2CpsNE47Xb23EF-m0_ZFVS7Ew@mail.gmail.com>

Hi Steve,

On Mon, Jan 11, 2016 at 08:55:34PM -0800, Steve Calfee wrote:
> I am trying to use docker to cross build buildroot. I don't want to build
> the toolchain so I tried to use a pre-built toolchain as the autobuilders
> do. I got a list of toolchains from
> https://sourceware.org/ml/crossgcc/2015-05/msg00014.html written by Thomas
> P.
> 
> So I extracted one into the filesystem and tried to use it, but something
> is wrong.
> 
> From bash I tried:
> /br/armv7-ctng-linux-gnueabihf/bin/armv7-ctng-linux-gnueabihf-gcc --version
> bash: /br/armv7-ctng-linux-gnueabihf/bin/armv7-ctng-linux-gnueabihf-gcc: No
> such file or directory

The 'No such file or directory' error might indicate missing libraries. This 
toolchain is built to run on 32bit x86 systems. Make sure you have 32bit 
versions of libc and libstdc++ packages installed on your system.

baruch

-- 
     http://baruch.siach.name/blog/                  ~. .~   Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
   - baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -

  reply	other threads:[~2016-01-12  7:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-12  4:55 [Buildroot] [USER] buildroot install external toolchains Steve Calfee
2016-01-12  7:49 ` Baruch Siach [this message]
2016-01-13 15:25   ` Steve Calfee

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=20160112074938.GB1937@tarshish \
    --to=baruch@tkos.co.il \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox