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/
Home Products Support Community News


[Xen-devel] [PATCH 0 of 4] tools: build system fix indirect library usag

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] [PATCH 0 of 4] tools: build system fix indirect library usage and --as-needed
From: Ian Campbell <ian.campbell@xxxxxxxxxx>
Date: Tue, 15 Mar 2011 16:16:03 +0000
Cc: Ian Campbell <ian.campbell@xxxxxxxxxx>
Delivery-date: Tue, 15 Mar 2011 09:17:01 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
This series arranges for all libraries and binaries to only link
against those shared libraries which they use directly, relying on the
dynamic linker to do the right thing for indirect dependencies.

In order to do this I've pushed the tools/blktap2 UUID abstraction
down into libvhd and out of line to encapsulate all knowledge
regarding this abstraction into libvhd rather than expecting the users
of the library to do the right thing.

Having done this supporting --as-needed becomes a pretty trivial case
of ensuring links lines have the libraries in the correct order.

Tested by:
        * running xl, start/stop a guest
        * running xend, start/stop a guest
        * manually importing each python extension and calling
          whatever initialisation function I could find.

Xen-devel mailing list