This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

CODECOMPOSER: CCS gmake error: The system cannot find the file specified

Part Number: CODECOMPOSER
Other Parts Discussed in Thread: SYSCONFIG

Tool/software:

My customer has met an issue during CCS project build as below:

I have found a similar issue in the "Project Import and Build errors in CCS" page below:

https://software-dl.ti.com/ccs/esd/documents/sdto_ccs_build-errors.html#make-the-system-cannot-find-the-file-specified

We have followed the guide in above link to check all the suggested items, including anti-virus, the "make" path and the permissions on the TEMP folder, they all look good. Also tried to change the path for TEMP but the issue still appeared.

Please find the CCS and compiler version as below:

  • CCS 12.8.1
  • ti_cgt_armllvm_3.2.2.LTS_windows-x64
  • Project: basic_ble example from simplelink_lowpower_f3_sdk_8_10_01_02

Please kindly suggest what is the next step to locate the root cause of this issue, thanks.

Complete build log as below:

1727.log.txt

Best regards,

Shuyang

  • Hi Shuyang,

    Did the user make any modifications to the project after importing it from the SDK?  Looking at the build-output, i see that "cc" is used to compile source files, which is not something that CCS does.  I have a feeling the user modified the project and it no longer builds.

    Could you please ask the user to import the same project into a clean new workspace and see if that builds successfully?

    Thanks,

    Baltasar

  • Hi Baltasar,

    The user did not make any modification to the project, they also have tried to change the workspace but with no luck.

    Which configuration is related to the "cc" parameter? I can ask them to check the corresponding configuration.

    Best regards,

    Shuyang

  • Hi Shuyang,

    Could you please ask the user to build their project once, then zip the project and attach it to this post?

    Thanks,

    Baltasar

  • Hi Baltasar,

    Please find the project as attached:

    basic_ble_LP_EM_CC2340R5_freertos_ticlang_gmake_error.zip

    Best regards,

    Shuyang

  • Thanks for the project. I was able to import and build it successfully so it looks like the project itself is fine:

    project basic_ble_LP_EM_CC2340R5_freertos_ticlang.log

    The issue must be related to some specific in your environment. I see the failure on your end occurred when trying to build the sysconfig file. Are you able to build any other examples? Do you only have issues with this particuar example?

    Thanks

    ki

  • Hi Ki,

    This issue happens with all projects, they even tried with CCS theia but saw the same error with the IDE.

    I have help the customer to check all the items mentioned in the "Project Import and Build errors in CCS" page, and they all looks fine. We are running out of idea at the moment. Is there anything else to check?

    From the customer's log, the error happened during the below step:

    process_begin: CreateProcess(NULL, cc -c -o syscfg/ti_ble_config.o syscfg/ti_ble_config.c, ...) failed.

    As Baltasar mentioned the "cc" parameter should not appear here. Would you please help explain what is the compiler doing during this step and where can I find the configuration related to the "cc" parameter?

    Best regards,

    Shuyang

  • Just a quick update...

    I think I know where the 'cc' command comes from - it's a builtin make rule, which attempts to use 'cc' to compile all .c files when make fails to find a rule in the makefile.  But I don't know why gmake fails to find the rule in the makefile - the autogenerated makefiles, in the attached project, look OK to me.  The rules "syscfg/%.o: ./syscfg/%.c" and "%.o: ../%.c" are present there, but gmake fails to match them.  Instead of the first rule, it defaults to the builtin rule, trying to use 'cc' to compile all SysConfig-generated source files.  And instead of matching the second rule, it just outputs "No rule to make target".  And files that are linked from the SDK are compiled correctly - the only difference is that these do not use pattern rules (rules that contain a '%' character).

    I suspect it's caused by something specific to the environment.  But I doubt it's caused by the non-English Windows environment, because we haven't seen other such cases.  Maybe it's somehow caused by some antivirus software that interferes with gmake at runtime.

    Shuyang, could you ask the user if they've tried building this project on other machines?  Could they try that?  Could they try it on a machine with the English Windows language setting?

    Baltasar