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.

Automatic Library Build fails

Hi CCS Champs,

I'm trying to build a CCS example (SYS/BIOS hello world from the project wizard). The target is Arm A8. I have a WinXP SP3 machine with CCS5.1.0.09000. When I build the project, it fails when trying to build the RTS library. I pasted in below some of the errors. There were actually a lot more of the same type of errors but I onlyh put a couple of them in because they all basically looked the same. I've seen this before on a different unrelated project but I worked around that by simply choosing a different libary (elf vs coff). but now it's back again. I searched the forums and didn't see much mention of this so I'm wondering if something is hosed with my PC. BTW, I've reinstalled CCS and that didn't help.

 


<Linking>
warning #10366-D: automatic library build: using library
   "C:\ti\ccsv5\tools\compiler\tms470\lib\rtsv7A8_A_le_n_eabi.lib" for the
   first time, so it must be built.  This may take a few minutes.


... whole bunch of errors went by, below are a couple, they all seem to be the same error ...


gmake.exe[1]: *** [c:/docume~1/a0322191/locals~1/temp/tica27~1/obj/fs_cmp32.obj] Error 2
process_begin: CreateProcess(NULL, cl470 fs_toi32.asm -o -oe -k -ps -pdsw225 -q -mv7A8 --fp_mode=strict --no_visible_enums --abi=eabi -c --ti_lib --building_runtime -D_BOOL --neon -me -Ic:/docume~1/a0322191/locals~1/temp/tica27~1/src -fr c:/docume~1/a0322191/locals~1/temp/tica27~1/obj -fs c:/docume~1/a0322191/locals~1/temp/tica27~1/obj -ft c:/docume~1/a0322191/locals~1/temp/tica27~1/obj, ...) failed.
make (e=2): The system cannot find the file specified.

gmake.exe[1]: *** [c:/docume~1/a0322191/locals~1/temp/tica27~1/obj/fs_div32.obj] Error 2
process_begin: CreateProcess(NULL, cl470 fs_toll32.asm -o -oe -k -ps -pdsw225 -q -mv7A8 --fp_mode=strict --no_visible_enums --abi=eabi -c --ti_lib --building_runtime -D_BOOL --neon -me -Ic:/docume~1/a0322191/locals~1/temp/tica27~1/src -fr c:/docume~1/a0322191/locals~1/temp/tica27~1/obj -fs c:/docume~1/a0322191/locals~1/temp/tica27~1/obj -ft c:/docume~1/a0322191/locals~1/temp/tica27~1/obj, ...) failed.
make (e=2): The system cannot find the file specified.

gmake.exe[1]: *** [c:/docume~1/a0322191/locals~1/temp/tica27~1/obj/fs_mul32.obj] Error 2
process_begin: CreateProcess(NULL, cl470 fs_tou32.asm -o -oe -k -ps -pdsw225 -q -mv7A8 --fp_mode=strict --no_visible_enums --abi=eabi -c --ti_lib --building_runtime -D_BOOL --neon -me -Ic:/docume~1/a0322191/locals~1/temp/tica27~1/src -fr c:/docume~1/a0322191/locals~1/temp/tica27~1/obj -fs c:/docume~1/a0322191/locals~1/temp/tica27~1/obj -ft c:/docume~1/a0322191/locals~1/temp/tica27~1/obj, ...) failed.
make (e=2): The system cannot find the file specified.

gmake.exe[1]: *** [c:/docume~1/a0322191/locals~1/temp/tica27~1/obj/fs_tod32.obj] Error 2
process_begin: CreateProcess(NULL, cl470 fs_toull32.asm -o -oe -k -ps -pdsw225 -q -mv7A8 --fp_mode=strict --no_visible_enums --abi=eabi -c --ti_lib --building_runtime -D_BOOL --neon -me -Ic:/docume~1/a0322191/locals~1/temp/tica27~1/src -fr c:/docume~1/a0322191/locals~1/temp/tica27~1/obj -fs c:/docume~1/a0322191/locals~1/temp/tica27~1/obj -ft c:/docume~1/a0322191/locals~1/temp/tica27~1/obj, ...) failed.
make (e=2): The system cannot find the file specified.

 Thanks,

Brad

 

  • Brad,

    It looks like you are running into SDSCM00042146. You can check the details of the bug and workaround by going to the SDOWP link in my signature and entering the bug #.

    The bug is fixed in ARM CGT 4.9.2 and higher. You can download and install this version from http://syntaxerror.dal.design.ti.com/release/release.cgi
    Then set CCS to use this newer version: http://processors.wiki.ti.com/index.php/Compiler_Installation_and_Selection#CCStudio_5.1

     

  • Another possible cause is having some copy of MKS toolkit in your PATH.  See:

    http://processors.wiki.ti.com/index.php/Mklib#Troubleshooting

  • Thanks for the help. Well it wasn't completely straight forward but I did fix this issue and the above replies helped.

    The first thing I checked was for quotation marks in my path or temp variables, didn't have any. I then updated my CG tools from 4.9.1 to 4.9.3 and that still didn't fix the problem. So I went down the mkstool kit path of investigation. I don't actually have the mks toolkit persay but over the years I have built up my own personal bin folder with my favorite command line utilities and it may have a handful of the mks commands in there. However, my bin folder has over 400 files so I don't want to completely remove that from my path so I had to really find the offending commands.

    I ran mklib.exe from the command line with the --verbose option and I noticed it was calling the sh.exe out of my personal bin folder. So I renamed sh.exe in my personal bin folder to something else and after doing so, mklib called sh.exe from some xdctools folder instead. I then went back to CCS and built my project again and this time it builds.

    So in conclusion, it was sh.exe that was corrupting my build environment. i just hope I don't have other things like this that I'm not aware of that will come and bite me in the future.

     

  • Hi

    I have spent a couple of days trying to get mklib to work for me.  I have seen 'out of memory' messages (on a 4gb pc ?) - these seem to be improved by setting mklib.exe into compatibility mode.

    Then I was stumped for a long line time by 'gmake.exe *** No rule to make target  'library' . This appears consistently after I have tried to build the libraries once, but goes away if I start from a copy of the files immediately after the TMS470 4.9.2 compiler install.

    Then different 'out of memory' errors.  Thanks so much for the tip above, these go away if I set my path to pick up sh.exe from an XDCTOOLS installation.

    So, I have managed to get mklib building by:

    ensure gmake.exe comes from XDCTOOLS, and sh.exe from XDCTOOLS\bin

    set mklib.exe to Windows 95 compatibilty mode

    run mklib immediately after installing the product, if it fails, install again (or get  acopy of the install files)

    Glad I found this on the forum, and glad I am not alone in having troubles with mklib.

    John Robinson

    York, England