-z linker option in v6.1.19

Nitin Manohar said:

I was using linker option '-z' which doesn't seems to be supported in 6.1.19

The -z option is supported in all versions of codegen tools. It is an option passed to the shell which tells it to run the linker using the options following -z.
Are you running this on a command line, and if so, what does your command line look like and what is the error?

For the undefined symbol error, did you make sure to link in the appropriate runtime library for the device you are using? This post which talks about a related error might be helpful.

Thanks for the reply.

I've ensured that I'm linking with 6.1.19 supplied libraries.

I'm still using BIOS 5.20.05 version and its libraries. Could this be an issue?

Nitin,

Could you post the complete command line used for the build (both compile and link steps) and errors generated?
If it is a BIOS project, the runtime libs are automatically pulled in by BIOS. Did you check the cfg.cmd file generated by BIOS to ensure that the correct rts lib is being linked in?

Compilation:

c:\CCStudio_v3.1\6.1.19\bin\cl6x -g -pdr -pdv -pden -o3 -I.  -Ic:\CCStudio_v3.1\6.1.19\include -Ic:\CCStudio_v3.1\c6000\csl\include -
Ic:\CCStudio_v3.1\bios_5_20_05\packages\ti\bios\lib -Ic:\CCStudio_v3.1\c6000\csl\lib -Ic:\CCStudio_v3.1\6.1.19\include -Ic:\CCStudio_v3.1\6.1.19\lib -Ic:\CCStudio_v3.1\bios_5_20_05\packages\ti\rtdx\lib\c6000 -Ic:\CCStudio_v3.1\bios_5_20_05\packages\ti\rtdx\include\c6000 -Ic:\CCStudio_v3.1\bios_5_20_05\packages\ti\bios\include -d"_DEBUG" -d"NDEBUG" -d"CHIP_6410" -mv6400 --mem_model:data=far -fbDebug  -ffDebug  -frDebug  -fsDebug  -ftDebug  -d"CORE1"-d"CS_LITTLE_ENDIAN"
-pr -pds 179 -pds 225 -pds 230 -pds 238 -pds 190 ..\src\boardDate.c

Linking:

c:\CCStudio_v3.1\6.1.19\bin\lnk6x -a -c -mDebug\dfc8_ram.map -o Debug\dfc8_ram.out \
-w -x -ic:\CCStudio_v3.1\bios_5_20_05\packages\ti\rtdx\lib\c6000 -ic:\CCStudio_v3.1\c6000\csl\lib -ic:\CCStudio_v3.1\C6000\xdais\lib -ic:\CCStudio_v3.1\6.1.19\lib -ic:\CCStudio_v3.1\bios_5_20_05\packages\ti\bios\lib -priority \Debug\boardBIOS.obj Debug\boardCmdtbl.obj ...<obj files> dfc8_ram_linker.cmd

Linker warning:

warning: conservatively using trampoline for call destination "CLK_F_gethtime";
   generation and use of this trampoline can potentially be avoided if the
   --symbol_map option is used to re-direct symbol references instead of using
   symbol assignments

Linker errors:

undefined first referenced
  symbol       in file
 --------- ----------------
 __strasgi Debug\boardSfpp.obj

error: unresolved symbols remain
error: errors encountered during linking; "Debug\dfc8_ram.out" not built

I just want to address this ...

Nitin Manohar said:

undefined first referenced
  symbol       in file
 --------- ----------------
 __strasgi Debug\boardSfpp.obj

error: unresolved symbols remain
error: errors encountered during linking; "Debug\dfc8_ram.out" not built

I attached an FAQ which talks about this error.  It establishes the background for what is going on.  But it doesn't explain why you are seeing the error in this particular case.  Please check your build settings to be absolutely sure that you are linking against a v6.1.x version of the RTS library.  Linking against the v5.1.x RTS library would produce this error, but I don't think you are doing that.

Thanks and regards,

-George

1460.strasg_info.doc