Hi Roland,
On Fri, 2004-10-08 at 18:22 +0200, Roland Kuhn wrote:
> Hi!
>
> As it frequently happens to me that I forget to recompile some of my
> libraries when changing the ROOT version, I thought about ways to find
> this kind of error easier (usually it's some obscure segmentation
> violation that takes some minutes to register as a case of "simply
> recompile"). Would it be possible to reference some symbol in the ROOT
> libraries used, which is unique to each version? That way the dynamic
> linker could already find the incompatibility and the user would
> immediately know what's going on. If a new version of a library is
> backwards compatible, it could also provide the old version of the
> symbol, like it is done for the GLIBC.
If you configure ROOT with the option `--enable-soversion' then the
library's soname will contain the version number of ROOT, and so if you
execute a program linked to version of ROOT not present on the system,
the rumtime linker will complain immediately.
Yours,
--
___ | Christian Holm Christensen
|_| | -------------------------------------------------------------
| | Address: Sankt Hansgade 23, 1. th. Phone: (+45) 35 35 96 91
_| DK-2200 Copenhagen N Cell: (+45) 24 61 85 91
_| Denmark Office: (+45) 353 25 404
____| Email: cholm@nbi.dk Web: www.nbi.dk/~cholm
| |
This archive was generated by hypermail 2b29 : Sun Jan 02 2005 - 05:50:09 MET