Re: Fw: VNC Question: VNC 4.1.2 and XFree86 4.6.0 compilation errors

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



I have tried TightVNC, but still get errors:

WaitFor.c: In function 'WaitForSomething':
WaitFor.c:174: error: 'fd_set' has no member named 'fds_bits'
WaitFor.c:174: error: 'fd_set' has no member named 'fds_bits'
WaitFor.c:174: error: 'fd_set' has no member named 'fds_bits'
{...same error different line #'s for 210 more times}

I have no clue how to handle this one....

--David


> On Fri, 4 May 2007, David A. Gershman wrote:
> 
> -> I'm building my own Linux box from the ground up (LFS 6.2 base) and
> -> have gotten to the point of RealVNC.  I have a compiled (or uncompiled
> -> available) source tree for XFree86 4.6.0.  After having to patch one
> -> small file, it compiled fine and is working with no problems.  On to
> -> RealVNC...
> 
> If you don't get this working for some reason, you might think about 
> http://www.tightvnc.com/, which is the VNC setup I'm using now. It
even has a 
> Java client that you can use to access your system from a browser via
a Java 
> applet. The Xvnc server didn't need an X source tree (comes with a
stripped 
> down one) so has less places to go wrong. As I remember it didn't
build 100% 
> out of the box, but the changes were minor and doable by someone
building his 
> own system.
> 
> 
> -> /usr/X11R6/lib/libXt.so: undefined reference to `XkbLookupKeySym'
> -> collect2: ld returned 1 exit status
> -> make[7]: *** [xdmxconfig] Error 1
> 
> When the app was made (RealVNC), they may have programmed it against an 
> earlier version of some libraries, which had the symbol defined that is 
> causing the error. Later it was maybe removed, and the program never 
> re-written to take this into account. You see this when functions get 
> ripped out, or re-named, etc.
> 
> I'm no XFree86 or RealVNC programmer, I'm just relating what I've seen 
> while building sources.
> 
> -> Which would lead one to think XFree86 has the error.  But if that's
> -> the case then why didn't this error show up when compiling XFree86
> -> _without_ VNC?
> 
> The error probably doesn't sit within either, but *between* them (eg,
their 
> interaction).
> 
> HSTH (hope something there helps)
> 
> 
> -- 
> [* Microsoft Security Advisory No. #4,935,964: *]
>   "Vulnerability in Useless RPC Service Listening On 28
>   Different Ports (URSLO2DP) on Windows Allows Still
>   More Remote Code Execution."
>    <*yawn*> ...Elsewhere, paint is drying. News at 11.
> _______________________________________________
> XFree86 mailing list
> XFree86@xxxxxxxxxxx
> http://XFree86.Org/mailman/listinfo/xfree86
> 
> 

---------------
David A. Gershman
gershman@xxxxxxxxxxxxx
http://dagertech.net/gershman/
"It's all about the path!" --d. gershman
_______________________________________________
XFree86 mailing list
XFree86@xxxxxxxxxxx
http://XFree86.Org/mailman/listinfo/xfree86

[Index of Archives]     [X Forum]     [Xorg]     [XFree86 Newbie]     [IETF Announce]     [Security]     [Font Config]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux Kernel]

  Powered by Linux