#918 Linking problems when working with installed stable und local unstable dune
Metadata
| Property | Value |
|---|---|
| Reported by | Christian Engwer (christi@conan.iwr.uni-heidelberg.de) |
| Reported at | May 20, 2011 10:28 |
| Type | Bug Report |
| Version | Git (pre2.4) [autotools] |
| Operating System | Unspecified / All |
| Last edited by | Christian Engwer (christi@conan.iwr.uni-heidelberg.de) |
| Last edited at | Jul 9, 2012 20:26 |
| Closed by | Christian Engwer (christi@conan.iwr.uni-heidelberg.de) |
| Closed at | Jul 9, 2012 20:26 |
| Closed in version | Unknown |
| Resolution | Fixed |
| Comment |
Description
I had the stable dune-common debian package installed, but most of the time I am working with a local in-place dune tree.
The installed dune-common provides shared libs, whereas the local dune is using static libs to ease the debugging process.
The problem is that libtool, or the linker, or whoever, prefers globally installed shared library.
I see two solutions to the problem: a) add some kind of versioning information to make the linker choose the correct lib b) use absolute paths to the libs, when working with locally built dune modules
Both solutions have their downsides and I'm, not sure what is the best solution. In any case we should start using correct so versioning.