Bug#27381: marked as done (autoheader problem when creating new C project) by John Firebaugh <jfirebaugh at kde.org>

Stephan Kulow owner at bugs.kde.org
Sat Aug 31 05:00:59 UTC 2002

Your message with subj: autoheader problem when creating new C project

Thank you for your bug report.
The bug that your reported no longer applies to the latest development (CVS) 
version of KDE. This is most probably because the bug has been fixed, the 
application has been substantially modified, or the application no longer 
exists. The bug report will be closed.

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)

(Complete bug history is available at http://bugs.kde.org/db/27/27381.html)

Received: (at submit) by bugs.kde.org; 17 Jun 2001 17:55:32 +0000
Received: (qmail 7531 invoked by uid 33); 17 Jun 2001 17:55:32 -0000
Date: 17 Jun 2001 17:55:32 -0000
Message-ID: <20010617175532.7530.qmail at master.kde.org>
To: submit at bugs.kde.org
Subject: autoheader problem when creating new C project
From: wobby3 at home.com

Package:           kdevelop
Version:           1.4.1 (using KDE 2.1.1 )
Severity:          normal
Installed from:    Other
Compiler:          GNU C Computer 2.95.3
OS:                Linux
OS/Compiler notes: Not Specified

When creating a C project I get this error when it runs autoheader:
autoheader: error: shell error while sourcing /tmp/ah1149/traces.sh

I can't do anything with my project till that's fixed.  I e-mailed the autoconf bug list and they had some comments.  I didn't really understand what they said, but it sounded like they said that the way KDevelop creates configure.in is wrong or something.  Not sure though.

(Submitted via bugs.kde.org)

More information about the KDevelop-devel mailing list