[EMAIL PROTECTED]:[~] $ echo $LANG en_US.UTF-8 [EMAIL PROTECTED]:[~] $ echo $SUPPORTED
[EMAIL PROTECTED]:[~] $ echo $TERM vt100 [EMAIL PROTECTED]:[~] $ - Valnir -----Original Message----- From: Michael Barton [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 22, 2006 7:25 PM To: Nathan Kodak Cc: [email protected] Subject: Re: Compile Warnings. On 11/22/06, Valnir <[EMAIL PROTECTED]> wrote: > I'll check the socklen_t. Thanks for the idea. Could it be a 64-bit kernel, > even though it's got a 32-bit (AMD Athlon XP 3000+) processor? OH, probably not then. I guess they changed the declaration of socklen_t in the newer kernel. Strange, that. > I am copying out of SecureCRT from being SSH'd into the box. It shows that > way in the SSH window. I think it shows that way at the console as well. The > ~ and (tm) aren't there, but the aE is... It's more an annoyance than a > requirement. Thanks for any input though. I've seen it happen before, but I'm not sure what causes it. Terminal settings are voodoo to me. Out of curiosity, what do "echo $LANG", "echo $SUPPORTED", and "echo $TERM" show? --Palrich. > - Valnir > > > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of > Michael Barton > Sent: Wednesday, November 22, 2006 5:23 PM > To: [email protected] > Subject: Re: Compile Warnings. > > The difference is probably that your new host is running a 64-bit kernel. > > Make sure size is defined as a socklen_t. That's the convention on Linux and > BSD. > > Unixes that don't have a TCP stack based on BSD's differ on the type of > pointer that goes there, and unsigned int was the most portable thing to do > before 64-bit machines came around. > > As for the weird quote characters, I have no idea. It looks like > UTF-8 flattened to ASCII (on account of the multiple bytes in the > extended-ascii range for each character). What apps are you copying them > from and to? > > > > > On 11/22/06, Valnir <[EMAIL PROTECTED]> wrote: > > Hey guys. Everyone was complaining about not having any traffic on > > this list, so here's something to get you thinking over the long weekend. > > > > I am running my mud on WolfPaw and everything compiles perfect. No > > errors, no warnings. All good. I am thinking about moving where my > > mud is hosted though. The new server is running Fedora Core 5 with > > GCC > > 4.1.1 and I get an interesting compliation warning: > > > > gcc -c -Wall -g3 comm.c > > comm.c: In function ‘init_descriptor’: > > comm.c:986: warning: pointer targets in passing argument 3 of > > ‘getsockname’ differ in signedness > > comm.c:987: warning: pointer targets in passing argument 3 of > > ‘accept’ differ in signedness > > comm.c:1010: warning: pointer targets in passing argument 3 of > > ‘getpeername’ differ in signedness > > > > It's a clean make, so I know it's getting all the Fedora header > > files with nothing left over from the WolfPaw build. I went ahead > > and tried to run it to see what it would do, but as I expected > > (since the warning is in the descriptor stuff) it crashed as soon as I > > tried to log in. > > > > Also, just on a side note. Any idea how to get the ‘accept’ to > > show up as `accept' instead? > > > > Thanks! > > > > - Valnir > > > > -- > > ROM mailing list > > [email protected] > > Unsubscribe here ->>> > > http://www.rom.org/cgi-bin/mailman/listinfo/rom > > > -- > ROM mailing list > [email protected] > Unsubscribe here ->>> http://www.rom.org/cgi-bin/mailman/listinfo/rom > > > -- ROM mailing list [email protected] Unsubscribe here ->>> http://www.rom.org/cgi-bin/mailman/listinfo/rom
