A concrete example. A Linux/FreeBSD fpc release was compiled using the pascal headers for libX11.so.6 and using symlink libX11.so >> libX11.so.6.0.8.
This release was installed on a system (with libX11-dev too to make it work). If, some time later, a system-update was done to the brand new version libX11.so.7.0.1, this will update also libX11-dev >> libX11.so >> libX11.so.7.0.1. And using fpc, there will be a error because libX11.so does not point to a libX11.so.6 version. But if the same Linux/FreeBSD fpc release was compiled using symlink libX11.so.6, there, no problem, it will use the still installed symlink libX11.so.6. Or, if libX11.so.6 is no more installed, fpc could say "libX11.so.6 not found" (because fpc knows now what version of libX11 he needs). Other thing. If your way *is* the way to do, why fpc does not use libc6-dev (that will create symlink libc.so) but uses LIBC_SO = 'libc.so.6' instead of LIBC_SO = 'libc.so' ? PS: Do not worry Marcov, it is my last post on fpc forum. Fre;D <http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal>
_______________________________________________ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal
