• State Answer Suggested
  • Locked Locked
  • Replies 2 replies
  • Answers 1 answer
  • Subscribers 53 subscribers
  • Views 641 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.

Stopping a parallel build (make -j) hangs infinitely

Eddie3909
Guru 10385 points

Other Parts Discussed in Thread: SYSBIOS

CCSv5.5.0.00077, Windows 7. C6472

I came across this bug in eclipse and wondered if it would help the issue we see on this post

http://e2e.ti.com/support/development_tools/code_composer_studio/f/81/t/351449

Bug 367429 - Stopping a parallel build (make -j) hangs infinitely (web link below)
https://bugs.eclipse.org/bugs/show_bug.cgi?id=367429

Is there a way TI could provide us with a CCSv5.5 starter.exe with the CREATE_BREAKAWAY_FROM_JOB flag set as per the linked post to the above bug report?
https://bugs.eclipse.org/bugs/show_bug.cgi?id=333578

Compiles with -j 1 are taking way too long and it would really help get product to mkt if we can reduce the build time.

Cheers
Eddie

  • 0
    TI__Guru**** 173310 points

    Eddie,

    I'm not sure if that Eclipse bug could be related to the behavior you are observing with CCS hanging when a compiler error is hit during build. It is possible, but I can't tell for sure from reading the description. The other issue is that we are no longer fixing bugs or making updates to CCSv5, so that poses a challenge as well in terms of creating a special build to test with.

    I know this is not the answer you were hoping for, but the best way for us to analyze the problem would be with a reproducible test case. I will consult with a CCS engineer to see if there are other logs etc that could help analyze the issue and maybe you could capture those for us the next time you hit the problem.

     

  • 0 in reply to AartiG
    Guru 10385 points

    Hi Arti

    Thanks for the reply. Unfortunately we're a bit gun shy of going to CCSv6 because the legacy printf logs are no longer supported and we experienced a ton of tool incompatibilities (like SYSBIOS not compatible with XDC thats not compatible with CGT and also a compiler bug - but I have to mention that you guys/gals were great in trying to help us solve them).

    I guess we're stuck with this compile issue until someone in our group gets up the nerve to try CCSv6 again.

    We also saw the same issue on CCSv6 when we tried it. Hopefully its been fixed.  :)

    Cheers2u
    Eddie