I notice that in your gcc version of the Arm Toolchain you use uclibc as the c library. Is there any reason for this ? This is the normal choice for uclinux targets but not standalone. The reason I ask is uclibc library falls under LGPL license which can cause issues if statically linking your application. Regards sjo
But even with statically linked LGPL lib such as uclibc you have to provide the end user the obj files so they can relink to a newer uclibc if they so wish. Obviously not a problem with shared libs. Unless my understanding is incorrect. Regards sjo