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

[Xen-devel] why is blktap statically linking it's drivers?

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] why is blktap statically linking it's drivers?
From: Sean Dague <japh@xxxxxxxxxx>
Date: Fri, 4 Aug 2006 14:19:22 -0400
Delivery-date: Fri, 04 Aug 2006 11:20:12 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
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>
Mail-followup-to: xen-devel@xxxxxxxxxxxxxxxxxxx
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.9i
It took me a bit to realize that the issue I was having with blktap
compiling in xen-unstable is that it is statically linking libcrypto and
libc into all of the executables in: xen-unstable/tools/blktap/drivers

Is there a reason for this?  It means that every one of those executables
ends up at > 1 MB, which seems quite excessive.  It also means that you need
static-devel packages on some distros, which tend to not be installed by
default.

        -Sean

-- 
Sean Dague
IBM Linux Technology Center                     email: japh@xxxxxxxxxx
Open Hypervisor Team                           alt: sldague@xxxxxxxxxx

Attachment: pgpnewY957wvA.pgp
Description: PGP signature

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
<Prev in Thread] Current Thread [Next in Thread>