From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/5551 Path: news.gmane.org!not-for-mail From: Rich Felker Newsgroups: gmane.linux.lib.musl.general Subject: Re: Packaging: Slackware Date: Mon, 21 Jul 2014 10:50:40 -0400 Message-ID: <20140721145040.GQ17402@brightrain.aerifal.cx> References: <53C8E3A2.20206@langurwallah.org> <20140718195359.GY17402@brightrain.aerifal.cx> <53C9DDD4.9050909@langurwallah.org> <20140721024834.GM17402@brightrain.aerifal.cx> <20140721210410.46dfb8b3334acb999e7bd70f@gmail.com> <20140721141525.GO17402@brightrain.aerifal.cx> <53CD26F2.7010306@langurwallah.org> Reply-To: musl@lists.openwall.com NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1405954264 15920 80.91.229.3 (21 Jul 2014 14:51:04 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 21 Jul 2014 14:51:04 +0000 (UTC) Cc: musl@lists.openwall.com To: Weldon Goree Original-X-From: musl-return-5556-gllmg-musl=m.gmane.org@lists.openwall.com Mon Jul 21 16:50:58 2014 Return-path: Envelope-to: gllmg-musl@plane.gmane.org Original-Received: from mother.openwall.net ([195.42.179.200]) by plane.gmane.org with smtp (Exim 4.69) (envelope-from ) id 1X9EvX-0004Ci-Ud for gllmg-musl@plane.gmane.org; Mon, 21 Jul 2014 16:50:56 +0200 Original-Received: (qmail 14247 invoked by uid 550); 21 Jul 2014 14:50:55 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: Original-Received: (qmail 14235 invoked from network); 21 Jul 2014 14:50:54 -0000 Content-Disposition: inline In-Reply-To: <53CD26F2.7010306@langurwallah.org> User-Agent: Mutt/1.5.21 (2010-09-15) Original-Sender: Rich Felker Xref: news.gmane.org gmane.linux.lib.musl.general:5551 Archived-At: On Mon, Jul 21, 2014 at 08:12:58PM +0530, Weldon Goree wrote: > On 07/21/2014 07:45 PM, Rich Felker wrote: > > > > Yes. I'm still not clear though on whether the intent is to provide an > > environment for musl-[dynamic-]linked programs running on Slackware, > > or more for a development environment using the musl-gcc wrapper. This > > might affect the stability requirements. Of course if it's just a > > development environment using the wrapper, there may not be a lot of > > point in packaging that since you already need a compiler to use it, > > The intent is to provide a build script that builds a musl environment > that one could then use to build other build scripts in the repository > (James B's description was good). I'm trying to get some anecdata on > what the people who mentioned being interested in a musl build script > want (cross toolchain vs. gcc wrapper with some environment setup vs. > just the library itself). > > The point of making a build script in the trivial case is that it > integrates it (in a predictable way) with slackware's package > management/file finding system ("where did I put the cross-x86 version's > files again?", etc.). This sounds good. Given the prevalence of C++ these days (which I'm rather unhappy about), musl-gcc has limited usefulness; for example it's hard to even compile a cross-compiler with it, since gcc 4.8+ are written in C++. So I would lean towards providing a native musl-based compiler using the patches from musl-cross (these fix some header issues, default dynamic linker path, libstdc++ build, etc. for working with musl). One remaining open item on the wiki is making musl-gcc work with C++ (i.e. sufficient compatibility to use the host libstdc++). I think the problem here is either that gcc adapts its C++ headers to the host libc, or just that it's using precompiled headers which pulled in part of the libc headers. If someone could debug this and find a workaround, we might be able to revitalize musl-gcc as a serious development option (and it would make bootstrapping a lot easier). Rich