From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([69.77.167.62] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1L1904-0005G1-R7 for garchives@archives.gentoo.org; Sat, 15 Nov 2008 00:26:57 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id BC9CFE01B5; Sat, 15 Nov 2008 00:26:55 +0000 (UTC) Received: from smtp-out.neti.ee (smtp-out.neti.ee [194.126.126.37]) by pigeon.gentoo.org (Postfix) with ESMTP id 88AA6E01B5 for ; Sat, 15 Nov 2008 00:26:55 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at estpak.ee Received: from Relayhost3.neti.ee (relayhost3.estpak.ee [88.196.174.169]) by MXR-8.estpak.ee (Postfix) with ESMTP id 501DB157E93 for ; Sat, 15 Nov 2008 02:26:51 +0200 (EET) X-SMTP-Auth-NETI-Businesmail: no Subject: Re: [gentoo-dev] Re: Please review: function epunt_la_files for eutils.eclass From: Mart Raudsepp To: gentoo-dev@lists.gentoo.org In-Reply-To: <200811150005.54423.loki_val@gentoo.org> References: <200811091704.10291.loki_val@gentoo.org> <200811121831.49814.loki_val@gentoo.org> <20081113221413.71edadab@halo.dirtyepic.sk.ca> <200811150005.54423.loki_val@gentoo.org> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-WYjBVP97mwzlq7/UQcMA" Date: Sat, 15 Nov 2008 02:26:52 +0200 Message-Id: <1226708812.12338.3.camel@localhost> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org Mime-Version: 1.0 X-Mailer: Evolution 2.22.0 X-Archives-Salt: 71f4dcc6-4d27-4e62-91d4-eaf6343231bc X-Archives-Hash: b869045c96693f21adf9bd0b5e75cde9 --=-WYjBVP97mwzlq7/UQcMA Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Sat, 2008-11-15 at 00:05 +0100, Peter Alfredsen wrote: > Anyway, we really need to start punting .la files one way or the other.=20 > For desktop users of our distro, they do a lot more harm than good. For=20 > embedded, perhaps static linking serves some purpose, but really, if=20 > you can't afford dynamic linking, what are you going to run on your=20 > board? Just to quickly explain the purpose of static linking on embedded - it has nothing to do with avoiding dynamic linking (run-time?) cost, it has everything to do with size. If you have a library that only one or few applications use, you can end up with smaller size through static linking it, rather than using a shared library of it. This is because during static linking all functions that are not used can be discarded from the final binary, while with shared libraries all the code has to remain, because it isn't know what will be using that shared library, so the toolchain can not safely discard anything, even if you just have one application using some big library, but only using a small subset of its functionality. --=20 Mart Raudsepp Gentoo Developer Mail: leio@gentoo.org Weblog: http://planet.gentoo.org/developers/leio --=-WYjBVP97mwzlq7/UQcMA Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.8 (GNU/Linux) iEYEABECAAYFAkkeF0wACgkQkeYb6olFHJePmQCg9HIeuy9MX8xGFacGvnGG9y3e d2oAn3PseRNmQOcPgTEyMqH3B/3CWDyP =ennd -----END PGP SIGNATURE----- --=-WYjBVP97mwzlq7/UQcMA--