vnc port still does not work..

Kris Kennaway kris at obsecurity.org
Fri Apr 22 06:31:09 PDT 2005


On Fri, Apr 22, 2005 at 07:22:58AM -0400, Jason wrote:
> > Have you given tightvnc a try, AFAIK tightvnc is a little bit more
> > "maintained" and "current" than RealVNC (see: network optimizations and
> > the likes)
> both tightvnc and tridiavnc give the same result.
> [jason at shonuff]$ pwd   
> /usr/ports/net/tightvnc
> [jason at shonuff]$ make install clean
> ===>  tightvnc-1.2.9 is marked as broken: Does not compile on !i386.
> ===>  Cleaning for libiconv-1.9.2_1
> etc..

This is evidence that the VNC-derived codebase has problems on !i386.
You could also look for a large number of warnings during compilation
as more evidence that it wasn't written for 64-bit targets.  However
you should compare your config to a working config on i386 to rule out
configuration problems.

Also take this up with the developers, since they're the ones who
should fix any non-portability of their code.

Kris
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-sparc64/attachments/20050422/4ed3cf0a/attachment.bin


More information about the freebsd-sparc64 mailing list