From mboxrd@z Thu Jan 1 00:00:00 1970 From: Sean Dague Subject: why is blktap statically linking it's drivers? Date: Fri, 4 Aug 2006 14:19:22 -0400 Message-ID: <20060804181922.GA28530@dargo.dague.pvt> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0458494736==" Return-path: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Mime-version: 1.0 Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org --===============0458494736== Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="XsQoSWH+UP9D9v3l" Content-Disposition: inline --XsQoSWH+UP9D9v3l Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable 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 --=20 Sean Dague IBM Linux Technology Center email: japh@us.ibm.com Open Hypervisor Team alt: sldague@us.ibm.com --XsQoSWH+UP9D9v3l Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (GNU/Linux) iD8DBQFE04+qSamXem9TdyYRAq85AJ9APrQRH5rDlJIeLLzmsRx1g5WuHACfSdkX xhTU6+h6CnF4p67nGu+ZJtg= =13sB -----END PGP SIGNATURE----- --XsQoSWH+UP9D9v3l-- --===============0458494736== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel --===============0458494736==--