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.
Compile up to exception. Running "C:\devel\msys\1.0\bin\make.exe -f Makefile CONF=Debug" in C:\Documents and Settings\Adam\NBProjects\HelloApp\helloapp /usr/bin/make -f nbproject/Makefile-Debug.mk SUBPROJECTS= .build-conf make[1]: Entering directory `/c/Documents and Settings/Adam/NBProjects/HelloApp/helloapp' cd ../hello1lib && /usr/bin/make -f Makefile CONF=Debug make[2]: Entering directory `/c/Documents and Settings/Adam/NBProjects/HelloApp/hello1lib' /usr/bin/make -f nbproject/Makefile-Debug.mk SUBPROJECTS= .build-conf make[3]: Entering directory `/c/Documents and Settings/Adam/NBProjects/HelloApp/hello1lib' make[3]: Nothing to be done for `.build-conf'. make[3]: Leaving directory `/c/Documents and Settings/Adam/NBProjects/HelloApp/hello1lib' A java.util.EmptyStackException exception has occurred. Please report this at http://www.netbeans.org/community/issues.html, including a copy of your messages.log file as an attachment. The messages.log file is located in your C:\Documents and Settings\Adam\.netbeans\5.5.1\var\log folder. A java.util.EmptyStackException exception has occurred. Please report this at http://www.netbeans.org/community/issues.html, including a copy of your messages.log file as an attachment. The messages.log file is located in your C:\Documents and Settings\Adam\.netbeans\5.5.1\var\log folder. When I quit IDE I get asked if I want to kill the build processes
Created attachment 43482 [details] Log as asked for.
Here us the proof that I can compile. Adam@KIWI /c/Documents And Settings/Adam/NBProjects/HelloApp/helloapp $ make make -f nbproject/Makefile-Debug.mk SUBPROJECTS= .build-conf make[1]: Entering directory `/c/Documents And Settings/Adam/NBProjects/HelloApp/helloapp' cd ../hello1lib && make -f Makefile CONF=Debug make[2]: Entering directory `/c/Documents And Settings/Adam/NBProjects/HelloApp/hello1lib' make -f nbproject/Makefile-Debug.mk SUBPROJECTS= .build-conf make[3]: Entering directory `/c/Documents And Settings/Adam/NBProjects/HelloApp/hello1lib' make[3]: Nothing to be done for `.build-conf'. make[3]: Leaving directory `/c/Documents And Settings/Adam/NBProjects/HelloApp/hello1lib' make[2]: Leaving directory `/c/Documents And Settings/Adam/NBProjects/HelloApp/hello1lib' cd ../hello2lib && make -f Makefile CONF=Debug make[2]: Entering directory `/c/Documents And Settings/Adam/NBProjects/HelloApp/hello2lib' make -f nbproject/Makefile-Debug.mk SUBPROJECTS= .build-conf make[3]: Entering directory `/c/Documents And Settings/Adam/NBProjects/HelloApp/hello2lib' make[3]: Nothing to be done for `.build-conf'. make[3]: Leaving directory `/c/Documents And Settings/Adam/NBProjects/HelloApp/hello2lib' make[2]: Leaving directory `/c/Documents And Settings/Adam/NBProjects/HelloApp/hello2lib' mkdir -p build/Debug/MinGW-Windows g++.exe -c -g -o build/Debug/MinGW-Windows/main.o main.cc In file included from c:/devel/mingw/bin/../lib/gcc/mingw32/3.4.2/../../../../include/c++/3.4.2/backw ard/iostream.h:31, from main.cc:20: c:/devel/mingw/bin/../lib/gcc/mingw32/3.4.2/../../../../include/c++/3.4.2/backw ard/backward_warning.h:32:2: warning: #warning This file includes at least one deprecated or antiquated header. Please consider using one of the 32 headers found in section 17.4.1.2 of the C++ standard. Examples include substituting the <X> header for the <X.h> header for C++ includes, or <iostream> instead of the deprecated header <iostream.h>. To disable this warning use -Wno- deprecated. mkdir -p dist/Debug g++.exe -o dist/Debug/helloapp build/Debug/MinGW- Windows/main.o ../hello1lib/dist/Debug/libhello1lib.a ../hello2lib/dist/Debug/l ibhello2lib.a make[1]: Leaving directory `/c/Documents And Settings/Adam/NBProjects/HelloApp/helloapp'
By the way, please do not use the 'nbbuild' component for IDE problems. If you are unsure what component to use, choose 'ide' and it will be reassigned.
may be IZ duplicate 105444 ?
This is the same defect which has been reported under IZ 105444. *** This issue has been marked as a duplicate of 105444 ***
Please could you explain to me how I can fix this issue. This is a fresh install of CND for me and I did not expect any issues.
> Please could you explain to me how I can fix this issue. This is a fresh install of CND for > me and I did not expect any issues. At this point, the fix is in the grgich_hills branch and is not available other than by doing your own build. If you want to do that, email me at gordon.prieur@sun.com. Otherwise, the fix won't be available in a release or patch until mid to late summer (we don't even have exact dates yet).