# Newlib libc.a versus libnosys.a to provide own syscalls.c

**URL:** <https://community.sparkfun.com/t/newlib-libc-a-versus-libnosys-a-to-provide-own-syscalls-c/9068>\
**Category:** MicroMod\
**Tags:** arm-lpc\
**Created:** [November 16, 2008, 2:47pm UTC](https://community.sparkfun.com/t/newlib-libc-a-versus-libnosys-a-to-provide-own-syscalls-c/9068 "2008-11-16T14:47:41Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![pieterc](https://avatars.discourse-cdn.com/v4/letter/p/edb3f5/32.png) [@pieterc](https://community.sparkfun.com/u/pieterc)\
**Post date:** [November 16, 2008, 2:47pm UTC](https://community.sparkfun.com/t/newlib-libc-a-versus-libnosys-a-to-provide-own-syscalls-c/9068/1 "2008-11-16T14:47:41Z")

</div>

Hi Everyone,

Can anyone point me to official documentation that describes how libnosys.a is supposed to be used?

I am using the Yagarto ARM toolchain with Newlib (libc.a) that is compiled with a SWI version of syscalls.o. I do not want to manually strip out syscalls.o from libc.a each time a new version is released. Is there an elegant way of providing your own syscalls interface and using libc.a?

Thanks and best regards,

Pieter