WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] Re: [Xen-changelog] Break the building/save/restore code

To: Anthony Liguori <aliguori@xxxxxxxxxx>
Subject: Re: [Xen-devel] Re: [Xen-changelog] Break the building/save/restore code out into a separate library libxenguest.
From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date: Thu, 25 Aug 2005 09:43:43 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, Christian Limpach <Christian.Limpach@xxxxxxxxxxxx>
Delivery-date: Thu, 25 Aug 2005 08:37:16 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <430D28E3.6090306@xxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <E1E85yn-0000xU-9H@xxxxxxxxxxxxxxxxxxxxx> <430D28E3.6090306@xxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx

On 25 Aug 2005, at 03:11, Anthony Liguori wrote:

I considered linking libxenbuild against libxenctrl this way however I've found that even if you have -L., often you'll get linked to a library in /usr/lib instead. If you're running in the build tree, this can result in very unpredictable results.

Is there a better way to do this? It seems better to force an app to include both libraries. I can submit a xen-config script that takes a --libs option to simplify this.

Even if the app links against both libraries don't you have the same basic problem. i.e., the library found at link time may not be the same one as found at run time?

I don't see any automatic way of getting round this, and I really hate those foo-config scripts.

The version suffixes on shared libraries are *supposed* to avoid this issue (but don't work while APIs are changing, of course). While things are in flux, I think you just have to be careful with LD_LIBRARY_PATH if you have libraries in non-standard locations.

 -- Keir


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread] Current Thread [Next in Thread>