xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Ian Campbell <ian.campbell@citrix.com>
To: xen-devel@lists.xensource.com
Cc: Ian Campbell <ian.campbell@citrix.com>
Subject: [PATCH 0 of 4] tools: build system fix indirect library usage and --as-needed
Date: Tue, 15 Mar 2011 16:16:03 +0000	[thread overview]
Message-ID: <patchbomb.1300205763@localhost.localdomain> (raw)

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.

             reply	other threads:[~2011-03-15 16:16 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-15 16:16 Ian Campbell [this message]
2011-03-15 16:16 ` [PATCH 1 of 4] tools/blktap2: push uuid wrapper functions down into libvhd Ian Campbell
2011-03-15 16:16 ` [PATCH 2 of 4] tools/blktap2/libvhd: move uuid wrapper functions out of line Ian Campbell
2011-03-15 16:42   ` Daniel Stodden
2011-03-15 16:16 ` [PATCH 3 of 4] tools: link each shared library or binary only against the libraries it uses Ian Campbell
2011-03-15 16:16 ` [PATCH 4 of 4] tools: support building with --as-needed Ian Campbell
2011-03-15 16:18 ` [PATCH 0 of 4] tools: build system fix indirect library usage and --as-needed Ian Campbell
2011-03-17 19:17   ` Ian Jackson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=patchbomb.1300205763@localhost.localdomain \
    --to=ian.campbell@citrix.com \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).