[prev in list] [next in list] [prev in thread] [next in thread]
List: kdevelop-bugs
Subject: [Bug 147066] New: detect-autoconf.pl causes kdevelop to give
From: Joshua Rogers <joshuarogers () hopper ! net>
Date: 2007-06-21 22:38:33
Message-ID: 20070622003832.147066.joshuarogers () hopper ! net
[Download RAW message or body]
------- 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=147066
Summary: detect-autoconf.pl causes kdevelop to give incorrect
information
Product: kdevelop
Version: 3.4.1
Platform: unspecified
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: general
AssignedTo: kdevelop-bugs kdevelop org
ReportedBy: joshuarogers hopper net
Version: 3.4.1 (using KDE KDE 3.5.6)
Installed from: Unlisted Binary Package
OS: Linux
After starting KDevelop, I decided to create a new project using the "Simple KDE application" template. \
When I tried to build the project, I got the message:
./admin/cvs.sh: line 33: --version: command not found
*** AUTOCONF NOT FOUND!.
*** KDE requires autoconf 2.53 or newer
Okay. So, I'm running a fairly new PCLinuxOS install and I forgot to install autoconf. No problem. I \
installed it and tried to build the project again. Again I received the same message. I tried running
perl admin/detect-autoconf.pl
and was greeted with the message
# Unable to find automake!!
What was happening was that admin/cvs.sh would call admin/detect-autoconf.pl. detect-autoconf.pl would \
fail because it couldn't find automake. However, it would not export any of the paths, including \
autoconf, which I did have installed (and it had found). cvs.sh would later try to run
$autoconf --version
Since detect-autoconf.pl did not export anything, $autoconf was blank. Thus it was actually tring to run
--version
causing it to fail with the message that automake is not installed.
It seems that it should export the paths for the programs it can locate, so that cvs.sh (and in turn \
kdevelop) will be able to state the actual cause of error.
This error can be reproduced if autoconf is install and automake is not.
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic