[prev in list] [next in list] [prev in thread] [next in thread]
List: kdevelop-bugs
Subject: [Bug 131542] New: Some g++ output error messages aren't displayed as
From: greatbunzinni () gmail ! com
Date: 2006-07-30 8:39:28
Message-ID: 20060730103927.131542.greatbunzinni () gmail ! com
[Download RAW message or body]
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.kde.org/show_bug.cgi?id=131542
Summary: Some g++ output error messages aren't displayed as error
messages
Product: kdevelop
Version: 3.3.3
Platform: unspecified
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: general
AssignedTo: kdevelop-bugs kdevelop org
ReportedBy: greatbunzinni gmail com
Version: 3.3.3 (using KDE KDE 3.5.3)
I've noticed when developing a small qmake project that some g++ error messages aren't marked \
as errors in the message output window. For example, let's take the following error message \
taken out of the full compiler log output:
<error output="full">
g++ -o ../bin/direqtchat main.o direqtchat.o mainwindow.o chatwidget.o connectclientdialog.o \
networkengine.o jid.o ui_XmlDump.o ui_ConnectClientDialog.o ui_ConnectServerDialog.o \
ui_mainWindow.o ui_ChatWidget.o moc_mainwindow.o moc_chatwidget.o moc_connectclientdialog.o \
moc_networkengine.o moc_ui_XmlDump.o moc_ui_ConnectClientDialog.o moc_ui_ConnectServerDialog.o \
moc_ui_mainWindow.o moc_ui_ChatWidget.o -L/usr/share/qt3/lib -L/usr/X11R6/lib -lqt-mt -lXext \
-lX11 -lm -lpthread
networkengine.o: In function `NetworkEngine::deliverMessage(JID, JID, \
QString)':networkengine.cpp:(.text+0x5b): undefined reference to `ChatNode::addressMatches(JID \
const&)' :networkengine.cpp:(.text+0xaf): undefined reference to `ChatNode::receiveMessage(JID, \
JID, QString)'
networkengine.o: In function `NetworkEngine::~NetworkEngine()':networkengine.cpp:(.text+0x15f): \
undefined reference to `PostOffice::~PostOffice()'
networkengine.o: In function `NetworkEngine::~NetworkEngine()':networkengine.cpp:(.text+0x2bb): \
undefined reference to `PostOffice::~PostOffice()'
networkengine.o: In function `NetworkEngine::~NetworkEngine()':networkengine.cpp:(.text+0x303): \
undefined reference to `PostOffice::~PostOffice()'
networkengine.o: In function `NetworkEngine::NetworkEngine(QObject*, char \
const*)':networkengine.cpp:(.text+0x367): undefined reference to \
`PostOffice::PostOffice(QObject*, char const*)' :networkengine.cpp:(.text+0x3c4): undefined \
reference to `PostOffice::~PostOffice()'
networkengine.o: In function `NetworkEngine::NetworkEngine(QObject*, char \
const*)':networkengine.cpp:(.text+0x409): undefined reference to \
`PostOffice::PostOffice(QObject*, char const*)' :networkengine.cpp:(.text+0x466): undefined \
reference to `PostOffice::~PostOffice()'
collect2: ld returned 1 exit status
make[1]: *** [../bin/direqtchat] Error 1
make: *** [sub-src] Error 2
*** Exited with status: 2 ***
</error>
that error message, in the very short compiler output mode, is shown like this:
<error output="very short">
linking ../bin/direqtchat (g++)
*** Exited with status: 2 ***
</error>
This makes it impossible to realize what the error was by looking at the very short compiler \
output, which forces the user to switch compiler output modes just to see what whent wrong with \
the compiling process, which isn't very user-friendly.
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic