Bug 80745 - KDevelop fails to build projects.
Summary: KDevelop fails to build projects.
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Red Hat Public Beta
Classification: Retired
Component: kdevelop
Version: phoebe
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Than Ngo
QA Contact: Ben Levenson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2002-12-30 19:03 UTC by Mario A. Vazquez
Modified: 2007-04-18 16:49 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2002-12-30 22:40:33 UTC
Embargoed:


Attachments (Terms of Use)

Description Mario A. Vazquez 2002-12-30 19:03:13 UTC
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):
kdevelop-2.1.4-3
autoconf-2.57-2
automake-1.6.3-3

How reproducible:
Allways


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 Than Ngo 2002-12-30 22:40:33 UTC
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.