Compiler/TDA3LA: Linker

Is your code organized as a CCS project?  If not, are you using a makefile, or what?  In either case, it would be helpful to see the entire linker invocation, along with all the resulting diagnostics.  Please copy-and-paste that into your next post.

Thanks and regards,

-George

5621.log1.txtThanks George,

We have makefile based project. I have attached log of compilation. 

BR, Naresh

The build log ends with ...

... LONG LINK COMMAND ...
<Linking>

>> Compilation failure

So I don't get to see the diagnostic.

The build log does show that you use ARM compiler version 16.9.4.LTS.  Except maybe you don't.  This ...

Naresh Patel said:

"C:\\Users\\npatel\\AppData\\Local\\Temp\\605443"

... is an old form for a temporary file.  There was a bug reported about temporary file names.  The ID is CODEGEN-2098.  You can look it up with the SDOWP link below in my signature.  For the ARM compiler 16.9.x.LTS series of releases, it is fixed as of version 16.9.3.LTS.  Since you use 16.9.4.LTS, you should see temporary file names in the new form, which look like ...

C:\\Users\\name\\AppData\\Local\\Temp\\{D8B571BA-8420-48B1-A32E-884CE0E4595E}

Very different from before.  

So, something does not match here.  I cannot explain how this happened.  Are you certain you use version 16.9.4.LTS?

Thanks and regards,

-George

Hi George,
Thank you for your response.

I have compile the same code with different ARM compiler too. Previously I am using ti-cgt-c6000_8.1.4 then I switched to latest one ti-cgt-msp430_16.9.4.LTS. I am getting the same error with all compiler.

Strange thing is that my colleague has same set up and he is not getting same error.

Best regards,
Naresh

Naresh Patel said:

Strange thing is that my colleague has same set up and he is not getting same error.

That is the nature of the temp file problem.  It does not occur every time, but intermittently.  

All of the compiler versions you mention have the fix for the temp file problem.  Yet, that diagnostic you show in an earlier post has an old form temp file name.  So, I am still confused as to what is going on.

Thanks and regards,

-George

Hello,

I am not able to resolve this issue.

I am always getting this incorrect path invoking problem by linker. please do the needful ASAP.

Best regards,
Naresh

Please demonstrate exactly which compiler version you use.  Be sure to use the same compiler that causes the problem.  It looks similar to the following ...

C:\work\dir>\ti\ccsv7\tools\compiler\ti-cgt-arm_16.9.4.LTS\bin\armcl -version
TI ARM C/C++ Compiler                   v16.9.4.LTS
Build Number 1RGTT-I3E26%M8-RTARQ-SAX-C08D

TI ARM EABI C/C++ Parser                v16.9.4.LTS
Build Number 1RGTT-I3E26%M8-RTARQ-SAX-C08D
TI ARM C/C++ File Merge                 v16.9.4.LTS
Build Number 1RGTT-I3E26%M8-RTARQ-SAX-C08D
TI ARM C/C++ Optimizer                  v16.9.4.LTS
Build Number 1RGTS-I3E26%M8-RTARQ-SAX-C08D
TI ARM C/C++ Codegen                    v16.9.4.LTS
Build Number 1RGTT-I3E26%M8-RTARQ-SAX-C08D
TI ARM Assembler                        v16.9.4.LTS
Build Number 1RGTT-I3E26%M8-RTARQ-SAX-C08D
TI ARM Embed Utility                    v16.9.4.LTS
Build Number 1RGTT-I3E26%M8-RTARQ-SAX-C08D
TI ARM C Source Interlister             v16.9.4.LTS
Build Number 1RGTT-I3E26%M8-RTARQ-SAX-C08D
TI ARM Linker                           v16.9.4.LTS
Build Number 1RGTT-I3E26%M8-RTARQ-SAX-C08D
TI ARM Absolute Lister                  v16.9.4.LTS
Build Number 1RGTT-I3E26%M8-RTARQ-SAX-C08D
TI ARM Strip Utility                    v16.9.4.LTS
Build Number 1RGTT-I3E26%M8-RTARQ-SAX-C08D
TI ARM XREF Utility                     v16.9.4.LTS
Build Number 1RGTT-I3E26%M8-RTARQ-SAX-C08D
TI ARM C++ Demangler                    v16.9.4.LTS
Build Number 1RGTT-I3E26%M8-RTARQ-SAX-C08D
TI ARM Hex Converter                    v16.9.4.LTS
Build Number 1RGTT-I3E26%M8-RTARQ-SAX-C08D
TI ARM Name Utility                     v16.9.4.LTS
Build Number 1RGTT-I3E26%M8-RTARQ-SAX-C08D
TI ARM Object File Display              v16.9.4.LTS
Build Number 1RGTT-I3E26%M8-RTARQ-SAX-C08D
TI ARM Archiver                         v16.9.4.LTS
Build Number 1RGTT-I3E26%M8-RTARQ-SAX-C08D

Please show exactly what you get.

Thanks and regards,

-George

Hello George

I am using ti-cgt-arm_5.2.5 compiler. and getting the same problem.

Best regards,
Naresh

The problem you must avoid is the temporary file problem described in CODEGEN-2098.  This problem is present in all ARM 5.2.x releases.  It is fixed in these ARM compiler releases:

• In the 15.12.x.LTS releases, it is fixed in 15.12.5.LTS and later
• In the 16.9.x.LTS releases, it is fixed in 16.9.3.LTS and later
• It is fixed in all 18.1.x.LTS releases

Please be completely certain you are using a compiler without this temporary file problem.

Thanks and regards,

-George

Hello

VSDK_COMP_ROOT := C:/VISION_SDK_02_08_00_00/ti_components
CG_TOOLS_A15 := C:/ti/ccsv7/tools/compiler/gcc-arm-none-eabi-6-2017-q1-update/
CG_TOOLS_M4 := C:/ti/ccsv7/tools/compiler/ti-cgt-arm_16.9.4.LTS
CG_TOOLS_C66 := C:/ti/ccsv7/tools/compiler/ti-cgt-c6000_8.1.4
CG_TOOLS_ARM_GCC := C:/ti/ccsv7/tools/compiler/gcc-arm-none-eabi-6-2017-q1-update
CG_TOOLS_ARP32 := $(VSDK_COMP_ROOT)/cg_tools/windows/arp32_1.0.7/
XDC_TOOLS_ROOT := $(VSDK_COMP_ROOT)/os_tools/windows/xdctools_3_31_02_38_core
SYSBIOS_ROOT := $(VSDK_COMP_ROOT)/os_tools/bios_6_42_02_29/packages
XDAIS_ROOT := $(VSDK_COMP_ROOT)/algorithms_codecs/xdais_7_24_00_04/packages
UTILS := $(XDC_TOOLS_ROOT)/bin


I am using above tools. still I am getting linker invocation error.

It is so strange... Can you please light us.

I'm sorry, but I still don't know what is happening.  I'd appreciate if you would try one more experiment.

Add these hidden options to the problem link: --d --v.  They cause lots of debug information to be emitted.  Please capture the entire invocation of the linker, plus all the output, in a text file, and attach that to your next post.

Thanks and regards,

-George

Please do the needful aSAP

I don't understand.  You are not waiting on anything from me.  I am waiting on you to submit the text file from the experiment I requested in my last post.

Thanks and regards,

-George