Compile problems on Mac OS X
kplloyd "at" lucent.com
Tue Jun 3 15:24:00 2003
I too wish I had read this thread earlier.
I have been using the X11 VNC on Mac OS X.2.x for
many months, having obtained it via Fink:
I had no problems with the 3.3.7-1 installation,
aside from realizing that I needed the free Apple
While Fink puts version 3.3.7-1 in the "unstable"
(as opposed to "stable") category, I use the viewer
almost every day without incident. It's great!
In an email to me a couple months ago, the maintainer
wrote, "It won't become "stable" until more people
One note is that copy/paste between VNC windows
and Aqua may need copy/pasting into *intermediate*
xterm windows (vncserver xterm, Apple X11 xterm,
Another note is that the X11 vncserver comes with this
Fink package, too! Of course, you just get X11, not
Aqua as you get with OSXVNC. But of course with the
X11 vncserver, you have the ability to create multiple
virtual desktops and have them all active at once!
BTW, I haven't checked how the GET_PIXEL problems were
avoided in the Fink package.
BTW2, I notice that tightvnc is also available via Fink,
though I haven't tried it.
PS - Fink rules!
Adrian Umpleby wrote:
> Hi all,
> Wish I'd noticed this thread over the weekend, else I would have got
> back sooner with a much simpler fix for you that I used quite a while
> ago to get vncviewer going under OS X...
> The basic problem appears to be with the definition of GET_PIXEL in
> hextile.c - my guess is that it does not like the fact that GET_PIXEL is
> being defined, but is also part of that definition...?
> i.e. this line in hextile.c:
> #define GET_PIXEL CONCAT2E(GET_PIXEL,BPP)
> The simple fix is to change GET_PIXEL to something else, like GET_PIXELBPP:
> #define GET_PIXELBPP CONCAT2E(GET_PIXEL,BPP)
> Then change the line in hextile.c that uses GET_PIXEL from:
> GET_PIXEL(fg, ptr);
> GET_PIXELBPP(fg, ptr);
> All should then compile fine!
> (Hey vnc developers - might be well worth fixing this in the vnc source...)
> VNC-List mailing list
> VNC-List "at" realvnc.com
> To remove yourself from the list visit: