[Buildroot] preserve toolchain

[Buildroot] preserve toolchain

[Marcus Osdoba]

  Hello mailinglist,

For a shorter development cycle I like to preserve the toolchain 
generated by buildroot for the next run. I naivly copied the 
output/toolchain to some other directory and set the toolchain directory 
in the buildroot config. The bin-directory does not include the 
gcc-binaries. Do I have to create links in the bin-directory to the gccs?

Is it possible to take the same toolchain for package build the next 
time? Can I recycle the toolchain generated by buildroot?

Thanks for any reply.

Regards,
Marcus

ossy at debian-virtual:~/buildroot/buildroot-dev$ make nano
/bin/sh: ../br_toolchain/toolchain-uclibc-gnueabi/bin/arm-linux-gcc: 
Datei oder Verzeichnis nicht gefunden

ossy at debian-virtual:~/buildroot/buildroot-dev$ ls -l 
../br_toolchain/toolchain-uclibc-gnueabi/
insgesamt 68
drwxr-xr-x  2 ossy ossy    16 11. Sep 17:01 bin
drwxr-xr-x 17 ossy ossy  4096 11. Sep 17:05 binutils-2.20.1
drwxr-xr-x 11 ossy ossy  4096 11. Sep 17:06 binutils-2.20.1-build
drwxr-xr-x 26 ossy ossy  4096 11. Sep 17:09 gcc-4.3.5
drwxr-xr-x 10 ossy ossy  4096 11. Sep 17:37 gcc-4.3.5-final
drwxr-xr-x  9 ossy ossy  4096 11. Sep 17:15 gcc-4.3.5-initial
drwxr-xr-x 10 ossy ossy  4096 11. Sep 17:23 gcc-4.3.5-intermediate
drwxr-xr-x  5 ossy ossy    41 11. Sep 17:04 gmp
drwxr-xr-x 15 ossy ossy  4096 11. Sep 17:01 gmp-4.2.4
drwxr-xr-x 15 ossy ossy  4096 11. Sep 17:04 gmp-4.2.4-host
drwxr-xr-x  3 ossy ossy    38 11. Sep 17:16 linux
drwxr-xr-x 23 ossy ossy  4096 11. Sep 17:16 linux-2.6.35.4
drwxr-xr-x  5 ossy ossy    42 11. Sep 17:05 mpfr
drwxr-xr-x  4 ossy ossy  8192 11. Sep 17:04 mpfr-2.4.1
drwxr-xr-x  5 ossy ossy 12288 11. Sep 17:05 mpfr-2.4.1-host
drwxr-xr-x 18 ossy ossy  4096 11. Sep 17:25 uClibc-0.9.31
drwxr-xr-x  4 ossy ossy    26 11. Sep 17:17 uClibc_dev

ossy at debian-virtual:~/buildroot/buildroot-dev$ ls -l 
../br_toolchain/toolchain-uclibc-gnueabi/bin
insgesamt 0
lrwxrwxrwx 1 ossy ossy 8 11. Sep 17:01 sed -> /bin/sed

[Buildroot] preserve toolchain

[Grant Edwards]

On 2010-09-14, Marcus Osdoba <marcus.osdoba@googlemail.com> wrote:

> For a shorter development cycle I like to preserve the toolchain 
> generated by buildroot for the next run.

I used to try to do that, and had many problems with it.  As a result,
I switched to using crosstool-ng to build the toolchain.

> I naivly copied the output/toolchain to some other directory and set
> the toolchain directory in the buildroot config. The bin-directory
> does not include the gcc-binaries. Do I have to create links in the
> bin-directory to the gccs?
>
> Is it possible to take the same toolchain for package build the next 
> time?

I managed to do it, but it required a number of customizations to the
external toolchain makefile, and there were still some minor issues
that required work-arounds in a shell-script that I was using to do
builds.  I eventually gave up and heeded the advice of the
maintainers: now I use crosstool-ng to build my external toolchain.

> Can I recycle the toolchain generated by buildroot?

Using crosstool-ng to build an external toolchain is the normal way of
accomplishing what you want to accomplish.

-- 
Grant Edwards               grant.b.edwards        Yow! Make me look like
                                  at               LINDA RONSTADT again!!
                              gmail.com            

[Buildroot] preserve toolchain

[Marcus Osdoba]

  Am 14.09.2010 20:45, schrieb Grant Edwards:
> On 2010-09-14, Marcus Osdoba<marcus.osdoba@googlemail.com>  wrote:
>
>> For a shorter development cycle I like to preserve the toolchain
>> generated by buildroot for the next run.
> I used to try to do that, and had many problems with it.  As a result,
> I switched to using crosstool-ng to build the toolchain.
>
>> I naivly copied the output/toolchain to some other directory and set
>> the toolchain directory in the buildroot config. The bin-directory
>> does not include the gcc-binaries. Do I have to create links in the
>> bin-directory to the gccs?
>>
>> Is it possible to take the same toolchain for package build the next
>> time?
> I managed to do it, but it required a number of customizations to the
> external toolchain makefile, and there were still some minor issues
> that required work-arounds in a shell-script that I was using to do
> builds.  I eventually gave up and heeded the advice of the
> maintainers: now I use crosstool-ng to build my external toolchain.
>
>> Can I recycle the toolchain generated by buildroot?
> Using crosstool-ng to build an external toolchain is the normal way of
> accomplishing what you want to accomplish.
>
Many thanks for this clear statement and field report! This saved much 
time for me.