[Bug 64107] KDevelop 3.0.0a6 configure/compile problem: python header detection

[Amilcar do Carmo Lucas]

------- 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=64107     




------- Additional Comments From a.lucas at tu-bs.de  2003-09-13 14:46 -------
> It's a bug in the configure script that comes with the KDevelop 3.0.0a6  
> distribution. 
 
Guess what we are not responsible for the distribuition.  
But the solution should be to execute: 
make -f Makefile.cvs 
This will recreate a new tailiored configure script for your system. 
This script will replace the broken one you got from your distribuitor. 
 
 
 
> That's fine with me, but if you want it to be that way, you have to say so  
> somewhere! There is no indication whatsoever on http://bugs.kde.org/, and  
> there is no indication whatsoever on http://www.kdevelop.org/ 
 
Thanks for pointing that out, I've fixed it. 
 
 
 
> automake 1.4-p6 
 
I think that here lies your problem. To use automake < 1.6.1 you need to use 
the trick described at: 
http://www.kdevelop.org/index.html?filename=requirements.html 
 
 
 
> And yes, I *am* talking about the configure script that comes with the  
> KDevelop 3.0.0a6 tarball. 
 
> And yes, maybe this bug is triggered by something external, like autoconf or  
> automake. But I've said it in the bug report, and I'll say it again here: 
> The part of the configure script that is supposed to detect Python did  
> detect Python correctly! It reported to stdout that no Python headers or  
> libraries are installed, and it did find the executable that *was*  
> installed. It just didn't stop the compilation as it should have. 
 
Please test the solutions that I've provided and let me know if it solved your 
problem. 
You can reply to me using : 
http://bugs.kde.org/show_bug.cgi?id=64107