I successfully built a u-boot, kernel, and filesystem using the external Linaro toolchain (4.7-2013.03) mentioned in the Sitara SDK download page here:
which in turn points to the Linaro toolchain here:
That solution has been working solidly for over a year on top of the "Danny" branch of Arago.
However now I'm trying to port a new library that uses new C++ features only available in GCC-4.8 and have run into a problem.
The new Linaro GCC-4.8 toolchain came from here:
When I dropped that new toolchain into my arago system and completely rebuilt (deleted all existing build artifacts and state), the kernel starts to boot, but init.sysvinit fails to load because of a library problem:
## Booting kernel from Legacy Image at 80007fc0 ...
Image Name: Linux-3.2.0-AM335XPSP_04.06.00.1
Image Type: ARM Linux Kernel Image (uncompressed)
...
OK
Starting kernel ...
[ 0.105621] _omap_mux_init_gpio: Could not set gpio83
[ 0.126007] _omap_mux_init_gpio: Could not set gpio106
[ 0.304199] mtdoops: mtd device (mtddev=name/number) must be supplied
/sbin/init: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory
[ 0.715057] Kernel panic - not syncing: Attempted to kill init!
[ 0.721282] Backtrace:
...
While the message says "No such file or directory, it does exist, but it appears the problem is rather a segfault or library load problem.
I tried building a clean image from the "Dora" branch of Arago as well - which seems to support GCC-4.8, and it exhibits the same issue (but does not with the 4.7 GCC).
I don't feel like I understand the details of how the myriad different builds of GCC are special, but I'm wondering if anyone has used the Sitara/Arago SDK with the GCC-4.8 Linaro toolchain successfully? If so, how? Is there some TI-specific customization that is in the original Linaro 4.7 toolchain missing in 4.8?
Thanks in advance!
Brad