Bug#15090: kdevelop generating bad configure scripts?

James Tappin sjt at star.sr.bham.ac.uk
Fri Nov 10 16:42:51 UTC 2000

Package: kdevelop
Version: unknown

I've noticed a number of KDE2 applications which are failing with the same 
build problems (well kmago and keuklid).

I unpack the distribution and go to its top level directory then:
> ./configure --with-extra-libs=....
> gmake
cd . && aclocal
cd . && automake --foreign --include-deps Makefile
cd . && perl am_edit keuklid-0.1.2/Makefile.in
Can't open perl script "am_edit": No such file or directory
gmake: *** [Makefile.in] Error 2

There seem to be 2 things wrong here -- (1) it shouldn't need to re-run the 
automake stuff after the ./configure and (2) there should be an am-edit 
script somewhere.

The workaround seems to be to touch Makefile.in and Makefile (in that order) 
then the make works although:
1) It still re-runs the configure
2) I have to do the touch Makefile.in; touch Makefile in many subdirectories.

Since the identical problem occurs in more than one application and all those 
affected have kdevelop project files in the top-level directory I assume that 
there is something awry with the configure generation in kdevelop.


| James Tappin           | School of Physics & Astronomy |  O__    |
| sjt at star.sr.bham.ac.uk | University of Birmingham      | --  \/` |
| Ph: 0121-414-6462. Fax: 0121-414-3722                  |         |

to unsubscribe from this list send an email to kdevelop-devel-request at kdevelop.org with the following body:
unsubscribe »your-email-address«

More information about the KDevelop-devel mailing list