#31 Build fails after switching tool chain

Next release
Peter Horn

The target no longer builds after the tool chain has been switched forth and back in the tool chain editor. The build fails with message

"No tool found that can build the extension specified with the build artifact name all"

The only way to get out is to add an new build configuration.

Steps to reproduce:

Create a project, add some files, build it.
Open Project Properties->C/C++ Build->Tool Chain Editor
Change the current tool chain to a different one, press apply
Then set the tool chain back to the original setting
Build the project -> Fails


GNU ARM C/C++ Development Support org.eclipse.cdt.cross.arm.gnu.feature.group
Eclipse IDE for C/C++ Developers epp.package.cpp


  • Liviu Ionescu (ilg)

    • assigned_to: nobody --> ilg-ul
    • status: open --> open-accepted
  • Liviu Ionescu (ilg)

    I confirm it. it looks like a CDT bug.

  • Liviu Ionescu (ilg)

    • priority: 5 --> 9
  • Liviu Ionescu (ilg)

    I marked this as a major bug, since I did not find a way to repair broken projects (you have to create a new project and copy content).

    I'll investigate if it is a plug-in or a CDT bug.


  • alexp

    alexp - 2011-10-16

    does a fix exist for this bug & svn?
    i import a project via svn, if i create a new procet this is a temporery solution to work, thank you ilg-ul for this solution.
    but in my case i'm not able to commit or update again the new project via svn.

  • Liviu Ionescu (ilg)

    I don't know of a fix for this bug :-(

    I'll check again when the Indigo will be fixed, currently the plug-in does not run properly on Indigo due to another CDT problem.


  • alexp

    alexp - 2011-10-16

    do you know a other way to do a workaround for my problem?
    if i create a new project i'm not able to syncronice with the team in eclipse (svn) & if i synchronice (checkout) i get the wrong settings and must switch the toolchain.
    in this case it's not easy to work...
    perhapse has somebody a idea?!


  • Nobody/Anonymous

    ok i found a solution for my problem.
    its similar like the workaround from ilg-ul.

    create a new project and config it you need.
    after, copy the content from the .cproject into the .cproject from the broken svn project.
    (the svn project hast now the right configuration)
    now you are able to work with a svn project and can update and commit :-)

  • alexp

    alexp - 2011-12-02

    today i tried indigo with GNU ARM,
    and it it has the sam problem (with the switching of the toolchain).

    and i have a problem with the version 0.5.4, i must uncheck the "group items by category" by installing it via help-->install new software --> (location http://gnuarmeclipse.sourceforge.net/updates/\). its the first time i must do this with the gnu arm plug-in.

    and it possible that the 0.5.4 does not work with the eclipse helios?

  • Liviu Ionescu (ilg)

    > "group items by category"

    fixed, please check again with

    > 0.5.4 does not work with the eclipse helios

    nope, it requires CDT 8.0


  • Liviu Ionescu (ilg)

    and, Alex, please do not mix multiple bug reports under the same ticket


  • alexp

    alexp - 2011-12-06


    only the toolchain-switch bug is open. do you think it can be fixes?

  • Liviu Ionescu (ilg)

    > only the toolchain-switch bug is open. do you think it can be fixes?

    I don't know yet, but now I have the full CDT source tree in my development environment and I can try to debug the toolchain-switch bug.

    the goal is to find a way to patch my plug-in to avoid the bug, otherwise I see the CDT team reaction is not very fast.


  • Manveru

    Manveru - 2012-07-31

    Was this bug reported to the CDT team? I am under Eclipse Juno with GNU ARM and the same problem hits me. Now I have broken project with very complex configuration, that cannot be build due to "No tool found that can build the extension specified with the build artifact name" in makefile.

    I was looking for solution to the other problem with GCC Build output parser (which took wrong command for compilation - not these from my setting, but pure "gcc") and that is why I was switching toolchains.

    I does not sound funny to me to recreate the project.

  • lkrzak

    lkrzak - 2013-09-12

    Are there any chances for a fix to this problem? I'm using Eclipse Keppler and the bug still exists. I'm using version

  • Liviu Ionescu (ilg)

    It is hard to say, being a CDT bug, it can be fixed only by the CDT developers. All I can do, is try (again) to find an workaround, but I do not guarantee any positive results.



  • lkrzak

    lkrzak - 2013-09-13

    Ok, let me just point out the exact steps to reproduce the problem and the problem itself, because it may be in fact something else than discussed previously.

    1. Create new C project -> ARM Cross Target Application -> Empty project and select any toolchain - the project is named "test"
    2. Add some source files -> build successful
    3. Change toolchain in C/C++ Build -> Toolchain editor -> build failed with error
    4. Change back the toolchain and the error still remains

    Now the error is:
    make: *** No rule to make target test.elf', needed byall'. Stop.

    Now what is seems to me is that in fact in the generated makefiles there is no rule to build test.elf

    Can I help in any way with this ?

  • Liviu Ionescu (ilg)

    I think it is the same problem, changing toolchains confuses CDT, and the generated makefile is incomplete, which leeds to failed builds.


  • Sprut

    Sprut - 2013-10-09


    This is the difference between the files .cproject.

    I did not click OK after changing the toolchain. I just chose to list the other, and then handed it back and then clicked OK.


    makefile changes too, but it does not affect the build. Returning old .cproject, and makefile to leave new - then everything is OK.

    Last edit: Sprut 2013-10-09
  • Liviu Ionescu (ilg)

    Thank you Sprut for your detailed report. The bug is known, but nobody from CDT fixed it yet. I recently got involved in CDT development, and I'll try to investigate.

  • Liviu Ionescu (ilg)

    • status: open-accepted --> closed
    • Group: --> Next release

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

No, thanks