[Bug 76012] bogus report that it fails to find makefile

Jens Dagerbo jens.dagerbo at swipnet.se
Sat Mar 6 20:39:02 UTC 2004


------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
      
http://bugs.kde.org/show_bug.cgi?id=76012      




------- Additional Comments From jens.dagerbo swipnet se  2004-03-06 20:38 -------
>It's all related. 

Not really, unless you consider all automake issues related. Even if you do, it's still no reason to cram several problems into one bugreport.


>The bogus Makefile error shows up because of the default/optimize/debug problem. 

No and no. In your case, but not in the reported case, the multiple build configuration problem is the cause of the Makefile warning. In your case however, it is NOT bogus - there IS no makefile for the configuration you have switched to, so it needs to be created. It cannot be created due to the "multiple build configuration problem", but this is clearly not the reported problem.

As for the 'config.status' file. I came to the same conclusion as you last time I looked at this, but got conflicting reports from other users. Apparently, removing that file isn't always enough. I never got further with the problem and hoped the smart kids that came up with this system would figure it out.

Still, it appears to me to be a bug of the distclean target to not remove 'config.status'. It's a generated file and as such I assume it should be cleaned up.




More information about the KDevelop-devel mailing list