From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/9768 Path: news.gmane.org!not-for-mail From: Shiz Newsgroups: gmane.linux.lib.musl.general Subject: Re: using musl with a c++ library. Date: Tue, 29 Mar 2016 12:26:21 +0200 Message-ID: <95A8D906-77D6-429E-93F5-E859974D593B@shiz.me> References: Reply-To: musl@lists.openwall.com NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 (Mac OS X Mail 9.2 \(3112\)) Content-Type: multipart/signed; boundary="Apple-Mail=_AD3370CA-9AFC-4073-8E29-EC396E2FED55"; protocol="application/pgp-signature"; micalg=pgp-sha256 X-Trace: ger.gmane.org 1459247224 23975 80.91.229.3 (29 Mar 2016 10:27:04 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 29 Mar 2016 10:27:04 +0000 (UTC) To: musl@lists.openwall.com Original-X-From: musl-return-9781-gllmg-musl=m.gmane.org@lists.openwall.com Tue Mar 29 12:26:57 2016 Return-path: Envelope-to: gllmg-musl@m.gmane.org Original-Received: from mother.openwall.net ([195.42.179.200]) by plane.gmane.org with smtp (Exim 4.69) (envelope-from ) id 1akqrR-0005SP-Dg for gllmg-musl@m.gmane.org; Tue, 29 Mar 2016 12:26:57 +0200 Original-Received: (qmail 23786 invoked by uid 550); 29 Mar 2016 10:26:53 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-ID: Original-Received: (qmail 23768 invoked from network); 29 Mar 2016 10:26:52 -0000 X-Pgp-Agent: GPGMail 2.6b2 In-Reply-To: X-Mailer: Apple Mail (2.3112) Xref: news.gmane.org gmane.linux.lib.musl.general:9768 Archived-At: --Apple-Mail=_AD3370CA-9AFC-4073-8E29-EC396E2FED55 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii > On 29 Mar 2016, at 11:02, Rashad Kanavath = wrote: >=20 > should I rebuild just libstdc++ using musl-gcc wrapper script and use = that libstdc++ ?. I believe the current recommendation is to not use musl-gcc at all for = C++ stuff, but just build a proper musl-native toolchain. Recipes for such can be = found at [1] and [2]. musl-gcc is just a wrapper for convenience, but definitely not a = replacement for a proper native toolchain. > Also Is it possible to distribute musl with an application package. = Currently I have a self-extracting archive which uses an older version = of glibc. so it will run on any platform that has a glibc version higher = that it was build (2.4). If I use musl and is able to distribute it = along with my application package, Then I don't have to rely on anything = other than linux kernel version on the target platform. Yes, as musl is licensed under the MIT license, this is allowed. You could even statically link against it to be able to ship just a = single binary file. - Shiz [1]: https://bitbucket.org/GregorR/musl-cross [2]: https://github.com/richfelker/musl-cross-make --Apple-Mail=_AD3370CA-9AFC-4073-8E29-EC396E2FED55 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- iQIcBAEBCAAGBQJW+lhfAAoJEI8YjKeZk+kH/JQP/1P88OsG8rR8cuB3NbK/rPa3 f76fB7l6KPj6POa5bpFxaTuXekIALMXDkmoV4TYkY/s3WqAGFwMPCbpBiZmcOCo2 CjMRJ0gRVGLZvuy261QqLYSXsc65CVml5hphM6XR6sAiSJuuJC/5fpOEVxeMfKOG Xpqq9/J4VoLFIul9DUhB7DeLsJWXkS+Qbr0Y5DR+CiChKEtt0Ofe8JbCswqw0AU/ 05uCoNq73K0n2RTA34SFIdmCh1R8uQBFch4160+RjqmizLKwudhAXyovUO0BHJmq JG6Obzd115eNAZQxcZzY90dAFE2xMVsw80Xc0hC9vrRLAm6HU+GqC8e72mx8VKwP 4ivylDuVqtiCdwiOWhu+WMwd7j3mfFvJM7tqrhM/0JiyKkduFGQu+37wFwUxAfYu C4bvZklJZZsyoLJB7l8U2I9fnXjFVTr86bgwivG1eb+FaVQ1ljwIWvsii86ZONwo THO4z+5kPOhZILp4zq1RlxpMZUJipu7ckpwHsYtqtZuA2Jt+J+uc0lNIyvW7HEEr +xdrifiPozBPgAMWP+f9x2ypgSjairfx+KSsbKSvxFLF9dXhThKASoiHi0egRAfA 6PqGav4E72SjPnFZRCo2Zz/gzWf4btfDMFM+D6bnFLwAq3vWrrlzQiOoUb+X6dFy CGja2mv00cAgu+AtOJ00 =p9U0 -----END PGP SIGNATURE----- --Apple-Mail=_AD3370CA-9AFC-4073-8E29-EC396E2FED55--