From mboxrd@z Thu Jan  1 00:00:00 1970
From: Grant Edwards <grant.b.edwards@gmail.com>
Date: Tue, 26 Jun 2012 15:48:14 +0000 (UTC)
Subject: [Buildroot] Using Buildroot generated toolchain on different
 machine without Buildroot environment
References: <jscj4m$j2p$1@dough.gmane.org> <20120626171906.5ea51e6a@skate>
Message-ID: <jsclju$7qc$1@dough.gmane.org>
List-Id: <buildroot.busybox.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: buildroot@busybox.net

On 2012-06-26, Thomas Petazzoni <thomas.petazzoni@free-electrons.com> wrote:
> Le Tue, 26 Jun 2012 17:05:59 +0200,
> Aleksandar Zivkovic <Aleksandar.Zivkovic@rt-rk.com> a ??crit :
>
>> I'm trying to extract the toolchain generated by Buildroot in order to 
>> use it on other machines without Buildroot environment. Thought this is 
>> simple and did the following way:
>> * generate toolchain outside Buildroot (BR2_HOST_DIR="$(TOPDIR)/../host")
>> * use files from $(TOPDIR)/../host on other machine
>
> Did you install them at the exact same location on the other machine?
>
> For the moment, the toolchains generated by Buildroot are not
> relocatable, so they must be installed on the other machine at the
> same location they were generated on the initial build machine.

Toolchains built with crosstool-ng can be moved anywhere, but all you
end up with is the basic "libc" libraries.  You'll have to copy the
libraries built by buildroot manually if you want to use them on the
other hosts.

-- 
Grant Edwards               grant.b.edwards        Yow! The PILLSBURY DOUGHBOY
                                  at               is CRYING for an END to
                              gmail.com            BURT REYNOLDS movies!!