pls help

Posted by Gorock on Mon 03 Sep 2007 10:04 AM — 13 posts, 39,936 views.

#0
i just got the new smaug1.8 i unpacked it and when i compiled it here is what i got

make -s smaug
Compiling o/imc.o....
Compiling o/act_comm.o....
Compiling o/act_info.o....
Compiling o/act_move.o....
Compiling o/act_obj.o....
Compiling o/act_wiz.o....
Compiling o/ban.o....
Compiling o/boards.o....
Compiling o/build.o....
Compiling o/chess.o....
Compiling o/clans.o....
Compiling o/color.o....
Compiling o/comm.o....
comm.c: In function `void nanny_get_name(DESCRIPTOR_DATA*, char*)':
comm.c:1853: warning: comparison is always false due to limited range of data
type
comm.c:1921: warning: comparison is always false due to limited range of data
type
comm.c: In function `void nanny_get_old_password(DESCRIPTOR_DATA*, char*)':
comm.c:2016: warning: comparison is always false due to limited range of data
type
make[1]: *** [o/comm.o] Error 1
make: *** [all] Error 2


im not sure what else you'll need to know to help me but i am lost and dunno what to do thank you for any help in advance
USA #1
It would be a little helpful to see the lines in question so we can figure out what is going on. But, one likely culprit is that you are running on a 64-bit system, and none of the SMAUG devs tested on it; so, they didn't code 64-bit-safe code.
#2
1853
if( check_playing( d, argument, FALSE ) == BERR )
{
write_to_buffer( d, "Name: ", 0 );
return;
}

fOld = load_char_obj( d, argument, TRUE, FALSE );
if( !d->character )
{
log_printf( "Bad player file %s@%s.", argument, d->host );
write_to_buffer( d, "Your playerfile is corrupt...Please notify Thoric@mud.compulink.com.\r\n", 0 );
close_socket( d, FALSE );
return;
}



1921

chk = check_reconnect( d, argument, FALSE );
if( chk == BERR )
return;

if( chk )
{
fOld = TRUE;
}
else
{
if( sysdata.wizlock && !IS_IMMORTAL( ch ) )
{
write_to_buffer( d, "The game is wizlocked. Only immortals can connect now.\r\n", 0 );
write_to_buffer( d, "Please try back later.\r\n", 0 );
close_socket( d, FALSE );
return;
}
}




2016


write_to_buffer( d, echo_on_str, 0 );

if( check_playing( d, ch->pcdata->filename, TRUE ) )
return;

chk = check_reconnect( d, ch->pcdata->filename, TRUE );
if( chk == BERR )
{
if( d->character && d->character->desc )
d->character->desc = NULL;
close_socket( d, FALSE );
return;
}
if( chk == TRUE )
return;


i believe this should be all of it

also ive run smaug 1.4a on this same server
USA #3
Could you please give:
- the value of BERR (it should be in mud.h somewhere)
- the return value of check_playing, and the type of 'chk' (from line 1921)
- the compiler you are using (name and version)

Looks like this probably isn't a 64-bit issue after all.
#4
ok i talked to the server admin and he said its not 64 bit
so is this a prolem that can be solved by switching to an older version of smaug or what will i need to do
USA #5
Those are just warnings. The compiler shouldn't stop for those. I know I get those same warnings for different things, and mine compiles fine.
#6
ok i downloaded smaug 1.7 and it compiled and is up and running i suppose i can run this version seeing as how there aren't too many differences thanks for the help though :)
USA #7
Wait, what? There is no Smaug 1.7...
USA #8
Quote:
so is this a prolem that can be solved by switching to an older version of smaug or what will i need to do

I already said it probably wasn't 64-bit, and also gave you a list of things to provide so that we could help you. :)

Quote:
Wait, what? There is no Smaug 1.7...

He probably meant FUSS.
USA #9
In that case, the differences between 1.7 and 1.8 are pretty big.
#10
yeah i meant fuss but everything is running and there aren't any bugs so i can start working on everything now
#11
i think the problem is the way i am unpacking it i am using the command tar -zxvf (file) is that the proper way to do it?
USA #12
Yes, that's the way to unpack a tgz archive.