Bug#41967: marked as done ("next error" or click on error line does not open source file) by Harald Fernengel <harry at kdevelop.org>

[Stephan Kulow]

Your message with subj: Bug#41967: "next error" or click on error line does not open source file

This is a FAQ: http://www.kdevelop.org/index.html?filename=3Dfaq.html#40

SuSE 8.0 ships a localized version of make so KDevelop can't parse the outp=
ut=20
anymore. Use the newest KDE_2_2_BRANCH or latest Gideon, it is fixed there.

Also, don't tell make to be quiet, KDevelop needs the make output to open t=
he=20
right files...

Best regards,
Harry

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; 30 Apr 2002 14:11:28 +0000
Received: (qmail 11857 invoked by uid 33); 30 Apr 2002 14:11:28 -0000
Date: 30 Apr 2002 14:11:28 -0000
Message-ID: <20020430141128.11856.qmail at mail.kde.org>
To: submit at bugs.kde.org
Subject: "next error" or click on error line does not open source file
From: sgmd at genetik.fu-berlin.de
X-KDE-Received: -160.45.46.20

Package:           kdevelop
Version:           2.1 (using KDE 3.0.5 CVS/CVSup/Snapshot)
Severity:          normal
Installed from:    Compiled sources
Compiler:          gcc 2.95.3
OS:                Linux
OS/Compiler notes: SuSE 8.0

Hi,

I am not sure if this is a problem of kdevelop, but here it goes: whenever you click on an error line in the message window or if you select "view->next error" a message pops up saying that this file does not exist in the in the main project directory. It fails to search in the actual source directory. Tested with an own c++ project and with a wizard-made kde-programm. This happens with kdevelop 2.1 from SuSE rpms as well as with a fresh CVS checkout of kdevelop. I only wonder why nobody else reported this. Do I have to configure something to get the kdevelop 2-behavior back?

Best regards, 

Thomas

(Submitted via bugs.kde.org)