Bug #12098 2007-09-30 13:10
moonkid
doesn't parse any link errors
I am using the nightlys with MinGW. CB doesn't parse linker output correct. That is the build log: [buildlog] -------------- Build: Dynamic Debug Unicode in blackfisk --------------- mingw32-g++.exe -LC:\wxWidgets\lib\gcc_dll -LC:\Programme\CodeBlocks\lib -o .\blackfiskDud.exe .objs_debud\BFAboutDlg.o .objs_debud\BFApp.o .objs_debud\BFBackupLog.o .objs_debud\BFBackupQuestionDlg.o .objs_debud\BFBackupTree.o .objs_debud\BFCmdLine.o .objs_debud\BFCore.o .objs_debud\BFCore_traverser.o .objs_debud\BFDestinationCtrl.o .objs_debud\BFDestinationCtrl2.o .objs_debud\BFDestinationDlg.o .objs_debud\BFDirCtrl.o .objs_debud\BFHelpCtrl.o .objs_debud\BFHyperlinkCtrl.o .objs_debud\BFIconTable.o .objs_debud\BFLog.o .objs_debud\BFLogBase.o .objs_debud\BFLogViewDlg.o .objs_debud\BFMainFrame.o .objs_debud\BFMessageDlg.o .objs_debud\BFMsgObserver.o .objs_debud\BFPlaceholderButton.o .objs_debud\BFProgressCtrl.o .objs_debud\BFProjectSettings.o .objs_debud\BFProjectSettingsCtrl.o .objs_debud\BFProjectSettingsDlg.o .objs_debud\BFRootTask.o .objs_debud\BFSettings.o .objs_debud\BFSettingsDlg.o .objs_debud\BFSettingsDlg2.o .objs_debud\BFSystem.o .objs_debud\BFTask.o .objs_debud\BFTaskBase.o .objs_debud\BFTaskDlg.o .objs_debud\BFTaskProgressDlg.o .objs_debud\BFThread_ProjectRunner.o .objs_debud\BFwxLog.o .objs_debud\ObserverPattern.o .objs_debud\Progress.o .objs_debud\blackfisk.o .objs_debud\wxSerialize\src\wxSerialize.o -lwxzlibd -lwxmsw29ud -mwindows .objs_debud\BFRootTask.o: In function `ZNSt6vectorIP6BFTaskSaIS1_EEixEj': C:/Programme/CodeBlocks/bin/../lib/gcc/mingw32/3.4.4/../../../../include/c++/3.4.4/bits/stl_vector.h:(.bss+0x0): multiple definition of `BF_EVENT_THREAD_END' .objs_debud\BFMainFrame.o:C:/wxWidgets/include/wx/window.h:(.bss+0x0): first defined here .objs_debud\BFThread_ProjectRunner.o: In function `ZN8wxStringC1EPKw': C:/wxWidgets/include/wx/string.h:(.bss+0x0): multiple definition of `BF_EVENT_THREAD_END' .objs_debud\BFMainFrame.o:C:/wxWidgets/include/wx/window.h:(.bss+0x0): first defined here collect2: ld returned 1 exit status Process terminated with status 1 (0 minutes, 8 seconds) 0 errors, 0 warnings [/buildlog] You see the 0 errors and 0 warnings? CB doesn't see that there is error from the linker. The binary is not build and CB wonder if the executable is not available after a "build&run". That is in my "build messages" .objs_debud\BFRootTask.o:: In function `ZNSt6vectorIP6BFTaskSaIS1_EEixEj': .objs_debud\BFThread_ProjectRunner.o:: In function `ZN8wxStringC1EPKw': :: === Build finished: 0 errors, 0 warnings ===
- Category
- Compiler
- Group
- Status
- Open
- Close date
- Assigned to
History
polygon7 2007-10-11 11:18
Hi,
I think it is something similar to:
[ Bug #11586 ] [DJGPP] Build log don't catch error/warning messages...