MobileRead Forums - View Single Post - Buildroot a linux 2.6.26-lab126 kernal. (3.3)

knc1 · 08-16-2012, 10:30 PM

NO - two different objectives being discussed here.

One - Twobob wants to build a current (e)glibc tool chain. For that, the link he had was to a 4.2 series compiler which is too old to build the current glibc.

Second - Duplicate the original build tools of lab126. For that, as provided on the KeK resource server:

Code:

core2quad bin $ pwd
/home/mszick/arm-2006q3/bin
core2quad bin $ ./arm-none-linux-gnueabi-gcc --version
arm-none-linux-gnueabi-gcc (CodeSourcery ARM Sourcery G++ 2006q3-26) 4.1.1

Which is the closest CodeSourcery release to what lab126 used for the K3 system.

- - - -

Plus - I haven't seen **why** he wants to drop using the gcc-4.6 series tool chain he was using - it builds kernel modules acceptible to the Amazon kernel build.

There might be some C++ interworking problems, but we haven't seen any examples of that (yet).

The runtime Ruby errors are not related to the compiler that was used.

But I am sure Twobob has a plan in mind, so there is the closest compiler, already "in stock".

08-16-2012, 10:30 PM	#54
knc1 Going Viral Posts: 17,212 Karma: 18210809 Join Date: Feb 2012 Location: Central Texas Device: No K1, PW2, KV, KOA	NO - two different objectives being discussed here. One - Twobob wants to build a current (e)glibc tool chain. For that, the link he had was to a 4.2 series compiler which is too old to build the current glibc. Second - Duplicate the original build tools of lab126. For that, as provided on the KeK resource server: Code: core2quad bin $ pwd /home/mszick/arm-2006q3/bin core2quad bin $ ./arm-none-linux-gnueabi-gcc --version arm-none-linux-gnueabi-gcc (CodeSourcery ARM Sourcery G++ 2006q3-26) 4.1.1 Which is the closest CodeSourcery release to what lab126 used for the K3 system. - - - - Plus - I haven't seen why he wants to drop using the gcc-4.6 series tool chain he was using - it builds kernel modules acceptible to the Amazon kernel build. There might be some C++ interworking problems, but we haven't seen any examples of that (yet). The runtime Ruby errors are not related to the compiler that was used. But I am sure Twobob has a plan in mind, so there is the closest compiler, already "in stock".