From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/865 Path: news.gmane.org!not-for-mail From: Rich Felker Newsgroups: gmane.linux.lib.musl.general Subject: Re: Hi and a few questions Date: Sun, 20 May 2012 17:25:21 -0400 Message-ID: <20120520212521.GC163@brightrain.aerifal.cx> References: <1753849.ANqesc5nEP@main.pennware.com> <20120520172116.GA163@brightrain.aerifal.cx> <20120520134936.3b6812fe@newbook> 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: dough.gmane.org 1337549445 14186 80.91.229.3 (20 May 2012 21:30:45 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Sun, 20 May 2012 21:30:45 +0000 (UTC) To: musl@lists.openwall.com Original-X-From: musl-return-866-gllmg-musl=m.gmane.org@lists.openwall.com Sun May 20 23:30:44 2012 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 1SWDi5-00030P-9n for gllmg-musl@plane.gmane.org; Sun, 20 May 2012 23:30:41 +0200 Original-Received: (qmail 14016 invoked by uid 550); 20 May 2012 21:30:40 -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 14008 invoked from network); 20 May 2012 21:30:40 -0000 Content-Disposition: inline In-Reply-To: <20120520134936.3b6812fe@newbook> User-Agent: Mutt/1.5.21 (2010-09-15) Xref: news.gmane.org gmane.linux.lib.musl.general:865 Archived-At: On Sun, May 20, 2012 at 01:49:36PM -0700, Isaac Dunham wrote: > There was someone who was asking about portability previously; he has a > project that will use arm and mips cpus (this is the project that needs > libuv, hence the discussion on IRC) and-if musl works with libuv-he > thinks he could convince his boss to fund a port, if one isn't ready > ahead of time. Good to know! > Microblaze is one of the oddball CPUs that you can configure without an > MMU. Would this project target MMU configurations only? Well POSIX requires an MMU (or a completely virtualized system that has one), and as far as I know Linux does too (although there's UCLinux or whatever too). I suspect the situation would be the same as how we handle 2.4 kernels: "If some functionality works, great, but let's not do all kinds of crazy things to make stuff work 'better' when it's impossible to work 100% right anyway due to platform limitations." > For what it's worth, a shadow tree (see lndir(1)) would probably do all > that's really needed, if you > 1 Get musl source code > 2 lndir $MUSL_SOURCE ${MUSL_SOURCE}-${ARCH} > 3 Configure and build in ${MUSL_SOURCE}-${ARCH} Yes, this should work very well. > You might have issues with shadowing after you have built musl (ie, do > 3 in-tree, 2, repeat 3 in shadow tree), I wouldn't know for sure. The only major problem I can think of is include/bits getting shadowed, but "make clean" removes it anyway. So even this might work. Rich