Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » DSDP - Real-Time Software Components (RTSC) » Why were the arm syscalls removed XDC Tools v3.25.05.94?(Application linking fails with undefined references to _getpid and _kill)
Why were the arm syscalls removed XDC Tools v3.25.05.94? [message #1232895] Fri, 17 January 2014 20:45 Go to next message
Alexei Colin is currently offline Alexei Colin
Messages: 1
Registered: October 2013
Junior Member
In XDC Tools v3.25.03.72 there were several syscall definitions in gnu.targets.arm/syscalls.c, but all of them except _exit are no longer there in v3.25.05.94. The linker (arm-none-eabi-) complains about undefined _kill and _getpid. A workaround is to define those in the application source (by copying from syscalls.c in the previous version of XDC Tools).

What's the rationale for the change and what's a *good* way to adapt the application?
Re: Why were the arm syscalls removed XDC Tools v3.25.05.94? [message #1233986 is a reply to message #1232895] Mon, 20 January 2014 19:50 Go to previous message
Ashish Kapania is currently offline Ashish Kapania
Messages: 1
Registered: January 2014
Junior Member
Hi Alexie,

You can link with one of the BSP libraries that are shipped with GNU tools - libnosys.a or librdimon.a (if semi-hosting is enabled).

The syscalls lib present in older xdctools was identical to libnosys.a in GNU tools and so we decided to get rid of our syscalls lib in favor of using the BSP libraries from the tools.

We still have _exit syscall as there is a bug in CCS semihost support because of which it does not support semi-hosted _exit() call. Once that is fixed, we will remove _exit() also and get rid of syscalls.c from gnu targets.

Best,
Ashish
Previous Topic:XsScript debugging in Eclipse
Next Topic:GUI designer tool for XGCONF?
Goto Forum:
  


Current Time: Fri Aug 22 05:53:28 EDT 2014

Powered by FUDForum. Page generated in 0.01787 seconds