Bug#37350: marked as done (C++ terminal application project cannot be set up by selecting New project) by Harald Fernengel <harry at kdevelop.org>

Stephan Kulow owner at bugs.kde.org
Mon Jan 21 13:54:33 UTC 2002


Your message with subj: Fixed in CVS



has caused the attached bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I'm
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Stephan Kulow
(administrator, KDE bugs database)

Received: (at submit) by bugs.kde.org; 20 Jan 2002 21:04:35 +0000
Received: (qmail 4642 invoked by uid 33); 20 Jan 2002 21:04:35 -0000
Date: 20 Jan 2002 21:04:35 -0000
Message-ID: <20020120210435.4641.qmail at master.kde.org>
To: submit at bugs.kde.org
Subject: C++ terminal application project cannot be set up by selecting New project
From: 0611500836-0001 at t-online.de

Package:           kdevelop
Version:           2.0.1 (using KDE 2.2.1 )
Severity:          normal
Installed from:    SuSE RPMs
Compiler:          gcc 2.95.93 20010315 (SuSE)
OS:                Linux
OS/Compiler notes: Linux (i686) release 2.4.10-4GB

Select "New" Project -> C++ Terminal application
after "Create" is selected the process is started, but ends with the following information:
shell-init: could not get current directory: getcwd: cannot access parent directories: No such
file or directory
shell-init: could not get current directory: getcwd: cannot access parent directories: No such
file or directory
./aclocal.m4:2181: error: m4_defn: undefined macro: _m4_divert_diversion
acfunctions.m4:1108: AM_FUNC_OBSTACK is expanded from...
./aclocal.m4:2181: the top level
autoconf: tracing failed
make: *** [all] Error 1
sh: ./configure: No such file or directory

Remark: I am a relative new user of KDevelop but under SuSE 7.2 I did not get this error. I made a standard installation of SuSE 7.3 and double checked the error on three different machines with three different colleagues. The problem does not occur when creating a KDE or Qt project.



(Submitted via bugs.kde.org)





More information about the KDevelop-devel mailing list