• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Subscribers 82 subscribers
  • Views 1022 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.

Problem with new compiler version

JayBe
Prodigy 95 points

hi,

we are using a "homemade" development environment, in which the bin tools are called from inside Borland make utility in version 5.2 .

We get following errormessage in case we switch from compiler V4.1.3 to 5.0.0 or above :

 I:\C2000\v5.0.0\compiler\cgtools\BIN\cl2000 -pm -me -o3 -q -g -pdr -pdv -pden -pdse225 -pds303 -fr".\obj" -d"LARGE_MODEL" -ml -v28 -i.\include -ig:\sys\os_281x\kernel\Vx.wrk\include -ig:\sys\os_281x\kernel\Vx.wrk\kernelinc -ig:\sys\os_281x\cmn\V2.10\include -iI:\C2000\v5.0.0\compiler\BIOS\include -iI:\C2000\v5.0.0\compiler\cgtools\include -DSTDALONE=0 -DVERSION=142 -DCMPL=413 -DWITHSERFLASH=1 -DMC88_15 -frg:\project\plusOne\MC88_15_Applayer\Vx.wrk\obj.413 g:\sys\os_281x\kernel\Vx.wrk\source\_nvdata.c

>> Cannot Open Input icode File, Invalid argument : \\0568813, Aborting

>> Compilation failure

Does anybody know  what the icode file is and why the compilation breaks if the compiler is called from inside make ? From commannd line it is working.

 

Many thanks in advance,

JayBe

 

 

  • 0
    TI__Guru**** 173310 points

    The icode file is a temporary/intermediate file generated by the compiler during the compilation process that is automatically removed after it is used. Looks like the file cannot be opened for some reason, maybe due to path permissions. You may want to try adding the -ft compiler option and specify a directory to place temporary files to see if that helps.

  • 0 in reply to AartiG
    Prodigy 95 points

    Hi Arti,,

    thanks for the input, the compilation goes further with setting the temporary directory, but it seems the compiler wants more files to generate, which he can't:

    >> Abort - Cannot open output file \\059283: Invalid argument

    Unfortunately he does not say which. I added all options to specify the directories(-fb,-fs,-ff,-fr and -ft), but it didn't solve the problem.

    Is there any other switch/trick to tell the new compiler where the intermidiate files should be stored ?

    Thanks,

    JayBe

    PS.: I don't get, why all compilers up to 4.14 worked perfectly, but all above 5.00 do not work. There must have been a real big significant change inside the toolchain between 4.xx and 5.xx...


     

     
  • 0 in reply to JayBe
    TI__Guru**** 173310 points

    Sounds like the issue has to do with invoking the compiler from within Borland make, as you say the error does not appear when building on command line.

    Ae you able to try the gmake included in the Code Composer Studio releases to see if that gives an error as well?

  • 0 in reply to AartiG
    Prodigy 95 points

    Hi Aarti,

    I'm on a business trip this week, I'll give it a try next week.

    Regards,´

    Jan

  • 0 in reply to JayBe
    Prodigy 10 points

    On my computer changing the temp and tmp path variable to c:\temp\  unter System|Extended|Environment Variables   helped to get rid of the problem.

  • 0 in reply to MM10418
    TI__Intellectual 1785 points

    It seems that the compiler cannot handle spaces in the TMP directory. So the above workaround would resolve the issue.