|
Is this a known bug or am I dumb? |
me also
Member #7,731
September 2006
|
Finally reinstalled allegro, devcpp and all that put the -lalleg in its proper place, linked the liballeg.a to the project, did a full compile and... boom, pretty big error that came out, all the while insisting that my #include <allegro.h> line is the culprit, just when I thought the compiler and me could get along... this is the error:
Any bright ideas why I get more than 150 pages of errors? |
Richard Phipps
Member #1,632
November 2001
|
Quote: g++.exe -c base.cpp -o base.o -I"C:/DevCpp/include/c++" -I"C:/DevCpp/include/c++/mingw32" -I"C:/DevCpp/include/c++/backward" -I"C:/DevCpp/include" Where is your -lalleg call? |
me also
Member #7,731
September 2006
|
Tools / compiler options / "add the folowing comands when calling compiler" box Thats where I put it. |
Neil Walker
Member #210
April 2000
|
Maybe that option doesn't work. Most things don't work properly in DevC++. Try adding it to usual place. Neil. wii:0356-1384-6687-2022, kart:3308-4806-6002. XBOX:chucklepie |
me also
Member #7,731
September 2006
|
Whats the usual place ? I dont rember where I put it last time I installed ^^' |
Peter Hull
Member #1,136
March 2001
|
This is a compiling error, not a linking error. Stop messing about and show us base.cpp please. Pete
|
me also
Member #7,731
September 2006
|
Well, wish it were, but the code worked fine and smooth the very day before I formated my computer, afther formating I've reinstaled everything and now not only it doesnt work, but it gives this weird error, and I still ahvent touched the my code. But If you think I'd help, here it is:
|
BAF
Member #2,981
December 2002
|
RP: He doesn't need -lalleg for that portion because he's not linking, just compiling to an object file. Now, what is this base.h that allegro.h is including? [edit] Quote:
Internal compiler error: Error reporting routines re-entered.
I got the same error one time compiling wxWidgets, and upgrading my gcc fixed it. |
|