[Buildroot] [USER] buildroot install external toolchains

[Buildroot] [USER] buildroot install external toolchains

[Steve Calfee]

?Hi,
I am trying to use docker to cross build buildroot. I don't want to build
the toolchain so I tried to use a pre-built toolchain as the autobuilders
do. I got a list of toolchains from
https://sourceware.org/ml/crossgcc/2015-05/msg00014.html written by Thomas
P.

So I extracted one into the filesystem and tried to use it, but something
is wrong. ?

From bash I tried:
/br/armv7-ctng-linux-gnueabihf/bin/armv7-ctng-linux-gnueabihf-gcc --version
bash: /br/armv7-ctng-linux-gnueabihf/bin/armv7-ctng-linux-gnueabihf-gcc: No
such file or directory

from buildroots base directory:

ls -l /br/armv7-ctng-linux-gnueabihf/bin/armv7-ctng-linux-gnueabihf-gcc
-rwxr-xr-x 2 br br 562548 Apr 18  2014
/br/armv7-ctng-linux-gnueabihf/bin/armv7-ctng-linux-gnueabihf-gcc

make
>>> toolchain-external undefined Configuring
Cannot execute cross-compiler
'/br/armv7-ctng-linux-gnueabihf/bin/armv7-ctng-linux-gnueabihf-gcc'


So I conclude that just extracting the archive is not enough. What do I
need to do to use a prebuild toolchain?

Thanks, Steve
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20160111/ccb6465d/attachment.html>

[Buildroot] [USER] buildroot install external toolchains

[Baruch Siach]

Hi Steve,

On Mon, Jan 11, 2016 at 08:55:34PM -0800, Steve Calfee wrote:
> I am trying to use docker to cross build buildroot. I don't want to build
> the toolchain so I tried to use a pre-built toolchain as the autobuilders
> do. I got a list of toolchains from
> https://sourceware.org/ml/crossgcc/2015-05/msg00014.html written by Thomas
> P.
> 
> So I extracted one into the filesystem and tried to use it, but something
> is wrong.
> 
> From bash I tried:
> /br/armv7-ctng-linux-gnueabihf/bin/armv7-ctng-linux-gnueabihf-gcc --version
> bash: /br/armv7-ctng-linux-gnueabihf/bin/armv7-ctng-linux-gnueabihf-gcc: No
> such file or directory

The 'No such file or directory' error might indicate missing libraries. This 
toolchain is built to run on 32bit x86 systems. Make sure you have 32bit 
versions of libc and libstdc++ packages installed on your system.

baruch

-- 
     http://baruch.siach.name/blog/                  ~. .~   Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
   - baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -

[Buildroot] [USER] buildroot install external toolchains

[Steve Calfee]

Hi Baruch,

Hi Baruch,

On Mon, Jan 11, 2016 at 11:49 PM, Baruch Siach <baruch@tkos.co.il> wrote:
>
> Hi Steve,
>
> On Mon, Jan 11, 2016 at 08:55:34PM -0800, Steve Calfee wrote:
> > I am trying to use docker to cross build buildroot. I don't want to build
> > the toolchain so I tried to use a pre-built toolchain as the autobuilders
> > do. I got a list of toolchains from
> > https://sourceware.org/ml/crossgcc/2015-05/msg00014.html written by Thomas
> > P.
> >
> > So I extracted one into the filesystem and tried to use it, but something
> > is wrong.
> >
> > From bash I tried:
> > /br/armv7-ctng-linux-gnueabihf/bin/armv7-ctng-linux-gnueabihf-gcc --version
> > bash: /br/armv7-ctng-linux-gnueabihf/bin/armv7-ctng-linux-gnueabihf-gcc: No
> > such file or directory
>
> The 'No such file or directory' error might indicate missing libraries. This
> toolchain is built to run on 32bit x86 systems. Make sure you have 32bit
> versions of libc and libstdc++ packages installed on your system.
>
>


Thanks, I did not know they were 32 bit apps. So I installed those
libraries and the toolchains now work in a docker container.

I am still struggling with getting persistent storage working - Stuff
like customization, builds and downloads should be persistent. However
when done it will make it much easier to setup a build system.

Regards, Steve