[Buildroot] Using Buildroot generated toolchain on different machine without Buildroot environment

[Buildroot] Using Buildroot generated toolchain on different machine without Buildroot environment

[Aleksandar Zivkovic]

Hi all,

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

To test my procedure I modified toolchainfile.cmake file with paths on 
other machine and started cmake -DCMAKE_TOOLCHAIN_FILE="..." .
Unfortunately this doesn't work :( cmake is not able to generate 
makefiles complaining on the following:
i686-linux-gcc: error trying to exec 'cc1': execvp: No such file or
   directory

Google shows posts on this problem but I have a feeling that I missed 
the idea on how to isolate toolchain for usage on other machines so 
would like to ask help from you.

Thank you in advance,
Aleksandar

[Buildroot] Using Buildroot generated toolchain on different machine without Buildroot environment

[Thomas Petazzoni]

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. We have
a TODO-list with the items that need to be fixed in order to make this
possible (that TODO-list was posted in the report of the February 2012
Buildroot Developers Meeting, if I remember correctly).

Regards,

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

[Buildroot] Using Buildroot generated toolchain on different machine without Buildroot environment

[Grant Edwards]

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!!

[Buildroot] Using Buildroot generated toolchain on different machine without Buildroot environment

[Thomas Petazzoni]

Le Tue, 26 Jun 2012 15:48:14 +0000 (UTC),
Grant Edwards <grant.b.edwards@gmail.com> a ?crit :

> 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.

Correct, but many things besides the toolchain contain hardcoded paths:
the pkg-config binary, the external toolchain wrapper, the .la files,
etc. See the report I mentioned for details.

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

[Buildroot] Using Buildroot generated toolchain on different machine without Buildroot environment

[Aleksandar Zivkovic]

On 26/06/2012 17:58, Thomas Petazzoni wrote:
> Le Tue, 26 Jun 2012 15:48:14 +0000 (UTC),
> Grant Edwards<grant.b.edwards@gmail.com>  a ?crit :
>
>> 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.
>
> Correct, but many things besides the toolchain contain hardcoded paths:
> the pkg-config binary, the external toolchain wrapper, the .la files,
> etc. See the report I mentioned for details.
>
> Thomas
Hi all,

@Thomas: when I used the same path on other machine build works 
correctly. Thanks again for quick response!

@Grant: I agree, besides libc I'm using complete generated host 
directory which holds other libraries that might be needed. Thanks for 
hint!

Regards,
Aleksandar