Hi @Chakradhar
The issue looks to be the Eevironment for lib path is not set. Set the environment for lib path as below example:
For Linux
export CC_LIB=<path to cross-compiler library>
export CC_LIB=/home/<username>/NXP/S32DS.3.4/S32DS/build_tools/gcc_v9.2/gcc-9.2-arm32-eabi/arm-none-eabi/newlib
For Windows
export CC_LIB=<path to cross-compiler library>
export CC_LIB=/C/nxp/S32DS.3.4/S32DS/build_tools/gcc_v9.2/gcc-9.2-arm32-eabi/arm-none-eabi/newlib
Choose the 32 bit or 64 bit tool-chain lib path as gcc-9.2-arm32-eabi OR gcc-9.2-arm64-eabi.
You can also see nano.specs file exists at location:
S32DS.3.4/S32DS/build_tools/gcc_v9.2/gcc-9.2-arm32-eabi/arm-none-eabi/newlib/lib/
Also, as I mentioned before the SAF85XX is not a mass-market device, I am not able to check or verify any information due to the security level when working with automotive parts such as this. Could you please contact the person that provided you with the device for further support on this part?