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.

TMS320C6678: gmake error rebuilding IPC library: "is not recognized as an internal or external command"

Part Number: TMS320C6678


Hello,

This is a generic question about using gmake to rebuild a ti Library.

I am rebuilding a version of the IPC library since I need to use an updated Sys/Bios in that library.

I am using the included ipc.mak file on a windows 10 machine.

I have followed the instruction in the users guide for rebuilding the library.

The clean operation works after fixing an error on the make file.

When I run gmake I receive the following error:

'c:' is not recognized as an internal or external command,
operable program or batch file.
gmake: *** [all] Error 255

Changing paths around in the make file I see that the error is referring to the XDC_INSTALL_DIR path variable.

I tried different variations to no avail:

#XDC_INSTALL_DIR ?= c:/ti/xdctools_3_25_05_94  FAIL
#XDC_INSTALL_DIR ?= ./xdctools_3_25_05_94      FAIL
#XDC_INSTALL_DIR ?= ../xdctools_3_25_05_94     FAIL
XDC_INSTALL_DIR ?= c:\ti\xdctools_3_25_05_94   FAIL

I followed the instructions in the IPC users guide for rebuilding the library and I do not see what it is that is wrong.

Is there any general guidance on the is gmake error?

Thank You,

Forrest

  • I tried using the command line to pass in the directory parameters with the exact same results as before:

    C:\ti\ipc_1_25_01_00_Rebuilt>gmake -f ipc.mak XDC_INSTALL_DIR=C:\ti\xdctools_3_25_05_94 ti.targets.elf.C66=C:\ti\C6000Compilers\V8_3_3
    building ipc packages ...
    Target is: all
    XDC_INSTALL_DIR is: C:\ti\xdctools_3_25_05_94
    directory is: C:\ti\xdctools_3_25_05_94/xdc XDCARGS="ti.targets.C28_large=\"\" ti.targets.C28_float=\"\" ti.targets.C64P=\"\" ti.targets.C64P_big_endian=\"\" ti.targets.C64T=\"\" ti.targets.C674=\"\" ti.targets.arm.elf.Arm9=\"\" ti.targets.arm.elf.A8Fnv=\"\" ti.targets.arm.elf.M3=\"\" ti.targets.arm.elf.M4=\"\" ti.targets.arm.elf.M4F=\"\" ti.targets.elf.C64P=\"\" ti.targets.elf.C64P_big_endian=\"\" ti.targets.elf.C64T=\"\" ti.targets.elf.C66=\"C:\ti\C6000Compilers\V8_3_3\" ti.targets.elf.C66_big_endian=\"\" ti.targets.elf.C674=\"\" ti.targets.msp430.MSP430=\"\" ti.targets.msp430.MSP430X=\"\" ti.targets.msp430.MSP430X_small=\"\" ti.targets.arp32.elf.ARP32=\"\" ti.targets.arp32.elf.ARP32_far=\"\" gnu.targets.arm.M3=\"\" gnu.targets.arm.M4=\"\" gnu.targets.arm.M4F=\"\"" XDCBUILDCFG=./ipc.bld
    'C:\ti\xdctools_3_25_05_94' is not recognized as an internal or external command,
    operable program or batch file.
    gmake: *** [all] Error 255

  • Hi Forrest,

    Please add path "C:\ti\xdctools_3_25_05_94" to "Path" variable in "Environment variables" for your account. Then, open windows terminal and type "gmake", it may recognize it.

     Your error shows, Instead of a binary(.exe) command uses "C:\ti\xdctools_3_25_05_94" (XDC_INSTALL_DIR) folder. Please correct those in make file.

    Thanks & regards,

    Rajarajan U

  • Hello Rajarajan,

    Thank you for the response. I had done that according to the instructions in the users guide.

    There was nothing wrong with my make file. There was nothing wrong with my environment variables.

    I installed Cygwin and ran the gmake command from within Cygwin.

    gmake completed successfully within Cygwin.

    Thanks Anyway,

    Forrest

  • Hi Forrest,

    Good to hear that you solved this issue.

    In the gmake log xdc binary is called as "C:\ti\xdctools_3_25_05_94/xdc" and it may not work in windows terminal. The cygwin terminal may accept, both forward slash "/" and backward slash "\".

    This was the issue that I was mentioning earlier("in make file"). Apologies, for providing you the information in detailed manner.

    Thanks & regards,

    Rajarajan u

  • Hi Rajarajan,

    Yes. Thanks. I am aware of the difference in slashes. I had tried both directions initially ad neither had worked in windows. It is nice to know that Cygwin

    works so very well. I have used the DOS prompt for other make files recently. I will use Cygwin moving forward.

    Thanks,

    Forrest