From mboxrd@z Thu Jan  1 00:00:00 1970
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Date: Tue, 18 Dec 2012 13:53:36 +0100
Subject: [Buildroot] Using a precompiled busybox toolchain as an
 external toolchain
In-Reply-To: <CAKvQZ_0sLwXqmGeTdeC6EBqqZ_FN4s6cVcnM3OwVrSHHYHfWDA@mail.gmail.com>
References: <CAKvQZ_0sLwXqmGeTdeC6EBqqZ_FN4s6cVcnM3OwVrSHHYHfWDA@mail.gmail.com>
Message-ID: <20121218135336.2e24d6bc@skate>
List-Id: <buildroot.busybox.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: buildroot@busybox.net

Dear Willy Lambert,

On Tue, 18 Dec 2012 13:42:07 +0100, Willy Lambert wrote:

> _ copy ouptut/host/usr in ${MY_TOOLCHAIN_PATH}

No, this will not work. The toolchain produced by Buildroot is not
relocatable.

Instead, set BR2_HOST_DIR to ${MY_TOOLCHAIN_PATH}, and then do your
toolchain build. The toolchain will be installed in
${MY_TOOLCHAIN_PATH}, and you can use it as an external toolchain for
other Buildroot builds.

Best regards,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com