Date: Wed, 5 Jul 2006 07:46:51 -0500 From: Jonathan Fosburgh <jonathan@fosburgh.org> To: freebsd-ports@freebsd.org, "Justin T. Gibbs" <gibbs@scsiguy.com> Subject: Re: Fixing VNC port(s) for AMD64 Message-ID: <200607050746.58629.jonathan@fosburgh.org> In-Reply-To: <59892F1BBCF4052B1E3EFAFF@aslan.scsiguy.com> References: <59892F1BBCF4052B1E3EFAFF@aslan.scsiguy.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--nextPart21796252.sMFzl4KjAZ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Tuesday 04 July 2006 22:41, Justin T. Gibbs wrote: > So I'm new to AMD64 and was surprised by the lack of VNC > support for this platform. Its been a while since I've > hacked ports (like more years than I have fingers on one > hand), but I figured it couldn't be that hard to fix up one > of the VNC ports and submit my work back. > > Boy was I wrong. > My experiences trying to fix NXwindows for AMD64 were quite similar. A bett= er=20 solution would be to get the vendors to update their code to either a newer= =20 XF86 or Xorg. I think both VNC and NX use XFree 4.3 or earlier which do no= t=20 support amd64 (though they seem to support ia64). It seems to me that Linux= =20 users would have the same problems that we do. =2D-=20 Jonathan Fosburgh AIX and Storage Administrator UT MD Anderson Cancer Center Houston, TX --nextPart21796252.sMFzl4KjAZ Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.4 (FreeBSD) iD8DBQBEq7TCqUvQmqp7omYRAsL2AKCDFU82vZcu+fPAPh8FWoqnKWdYTACdEFWU WXxGIsQjSHFguAGc+Z89t8c= =W447 -----END PGP SIGNATURE----- --nextPart21796252.sMFzl4KjAZ--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200607050746.58629.jonathan>