[Dune] [#918] Linking problems when working with installed stable und local unstable dune

[Dune]

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.

A new Flyspray task has been opened.  Details are below. 

User who did this - Christian Engwer (christi) 

Attached to Project - Dune
Summary - Linking problems when working with installed stable und local unstable dune
Task Type - Bug Report
Category - Infrastructure
Status - New
Assigned To - 
Operating System - Unspecified / All
Severity - Low
Priority - Normal
Reported Version - SVN (pre2.2)
Due in Version - Undecided
Due Date - Undecided
Details - 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.


More information can be found at the following URL:
http://www.dune-project.org/flyspray/index.php?do=details&task_id=918

You are receiving this message because you have requested it from the Flyspray bugtracking system.  If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.