On 20 April 2012 22:26, Felipe Contreras <felipe.contre...@gmail.com> wrote: > Hi, > > I have been using CodeSourcery tool-chains since forever, and I > decided to try Linaro's tool-chain. So far I haven't had any issues, > except one: > > libgcc_s.so.1 is located in arm-linux-gnueabi/lib, which is not > available from arm-linux-gnueabi/libc. The CodeSourcer tool-chain has > all those files inside the 'libc' directory, which is useful for > Scratchbox2, because you need to specify a "target root" which is > basically the libc directory which acts in a similar fashion to /. > > I've managed to create a rule to workaround this issue, but I wonder > why are those files in that location, why not in 'libc/lib'?
Hi Felipe. There's three groups of files here: * The compiler supplied files (arm-linux-gnueabi/lib) which update with each release * The build root (arm-linux-gnueabi/libc) which has GLIBC and headers for building basic programs * The target root, which is the Linaro LEB installed on a device We've kept the compiler and build root separate to keep the compiler and distro supplied files apart and to make upgrading the build root easier. We plan to supply a kernel focused (think building perf) and desktop focused build root in the future. Installing will involve deleting the old libc and extracting the new one in place. Hope that helps, -- Michael _______________________________________________ linaro-toolchain mailing list linaro-toolchain@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-toolchain
