Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Waldemar Brodkorb <wbx@openadk.org>
To: buildroot@busybox.net
Subject: [Buildroot] How to deploy Buildroot's crosscompile toolchain???
Date: Sun, 5 Oct 2014 08:38:35 +0200	[thread overview]
Message-ID: <20141005063835.GH7164@waldemar-brodkorb.de> (raw)
In-Reply-To: <1412490777.5471.YahooMailNeo@web122103.mail.ne1.yahoo.com>

Hi,
Tal Lubko wrote,

> Hi
> 
> I've wanted to ask what is the right way to build and deploy Buildroot's 
> toolchain to other machines?
> These machines don't have Buildroot to build the toolchain.
> 
> Currently (being ignorant about the right way to do it), after building the 
> toolcahin, I'm just making a tar of output/host and copy it to other machine.
> There I'm untarring it to some directory and starting to cross compile...
> 
> Things seemed to be working when I've worked with an External toolchain (
> Sourcery CodeBench). However when I've switched to Buildroot's toolchain, I got
> a message about missing libmpc.so.3. Then I've started to wonder what is the
> right way to build and deploy the toolchain.
> 
> When I run "gcc -v"
> I get a lot parameters like prefix, sysroot and more that show the directory it
> was build in:
> /home/tal/buildroot/2014.08/...
> 
> Which leads me again to think that I'm doing something wrong...
> Any help will be appreciated.

I am not 100% sure, but I think buildroot internal toolchains are
not relocatable. At least not via a relative sysroot directory.

best regards
 Waldemar

  reply	other threads:[~2014-10-05  6:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-05  6:32 [Buildroot] How to deploy Buildroot's crosscompile toolchain??? Tal Lubko
2014-10-05  6:38 ` Waldemar Brodkorb [this message]
2014-10-05  8:07   ` Tal Lubko
2014-10-05  9:50 ` Peter Kuemmel
2014-10-05 12:35   ` Tal Lubko
2014-10-05 14:25     ` Matthew Weber

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=20141005063835.GH7164@waldemar-brodkorb.de \
    --to=wbx@openadk.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox