From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/5026 Path: news.gmane.org!not-for-mail From: Oliver Schneider Newsgroups: gmane.linux.lib.musl.general Subject: Re: for the wiki: a __MUSL__ alternative Date: Fri, 02 May 2014 10:44:28 +0000 Organization: CYREN Iceland Message-ID: <5363770C.3080902@f-prot.com> References: <5361FA9F.2090207@midipix.org> <20140501125117.GU26358@brightrain.aerifal.cx> Reply-To: musl@lists.openwall.com NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1399027492 24607 80.91.229.3 (2 May 2014 10:44:52 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 2 May 2014 10:44:52 +0000 (UTC) To: musl@lists.openwall.com Original-X-From: musl-return-5030-gllmg-musl=m.gmane.org@lists.openwall.com Fri May 02 12:44:46 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 1WgAxR-0002Cq-MQ for gllmg-musl@plane.gmane.org; Fri, 02 May 2014 12:44:45 +0200 Original-Received: (qmail 17790 invoked by uid 550); 2 May 2014 10:44:43 -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 17776 invoked from network); 2 May 2014 10:44:43 -0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.0 In-Reply-To: <20140501125117.GU26358@brightrain.aerifal.cx> X-Antivirus: Scanned by F-PROT Antivirus (http://www.f-prot.com) Xref: news.gmane.org gmane.linux.lib.musl.general:5026 Archived-At: Hey Rich, On 2014-05-01 12:51, Rich Felker wrote: > The whole point of the wiki answer is that doing this is wrong. Adding > a "here's a way to do it anyway" rather defeats the purpose and is > just going to get us more trouble in the long term. In any case, this > only works when dynamic linking is available, and it requires the > ability to run programs for the target which breaks cross compiling > and therefore violates one of the biggest rules for built scripts. you're right and I admire how steadfast you are in your resolve. Initially I desired to have this myself so that I could give attribution within the program depending on whether it was built with musl-libc or another libc. Right now I have simple used a define on the command line to tell whether it's a build with musl-libc or not. Also, I don't think the proposed solution is very elegant. In this case it'd be better to pass parameters using the specs file, no? // Oliver