Bug 80745 - KDevelop fails to build projects.
KDevelop fails to build projects.
Product: Red Hat Public Beta
Classification: Retired
Component: kdevelop (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Ngo Than
Ben Levenson
Depends On:
  Show dependency treegraph
Reported: 2002-12-30 14:03 EST by Mario A. Vazquez
Modified: 2007-04-18 12:49 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2002-12-30 17:40:33 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Mario A. Vazquez 2002-12-30 14:03:13 EST
Description of problem:
Trying to compile any proyect from a standard C/C++ to a KDE specific proyect
result in the following error:

configure.in:103: error: m4_popdef: undefined macro: AC_Dest
autoconf/status.m4:844: AC_CONFIG_FILES is expanded from...
configure.in:103: the top level
autom4te: /usr/bin/m4 failed with exit status: 1
make[1]: *** [cvs] Error 1
make: *** [all] Error 2
sh: line 1: ./configure: No such file or directory

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1.  Create any new proyect from KDevelop
2.  Try to compile it (Build/Make)
Actual results:
When creating the proyect files, KDevelop shows the previous error message and
do not allow to build the proyect.  DistClean and Rebuild, or Configure don´t
work either.  Haven´t tried with previously created proyects, but probably they
will fail too.

Expected results:
The proyect should compile without problems.

Additional info:
Made some test a month ago and found that KDevelop 2.1.X had problems with
autoconf 2.54 or greater.  It can be fixed by either:
1) downgrading to autoconf 2.53
2) replacing admin.tar.gz found in kdevelop/templates from a recent copy of
admin directory from kde-common in KDE cvs.  This requires QT 3.1, but since
that´s the one included I see no problem with that.
Comment 1 Ngo Than 2002-12-30 17:40:33 EST
it's fixed in 2.1.4-4, thanks for your infos.

Note You need to log in before you can comment on or make changes to this bug.