Qt binary package on different distributions - problem

[nooky59]

Hi,

As jacek mentioned, LSB may be able to help but the problem is that OpenSSL is not part of the LSB spec. The most common solutions are either:
- Compile statically
or
- You can ship the libraries that your app depends on, use a wrapper script and LD_LIBRARY_PATH to point to that directory

You may also want to compile on an older system such as Red Hat 9 or Debian 3.1 that uses an older version of glibc and RedHat

Best regards

Daniel

I will wake up this thread as I am currently in the step of X11 deployment.

Why do you suggest explicitally Red Hat 9 or Debian 3.1. Why not other brands or older one for Red Hat / Debian.

I suppose, that for Debian it was because the Sarge release 3.1 was still maintained when you post about it but now, support has finished for it.

For Red Hat 9, there is too no support and I don't think it was the case when you post about it.

But, as a good advice for other peoples, if you want to builf on a "Red Hat 9" like release, the best way is to use CentOS 3.X. This is the Red Hat Enterprise 3, based on Red Hat 9 and this one include security updates until 10/31/2010.

The only thing you have to do to properly compile Qt with the default settings is to use a fresher openssl library than the one bundled with CentOS 3, else compilation of Qt will failed.

You will have to use -I and -L flags for ./configure in order to give the correct location of libs and includes files from the fresher openssl, for example

./configure -I /usr/local/ssl/include -L /usr/local/ssl/lib


So I think a Red Hat Enterprise (or clone) is the best build platform for wide compatibility and its seven years support lifetime permit to use the older supported release to build Qt applications with an old glibc.

I've tried to build Qt on the older CentOS 2, still maintained too, but the Qt compilation has failed more seriously ;o)