Hey, thanks for the reply. I understand what you're saying, so
I'll take this opportunity to ask about Turbo (Tiger-only readers
can hit DELETE now....)

Our biggest issue with TurboVNC is, believe it or not, that it
can't cut and paste. My understanding is that this is because
it's built on a vnc code base that's too old for vncconfig to
work with.

Any chance of getting Turbo built with a newer base of vnc, so
vncconfig will work with it ? Maybe I should focus my efforts
there instead of trying to get Tiger to run on RHELv5....

    Thanks,

       John


DRC wrote:
> John,
>
> Mr. TurboVNC here.  TurboVNC is still actively supported.  I plan to try
> to move TurboVNC customers to TigerVNC in the long term, but not until I
> can build "compatible" packages for TigerVNC that work on platforms like
> RHEL.  There is also still about a 30-40% performance lag with TigerVNC
> vs. TurboVNC that needs to be addressed.  Currently, I am seeking
> financial sponsorship for both efforts.  Otherwise, it will be more of a
> long-term proposition.
>
> To answer your specific questions below, the current TigerVNC RPM's
> piggyback off of the X server that is installed on the system.  Thus,
> you can't build the RPM unless you have a very recent distro of Linux.
> To build on an older version of Linux requires building a monolithic
> version of Xvnc which embeds an older version of the Xorg source.  A
> preliminary attempt at a script to build such a version of Xvnc is in
> the SVN trunk (release/build-compat-linux).  It works, but I'm not
> totally happy with it yet.
>
> John Foley wrote:
>> Tiger users - I hope this isn't too stupid a question, but I need
>> some advice from your experiences....
>>
>> I'd really like to switch our group of users to TigerVNC server
>> from TurboVNC server (for reasons I won't bore you with). I have an
>> older version of Tiger running here now, but it suffers from the
>> "no key repeating" problem, so I need to move to a version that's
>> new enough to incorporate the fix for this.
>>
>> The problem is that these newer versions are all being built on
>> fedora 11 and higher, which uses a GLIBC of 2.7 - but my RHELv5.2
>> machines that I must use have a GLIBC of 2.5, so simply downloading
>> the rpms that "atkac" builds won't work for me  :(
>>
>> I can see and download the source for these newer builds, so I could
>> try to build the TigerVNC server on one of my RHELv5.2 machines -
>> but I'll admit that I'm stumped on exactly how to accomplish
>> this...
>>
>> So, my questions are :
>>
>> 1) anybody out there successfully built a "recent" version of TigerVNC
>>      server on RHELv5.2 ? Willing to share ?  :)
>>
>> 2) the downloaded/extracted source files appear to have an rpm .spec
>>      file in them - so is the build as "simple" as just running rpm
>>      using that .spec file ? Can anyone offer any suggestions and/or
>>      advice on doing the VNCserver build that might help me out ?
>>
>>     Thanks for any thoughts / suggestions --
>>
>>         John
>>
>>
>> ------------------------------------------------------------------------------
>> Download Intel® Parallel Studio Eval
>> Try the new software tools for yourself. Speed compiling, find bugs
>> proactively, and fine-tune applications for parallel performance.
>> See why Intel Parallel Studio got high marks during beta.
>> http://p.sf.net/sfu/intel-sw-dev
>> _______________________________________________
>> Tigervnc-users mailing list
>> Tigervnc-users@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/tigervnc-users


------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Tigervnc-users mailing list
Tigervnc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/tigervnc-users

Reply via email to