View Full Version : Latest CVS zone compile
Dominatus
08-03-2003, 08:11 AM
Hey all, I have the latest CVS source and am having problems with the zone compile. The EMSharemem and world compile fine (with just a few warnings) I am using gcc 3.2.3 which I think I read some people have sucessfully compiled with. I changed the mysql include location in the makefile to match my environment and have gotten rid of all the no such file errors. And have added a blank line at the end of parser.cpp. Now I am left with just this:(a little large)
Compile errors (http://www.stailey.net/downloads/compile.errors)
No errors till the end .. only warnings. Is this a version issue?
thanks!
Trumpcard
08-03-2003, 09:09 AM
cvs has been a bit buggy lately (0.5.0) due to some issues with the nightly dumps..
The dumps have been partial, so some stuff could get broken until i get it worked out..
Ducky59
08-03-2003, 09:29 AM
http://forums.eqemu.net/viewtopic.php?t=9642
there is a function near line 152 that needs to be either commented for linux, or put the #ifdef WIN32 around it. That fixxes the error that doesnt show in gcc232
Dominatus
08-03-2003, 11:08 AM
That did it! thanks a bunch!. Now just to try and get some dB data into it :-)
Bigpull
08-03-2003, 11:15 AM
http://forums.eqemu.net/viewtopic.php?t=9642
there is a function near line 152 that needs to be either commented for linux, or put the #ifdef WIN32 around it. That fixxes the error that doesnt show in gcc232
Uhm it shows just fine
parser.cpp: In function `char* itoa(int)':
parser.cpp:155: new declaration `char* itoa(int)'
../common/MiscFunctions.h:59: ambiguates old declaration `const char* itoa(int)
'
parser.cpp: In function `char* itoa(int)':
parser.cpp:155: invalid conversion from `const char*' to `char*'
Dominatus
08-03-2003, 12:54 PM
I think he meant doesn't report as an error during compile. I had all warnings, I grepped for the word error on my output and found only the failure at the end. Being a sysadmin and not a programmer I just look for errors and try to fix them :-)
Bigpull
08-03-2003, 02:08 PM
=) me and that disable BBCode box need to have a few words I think.
Next time try a "grep -v warning"
vBulletin® v3.8.11, Copyright ©2000-2024, vBulletin Solutions Inc.