This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
I noticed this problem when I tried to eliminate warning messages, that appear during building sample project Quote. If I modify file system.cc and press "Build Project" button, there are over 100 (!) identical "blue" messages in output window: system.cc:52: warning: comparison between signed and unsigned integer expressions system.cc:52: warning: comparison between signed and unsigned integer expressions system.cc:52: warning: comparison between signed and unsigned integer expressions system.cc:52: warning: comparison between signed and unsigned integer expressions ... From command line it works just fine. ===================================== bash-3.1$ cd c:/tmp/nikm/Quote1 bash-3.1$ g++ -c -g -Wall -o build/Debug/GNU-Windows/system.o system.cc system.cc: In member function `Module* System::GetModule(int)': system.cc:52: warning: comparison between signed and unsigned integer expression s system.cc:54: warning: control reaches end of non-void function bash-3.1$ I use build 060809 (Aug 09 2006) on Windows XP with latest Cygwin compilers. I set high priority P2, because it is very visible problem.
Just want to add: In case of uncompilabe code you will not see the reason of build fail(after all warning messages).
*** Issue 82579 has been marked as a duplicate of this issue. ***
*** Issue 80389 has been marked as a duplicate of this issue. ***
*** Issue 82639 has been marked as a duplicate of this issue. ***
This problem results from a change to o.n.m.cnd.execution.OutputWindowWriter (version 1.1.2.7). In this change a zero length file named ".fail" is created in the directory of a file causing an error. However, the file is never removed so the next time an error is found in the same directory, the creation of the ".fail" file fails and throws an uncaught FSException. Checkin comments are vague as to what this fix helps: "Added hack to obtain fail from execution". As a temporary fix I'm commenting out the FileObject.createData calls. This may break the intended functionality, but the current problems breaks very simple builds and seems much more serious. I'll reassign to Michal Skvor so he can fix his change.
*** Issue 83533 has been marked as a duplicate of this issue. ***
*** Issue 84976 has been marked as a duplicate of this issue. ***
Since this is fixed in cnd and is being tracked as unfixed, I'm closing it as fixed. Michal can open a related IZ if he needs to track the ".fail" file feature Mobility used.
*** Issue 85499 has been marked as a duplicate of this issue. ***
Verified in build 20080204