From kde-core-devel Mon Aug 12 09:20:38 2002 From: Thiago Macieira Date: Mon, 12 Aug 2002 09:20:38 +0000 To: kde-core-devel Subject: Re: Success: kde 3.1 cvs running on sgi IRIX! X-MARC-Message: https://marc.info/?l=kde-core-devel&m=102914425030516 =2D----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 a_sturm@naimasoft.com wrote: >Thiago Macieira schrieb am 12.08.2002, 09:20:06: >> >Where should socklen_t be defined? >> >> In the system headers. I think sys/socket.h, but I'm not sure. If this >> were a KDE application, I'd recommend using ksocklen_t from ksockaddr.h. >> >> I think the configure script will need an additional test for the presen= ce >> of that type and, if not defined, use "unsigned" instead. >> >> Want a patch? > >Well, i surely was grepping all headerfiles for socklen_t; but it didn't >turn up anything.... I would be verry pleased if you could make a patch! Actually, I've been taking a look at the code in libvncserver and we're a b= it=20 out of luck here. Since it's not part of KDE code, it doesn't include=20 config.h, so Autoconf tests won't help. Anyways, the code is perfectly valid POSIX code. It's your system that does= n't=20 provide socklen_t... :/ My suggestion is that you edit rfb.h, and add a section like: #ifdef __IRIX__ typedef unsigned socklen_t; #endif >:-)) I going to read the diff man page today to supply patches the next diff -u originalfile newfile or, in case of dirs: diff -ur originalpackage modifiedpackage if you're using code obtained from CVS, it's even easier: cvs diff -u (note: some older versions of diff don't support -u Unified Diff) =2D --=20 Thiago Macieira - UFOT Registry number: 1001 thiagom@mail.com ICQ UIN: 1967141 PGP/GPG: 0x6EF45358 Registered Linux user #65028 =2D----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE9V33mM/XwBW70U1gRAgQSAJ9DWFzCl/j3krHFRwuh+z1HzC/i2ACfdwZ3 whhHVRI3Hkij3xxt2uODVSs=3D =3Dnu3o =2D----END PGP SIGNATURE-----