Bug 227164

Summary: Problem when updating gcc
Product: [Applications] kdevelop Reporter: jan.fostier
Component: Language Support: CPP (old)Assignee: kdevelop-bugs-null
Status: RESOLVED DUPLICATE    
Severity: normal CC: olivier.jg
Priority: NOR    
Version First Reported In: unspecified   
Target Milestone: ---   
Platform: unspecified   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description jan.fostier 2010-02-16 11:44:01 UTC 
Version:           3.9.98 (using KDevPlatform 0.9.98) (using 4.3.5 (KDE 4.3.5), 4.3.5-2.fc12 Fedora)
Compiler:          gcc
OS:                Linux (x86_64) release 2.6.31.12-174.2.3.fc12.x86_64

Problem:

1) I had gcc 4.4.2 installed.
2) I updated to gcc 4.4.3.
3) After opening my project, all stl statements in the code were marked as problems, because kDevelop couldn't find the stl include files.  It was looking in /usr/include/c++/4.4.2, however, everything was now installed in /usr/include/c++/4.4.3
4) Rebuilding with CMake didn't solve it.  Even completely removing the CMake build directory and then rebuilding didn't solve it.  Eventually closing and reopening kDevelop made it find the correct path.
Comment 1 Andreas Pakulat 2010-02-16 12:22:36 UTC 
@david: feel free to mark as wontfix, IMHO its acceptable to have to restart kdevelop when upgrading such a core component as the compiler.
Comment 2 jan.fostier 2010-02-16 12:33:03 UTC 
The gcc update occured when kdevelop was *closed*.  You can restart 
kdevelop all you want after the update, but it will keep looking in the 
old include paths, hence marking half your code as problematic.  You 
have to remove your project's CMake build directory first (a bit like 
the autotools' make distclean, but then the hard way), and *then* 
restart kDevelop.
Comment 3 Andreas Pakulat 2010-02-16 13:19:02 UTC 
That wasn't clear from your original description. So did building the project from the commandline work after the update and before clearing the builddir?
Comment 4 jan.fostier 2010-02-16 13:24:40 UTC 
I realise that my original post was difficult to interpret.  It is 
difficult to retest it now, since I already removed my old builddir.  I 
think that building worked however.  This probably means that CMake did 
notice the change in compiler verision, but that this change (of include 
paths) did not propagate into kDevelop unless it was restarted.
Comment 5 Olivier.jg 2010-12-17 05:58:30 UTC 
This would probably work correctly these days, at least for CMake, but in any case there's a more specific bug for this.

*** This bug has been marked as a duplicate of bug 229406 ***