topic Re: S32DS for PA 2017.R1 can't support gcc --no-as-need option in S32 Design Studio

S32DS for PA 2017.R1 can't support gcc --no-as-need option

wesleyxie — Sat, 30 Dec 2017 16:58:57 GMT

Hi, Dear NXP guys

as below screenshot, when I specified "--no-as-need" in S32DS C Compiler settings,

the powerpc-eabivle-gcc.exe told me that it can NOT recognized this option.

I have to fix some lib link order issue by using this gcc option.

how can I archive this ? or is there other ways that S32DS supported ?

Re: S32DS for PA 2017.R1 can't support gcc --no-as-need option

jiri_kral — Tue, 02 Jan 2018 09:25:58 GMT

Hi,

the "no-as-needed" is linker (ld) option and can be added into linker settings:

Jiri

Re: S32DS for PA 2017.R1 can't support gcc --no-as-need option

wesleyxie — Mon, 15 Jan 2018 10:19:33 GMT

Hi,

I tried both the "--no-as-need" and "--no-as-needed" option in Linker, but seem neither of them work.

1. put fmc_bsp_os lib before fmc_sm, build project, many "undefined reference to FmcBspXxxx" error, those FmcBspXxxx functions should be already in fmc_bsp_os lib.

2. put fmc_bsp_os after fmc_sm, the "undefined reference to FmcBspXxxx" disappeared,

this means that FmcBspXxxx exist in fmc_bsp lib,

but the linker can not find it if the fmc_bsp_os lib is located before fmc_sm lib (no matter that --no-as-need is added or not).

Re: S32DS for PA 2017.R1 can't support gcc --no-as-need option

jiri_kral — Mon, 15 Jan 2018 15:00:46 GMT

Hi,

I'm assuming that the error is not related to any linker option. Can you please share your project here or you can send it on jiri.kral@nxp.com ?

Jiri