Really, the compilation was not successful. "Information: Total errors: 0, Size of output: 0"
I know there are errors! I want to see the errors! I want to know about the unresolved references! OS is WinME (I know it's embarassing).
This is some seriously old-butt DOS legacy code, could be c, c++ or both. Lots of headers.
Don't know what all libs it needs. I'm hoping the linker can tell me what's missing. Tried rebuilding for c and c++, same result. Trying to compile as a console piece as it was never intended for Windows, then tried GUI. The source code directory is c:\acquYanB.
Here's the log:
I can only suggest that you post the content of makefile.win. I have never seen this before, but I have seen makefile corruption caused by pre-processor errors. Dev-C++ uses the C pre-processor to generate the dependency lists for the makefile, and pre-processor errors in an older version of Dev-C++ would cause the makefile to be incorrectly generated. Since you say you have a large number of headers of unknown provenance, it is possible that you have a pre-processor error. You did not specify what version you were using - make sure it is 4.9.9.2.
It might be easier if this code is publicly available for you to simply post a link to it so it can be tested.
Clifford
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Why is the log missing the <newline> between the rm command and gcc command? And also between the gcc compilation and the g++ link command? And then the g++ command and the "Execution terminated" message?
If the log is genuine, it seems that the make file generation may have failed somehow, and concatenated the command lines into a single rm command. which will execute without error, but produce nothing.
If it is C code it will likely have a source file ending in .c and for C++ ending in .cpp. You therefore almost certainly have C code, but you appear to be invoking the linker through the C++ compiler. C compilation has been used automatically based on the extension, but you have set the project as C++ hence invoking the linker through g++. This is probably OK, the other way around it does not work if you use C++ standard libraries without explicitly linking them.
From your confusion about which language it is (how could you not know!?), it sounds like you may have been 'fiddling' too much, and I suggest that you start again with a clean project (you are using a project, right?).
Clifford
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have started with a new project per your suggestion because, yes, I have been 'fiddling' a lot. Here is the new log. Same result - builder produces nothing.
Thanks for pointing out the log file flaw. I don't really know what happened but I uninstalled K7 Antivirus and uninstalled LADsoft c/c++ IDE and now it semms to be working. The antivirus must have been killing the process? Now I have 31 errors and I am happy as heck about it. Thank you for your help in understanding the logfile and preprocessor.
Chickenwater
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Sometimes it seems that anti-virus tools are almost bad as the problem from which the seek to protect you. I recently discovered that on Vista, with AVG Free 7.5 installed, if you insert an SD card and then remove it, thereafter upon inserting the SD card it will not mount until you reboot! And this is not the only example of Anti-virus tools preventing Dev-C++ from working.
These symptoms however are unique as far as I am aware, so it is great that you reported back your discovery in case anyone else has the problem in the future. Thanks.
Clifford
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Really, the compilation was not successful. "Information: Total errors: 0, Size of output: 0"
I know there are errors! I want to see the errors! I want to know about the unresolved references! OS is WinME (I know it's embarassing).
This is some seriously old-butt DOS legacy code, could be c, c++ or both. Lots of headers.
Don't know what all libs it needs. I'm hoping the linker can tell me what's missing. Tried rebuilding for c and c++, same result. Trying to compile as a console piece as it was never intended for Windows, then tried GUI. The source code directory is c:\acquYanB.
Here's the log:
The source code directory is c:\acquYanB.
Compiler: Default compiler
Building Makefile: "C:\acquYanB\Makefile.win"
Executing make clean
rm -f ../acquYanB/acqu.o acqu.exegcc.exe -c acqu.c -o ../acquYanB/acqu.o -I"C:/DEV-CPP/include" -I"C:/acquYanB" -traditional-cpp -fmessage-length=0g++.exe ../acquYanB/acqu.o -o "acqu.exe" -L"C:/DEV-CPP/lib" -L"C:/acquYanB" -L"C:/acquYanB/objects" -fmessage-length=0 Execution terminated
Compilation successful
I know I am doing something wrong, I just don't know what!
Any insight you can give would be awesome. THANKS - Chickenwater.
>> I think that the log is genuine.
That may be, but it was still 'abnormal', your new log exhibits the same flaw. A normal one would look like this:
Compiler: Default compiler
Building Makefile: "C:\acquYanB\Makefile.win"
Executing make clean
rm -f acqu.o acqu.exe
gcc.exe -c acqu.c -o acqu.o -I"C:/DEV-CPP/include" <-----NEWLINE HERE!!!
gcc.exe acqu.o -o "acqu.exe" -L"C:/DEV-CPP/lib"
Execution terminated
Compilation successful
I can only suggest that you post the content of makefile.win. I have never seen this before, but I have seen makefile corruption caused by pre-processor errors. Dev-C++ uses the C pre-processor to generate the dependency lists for the makefile, and pre-processor errors in an older version of Dev-C++ would cause the makefile to be incorrectly generated. Since you say you have a large number of headers of unknown provenance, it is possible that you have a pre-processor error. You did not specify what version you were using - make sure it is 4.9.9.2.
It might be easier if this code is publicly available for you to simply post a link to it so it can be tested.
Clifford
Why is the log missing the <newline> between the rm command and gcc command? And also between the gcc compilation and the g++ link command? And then the g++ command and the "Execution terminated" message?
If the log is genuine, it seems that the make file generation may have failed somehow, and concatenated the command lines into a single rm command. which will execute without error, but produce nothing.
If it is C code it will likely have a source file ending in .c and for C++ ending in .cpp. You therefore almost certainly have C code, but you appear to be invoking the linker through the C++ compiler. C compilation has been used automatically based on the extension, but you have set the project as C++ hence invoking the linker through g++. This is probably OK, the other way around it does not work if you use C++ standard libraries without explicitly linking them.
From your confusion about which language it is (how could you not know!?), it sounds like you may have been 'fiddling' too much, and I suggest that you start again with a clean project (you are using a project, right?).
Clifford
Hi Clifford.
I think that the log is genuine. Anyway-
I have started with a new project per your suggestion because, yes, I have been 'fiddling' a lot. Here is the new log. Same result - builder produces nothing.
Compiler: Default compiler
Building Makefile: "C:\acquYanB\Makefile.win"
Executing make clean
rm -f acqu.o acqu.exegcc.exe -c acqu.c -o acqu.o -I"C:/DEV-CPP/include"
gcc.exe acqu.o -o "acqu.exe" -L"C:/DEV-CPP/lib"
Execution terminated
Compilation successful
Does this make sense? Thanks!
Chickenwater
Thanks for pointing out the log file flaw. I don't really know what happened but I uninstalled K7 Antivirus and uninstalled LADsoft c/c++ IDE and now it semms to be working. The antivirus must have been killing the process? Now I have 31 errors and I am happy as heck about it. Thank you for your help in understanding the logfile and preprocessor.
Chickenwater
Sometimes it seems that anti-virus tools are almost bad as the problem from which the seek to protect you. I recently discovered that on Vista, with AVG Free 7.5 installed, if you insert an SD card and then remove it, thereafter upon inserting the SD card it will not mount until you reboot! And this is not the only example of Anti-virus tools preventing Dev-C++ from working.
These symptoms however are unique as far as I am aware, so it is great that you reported back your discovery in case anyone else has the problem in the future. Thanks.
Clifford