• Locked Locked
  • Replies 4 replies
  • Subscribers 54 subscribers
  • Views 4365 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

CCS5: process_begin: CreateProcess .... failed

gbl
Intellectual 400 points
Other Parts Discussed in Thread: TEST2

Possibly since the installation of CCS5.1.08020 in parallel to CCS5.1.05000 (which worked well so far) I have the following problem:

Even after complete deinstallation and new installation of all CCS related software, even with the most simple hello world program I get this error when issuing a post build command:

D:/Program Files (x86)/Texas Instruments/CCS5.1.0.05000/ccsv5/utils/gmake/gmake --no-print-directory post-build
process_begin: CreateProcess(D:\Program, D:/Program Files (x86)/Texas Instruments/CCS5.1.0.05000/ccsv5/utils/gmake/gmake --no-print-directory post-build, ...) failed.
make (e=193): Error 193
gmake: *** [test2.out] Error 193
gmake: Target `all' not remade because of errors.

It is absolutely unclear to me what could cause this. Similar threads identified certain gmake versions as cause of the problem, but those work fine on a parallel PC.

It looks as if the makefile used for the post-build target is the problem. Where can I find that?

Other point: obviously there is a problem with spaces in the path names (see that broken D:\Program, D:/Program Files ..). What can cause this?

Any help is more than welcome as our complete build server is blocked.

  • TI__Guru**** 472451 points

    Hi,

    What is the post-build step you are executing? Could you try using a new workspace and importing your existing projects to it and try building again?

    ki

  • in reply to Ki
    Intellectual 400 points

    Hi,

    I reduced the post-build step to a very simple 'cd'. Even if I create a totally new project (standard "hello world" example) the problem occurs. it must be something fundamental that occurs when creating the makefile with target "post-build". The commands that are executed seem to get confused with the "program file" paths.

  • in reply to Ki
    Intellectual 400 points

    After de-installation of TI tools from path d:\program files and new installation to d:\programs (path name without blank) it does work again. Additional blanks in the path name in Texas Instruments do not matter.

    All together still very mysterious. How can I watch the make file that is generated for post-build?

  • in reply to gbl
    TI__Guru**** 162895 points

    I wonder if it is specific to "Program Files" or "Program Files (x86)".  I know Vista and Win7 are pretty sensitive about what a happens in those folders.  We have updated the installer to detect Win7 and suggest installing in a different directory.  I have spaces all over my paths but I install outside of Program Files.

    If you want to look at the generated makefiles they are present in the configuration directory, i.e. \Debug.  If I recall correctly you might be redirecting the output for some things so if they are not in that directory check the locations where you are redirecting output to.

     

    John