• Locked Locked
  • Replies 1 reply
  • Subscribers 53 subscribers
  • Views 989 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.

Parallel builds broken on CCSv6.2

BrianBrianBrian
Expert 1085 points
Other Parts Discussed in Thread: SYSBIOS

After upgrading from 6.1 to 6.2, parallel builds now fail unless I clean my project or disable parallel builds and then reenable them again.  According to the build log it looks like stale auto-generated targets like this

subdir_rules.mk:10: recipe for target 'build-1380448913-inproc' failed

from a previous parallel build are confusing the build process:

**** Build of configuration Release for project er301 ****

"C:\\ti\\ccsv6\\utils\\bin\\gmake" -j 8 all -O
'Building file: ../er301.cfg'
'Invoking: XDCtools'
"/xs" --xdcpath="C:/ti/bios_6_46_00_23/packages;/packages;C:/ti/uia_2_00_03_43/packages;/packages;C:/Users/brian/ccsv6.1/rtsc;" xdc.tools.configuro -o configPkg -t gnu.targets.arm.A8F -p od.er301.rev1 -r release -c "../er301.cfg"
subdir_rules.mk:10: recipe for target 'build-1380448913-inproc' failed
process_begin: CreateProcess(NULL, sh.exe -c "/xs --xdcpath=C:/ti/bios_6_46_00_23/packages;/packages;C:/ti/uia_2_00_03_43/packages;/packages;C:/Users/brian/ccsv6.1/rtsc; xdc.tools.configuro -o configPkg -t gnu.targets.arm.A8F -p od.er301.rev1 -r release -c ../er301.cfg", ...) failed.
make (e=2): The system cannot find the file specified.

gmake[1]: *** [build-1380448913-inproc] Error 2
making ../src/sysbios/sysbios.aa8fg ...
gmake[1]: Nothing to be done for 'all'.
'Building file: ../er301.cfg'
'Invoking: XDCtools'
"/xs" --xdcpath="C:/ti/bios_6_46_00_23/packages;/packages;C:/ti/uia_2_00_03_43/packages;/packages;C:/Users/brian/ccsv6.1/rtsc;" xdc.tools.configuro -o configPkg -t gnu.targets.arm.A8F -p od.er301.rev1 -r release -c "../er301.cfg"
subdir_rules.mk:10: recipe for target 'build-1380448913-inproc' failed
process_begin: CreateProcess(NULL, sh.exe -c "/xs --xdcpath=C:/ti/bios_6_46_00_23/packages;/packages;C:/ti/uia_2_00_03_43/packages;/packages;C:/Users/brian/ccsv6.1/rtsc; xdc.tools.configuro -o configPkg -t gnu.targets.arm.A8F -p od.er301.rev1 -r release -c ../er301.cfg", ...) failed.
make (e=2): The system cannot find the file specified.

gmake[2]: *** [build-1380448913-inproc] Error 2
/pre-build.bat
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\brian\od\firmware\er-301\ccs\er301\Release>' '
'Building file: ../er301.cfg'
'Invoking: XDCtools'
"/xs" --xdcpath="C:/ti/bios_6_46_00_23/packages;/packages;C:/ti/uia_2_00_03_43/packages;/packages;C:/Users/brian/ccsv6.1/rtsc;" xdc.tools.configuro -o configPkg -t gnu.targets.arm.A8F -p od.er301.rev1 -r release -c "../er301.cfg"
subdir_rules.mk:10: recipe for target 'build-1380448913-inproc' failed
process_begin: CreateProcess(NULL, sh.exe -c "/xs --xdcpath=C:/ti/bios_6_46_00_23/packages;/packages;C:/ti/uia_2_00_03_43/packages;/packages;C:/Users/brian/ccsv6.1/rtsc; xdc.tools.configuro -o configPkg -t gnu.targets.arm.A8F -p od.er301.rev1 -r release -c ../er301.cfg", ...) failed.
make (e=2): The system cannot find the file specified.

gmake[2]: *** [build-1380448913-inproc] Error 2
makefile:449: recipe for target 'all' failed
gmake[1]: *** No rule to make target 'build-1380448913', needed by 'configPkg/compiler.opt'. Stop.
gmake: *** [all] Error 2

**** Build Finished ****

CCS Version: 6.2.0.00050

OS: Windows 7

Target: AM335x

  • TI__Guru**** 173310 points

    BrianBrianBrian said:
    After upgrading from 6.1 to 6.2, parallel builds now fail unless I clean my project or disable parallel builds and then reenable them again.  

    Are you opening your previously created CCS 6.1 workspace in 6.2, or did you create a new workspace in 6.2 and import your project into it? Just wanted to check into this as it is always recommended to create new workspaces with each new release of CCS to avoid workspace corruption problems.

    Secondly we have seen a few instances where RTSC projects require a clean build/rebuild, especially if the RTSC package versions have changed between a previous and later build, and I think that may be what happened in this case.