http://dl.dropbox.com/u/3409323/TigerVNC/epel5/SPECS/tigervnc.spec
http://dl.dropbox.com/u/3409323/TigerVNC/epel5/SRPMS/tigervnc-1.2.0-11.20130330svn5066.el5.src.rpm<http://dl.dropbox.com/u/3409323/TigerVNC/epel5/SRPMS/tigervnc-1.2.0-10.20130330svn5066.el5.src.rpm>
http://dl.dropbox.com/u/3409323/TigerVNC/epel5/RPMS/x86_64/tigervnc-server-module-1.2.0-11.20130330svn5066.el5.x86_64.rpm<http://dl.dropbox.com/u/3409323/TigerVNC/epel5/RPMS/x86_64/tigervnc-server-module-1.2.0-10.20130330svn5066.el5.x86_64.rpm>
http://dl.dropbox.com/u/3409323/TigerVNC/epel5/RPMS/x86_64/tigervnc-server-minimal-1.2.0-11.20130330svn5066.el5.x86_64.rpm<http://dl.dropbox.com/u/3409323/TigerVNC/epel5/RPMS/x86_64/tigervnc-server-minimal-1.2.0-10.20130330svn5066.el5.x86_64.rpm>
http://dl.dropbox.com/u/3409323/TigerVNC/epel5/RPMS/x86_64/tigervnc-server-applet-1.2.0-11.20130330svn5066.el5.x86_64.rpm<http://dl.dropbox.com/u/3409323/TigerVNC/epel5/RPMS/x86_64/tigervnc-server-applet-1.2.0-10.20130330svn5066.el5.x86_64.rpm>
http://dl.dropbox.com/u/3409323/TigerVNC/epel5/RPMS/x86_64/tigervnc-server-1.2.0-11.20130330svn5066.el5.x86_64.rpm<http://dl.dropbox.com/u/3409323/TigerVNC/epel5/RPMS/x86_64/tigervnc-server-1.2.0-10.20130330svn5066.el5.x86_64.rpm>
http://dl.dropbox.com/u/3409323/TigerVNC/epel5/RPMS/x86_64/tigervnc-license-1.2.0-11.20130330svn5066.el5.x86_64.rpm<http://dl.dropbox.com/u/3409323/TigerVNC/epel5/RPMS/x86_64/tigervnc-license-1.2.0-10.20130330svn5066.el5.x86_64.rpm>
http://dl.dropbox.com/u/3409323/TigerVNC/epel5/RPMS/x86_64/tigervnc-1.2.0-11.20130330svn5066.el5.x86_64.rpm<http://dl.dropbox.com/u/3409323/TigerVNC/epel5/RPMS/x86_64/tigervnc-1.2.0-10.20130330svn5066.el5.x86_64.rpm>

Updated with the latest Fltk source & patches.  Also the wrong versions of
the vncservers init script & config file were previously included.



On Sat, Mar 30, 2013 at 12:38 PM, Brian Hinz
<bph...@users.sourceforge.net>wrote:

> On Sat, Mar 30, 2013 at 5:43 AM, D.L.C. Burggraaff <bu...@kabelfoon.nl>wrote:
>
>> I repackage the "cross-compatible" builds for PartedMagic (
>> http://partedmagic.com). And of course I repackage these builds for my
>> own use (Slackware, Xubuntu).
>>
>> Most of the time I could rebuild within a reasonable time-frame all
>> executables from source (PartedMagic prefers -Os instead of -O2) except
>> Xvnc.
>> This week I downloaded trunk and tried to compile. After some initial
>> fights with FLTK I decided to ask about the possibility of a (pre-)release
>> instead.
>>
>> I remember having read about DRC's build script some time ago. Maybe I
>> should have a more involved "go" with it (any hints on where to find it?).
>> Until then the RPM Brian mentioned would be more than welcome.
>>
>
> Until a more suitable location can be found, here are links to an updated
> RPM/SRPM/SPEC:
>
> http://dl.dropbox.com/u/3409323/TigerVNC/epel5/SPECS/tigervnc.spec
>
> http://dl.dropbox.com/u/3409323/TigerVNC/epel5/SRPMS/tigervnc-1.2.0-10.20130330svn5066.el5.src.rpm
>
> http://dl.dropbox.com/u/3409323/TigerVNC/epel5/RPMS/x86_64/tigervnc-server-module-1.2.0-10.20130330svn5066.el5.x86_64.rpm
>
> http://dl.dropbox.com/u/3409323/TigerVNC/epel5/RPMS/x86_64/tigervnc-server-minimal-1.2.0-10.20130330svn5066.el5.x86_64.rpm
>
> http://dl.dropbox.com/u/3409323/TigerVNC/epel5/RPMS/x86_64/tigervnc-server-applet-1.2.0-10.20130330svn5066.el5.x86_64.rpm
>
> http://dl.dropbox.com/u/3409323/TigerVNC/epel5/RPMS/x86_64/tigervnc-server-1.2.0-10.20130330svn5066.el5.x86_64.rpm
>
> http://dl.dropbox.com/u/3409323/TigerVNC/epel5/RPMS/x86_64/tigervnc-license-1.2.0-10.20130330svn5066.el5.x86_64.rpm
>
> http://dl.dropbox.com/u/3409323/TigerVNC/epel5/RPMS/x86_64/tigervnc-1.2.0-10.20130330svn5066.el5.x86_64.rpm
>
> A couple of notes about the build:
>
> (1) Requires cmake > 2.8, which isn't readily available for EL5 but easy
> enough to build.  I used the spec for cmake28 from the epel6 repo to
> install cmake28 on EL5 (with one small change IIRC).
> (2) The spec file needs a little updating.  Pierre has updated a couple of
> the Fltk patches since I last modified this spec file.  I'll update those
> and repost later today or tomorrow.
> (3) The Xvnc binary is mostly static and may "just work".  If not, I think
> that the spec file is pretty straight forward if you wanted to use it as a
> basis for a custom build script.
> (4) The build process was derived from DRC's cross-compatible build
> script, but differs in source versions (which were matched as closely to
> Fedora 12 as possible) and some of the options used to configure Xvnc.
>  I've running this in a production environment for over a year now and it's
> very stable.
>
> Oh, and thanks for your work on partedmagic.  It's a great piece of
> software that has saved my bacon more than once.
>
> -brian
>
>
>
>
>
------------------------------------------------------------------------------
Own the Future-Intel(R) Level Up Game Demo Contest 2013
Rise to greatness in Intel's independent game demo contest. Compete 
for recognition, cash, and the chance to get your game on Steam. 
$5K grand prize plus 10 genre and skill prizes. Submit your demo 
by 6/6/13. http://altfarm.mediaplex.com/ad/ck/12124-176961-30367-2
_______________________________________________
Tigervnc-devel mailing list
Tigervnc-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/tigervnc-devel

Reply via email to