On 2/18/11 3:11 AM, Adam Tkac wrote:
> Building X.Org 7.5 on older systems, like RHEL 4/5 will probably fail
> because upstream doesn't care about backward compatibility much.
> 
> In my opinion we can build Xvnc only on fairly new systems, like
> RHEL-6 (not sure about RHEL-5). Resulting static Xvnc will run on
> both RHEL-5 and RHEL-4. Is it acceptable for you? Otherwise we need
> to dive into X.Org and all it's dependencies and restore backward
> compatibility, which might be non-trivial task.


I don't know that that's necessarily true.  It's been my experience that
GLIBC dependencies usually prevent something compiled on a later version
from running on an earlier one.

For now, I'm stuck supporting RHEL 4 and 5, which means I'm stuck
supporting Xorg 7.4.  I'm OK with that for now.  If it gets to the point
where it is difficult for you and others to develop around, then we can
consider an alternative.

We should be able to take the binaries directly out of my pre-release
system and put them on SourceForge.  That was my intent, rather than you
guys having to spin static binaries for every release.

The pre-release build system guarantees a reproducible build from
pristine source, and it does such things as checking 'make dist' to
ensure that all files are included and generating a pristine source tarball.


------------------------------------------------------------------------------
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
_______________________________________________
Tigervnc-devel mailing list
Tigervnc-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/tigervnc-devel

Reply via email to