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

Nicolai Haehnle prefect_ at gmx.net
Sat Sep 13 01:03:04 UTC 2003

Hash: SHA1

On Friday 12 September 2003 20:26, you wrote:
> http://bugs.kde.org/show_bug.cgi?id=64107
> [snip]
> ------- This in not a bug!

Yes it is, this *is* a bug. It's obviously not a bug in KDevelop itself, but 
It's a bug in the configure script that comes with the KDevelop 3.0.0a6 

> This is a compilation error.

True, it is *also* a compilation error. I clearly said so in the bug report.

> Please:
>  -Report bugs to the bug database (here)
>  -Report compilation erros to the mailing list (not here)

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/

> PS: How about providing you QT, autoconf, Python and automake versions?

Qt version 3.2.1 (does it make a difference with this bug?)
Python 2.3 (as stated before - if there's a way to get more detailed version 
information out of the python executable, I simply don't know about it)

autoconf 2.57
automake 1.4-p6

I'm curious though - I thought configure scripts were supposed to work 
without autoconf and/or automake installed, so those version numbers 
shouldn't make a difference at all?

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.

Version: GnuPG v1.2.3 (GNU/Linux)


More information about the KDevelop-devel mailing list