From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/857 Path: news.gmane.org!not-for-mail From: Szabolcs Nagy Newsgroups: gmane.linux.lib.musl.general Subject: Re: Hi and a few questions Date: Sun, 20 May 2012 19:53:16 +0200 Message-ID: <20120520175316.GC17860@port70.net> References: <1753849.ANqesc5nEP@main.pennware.com> 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 1337536418 22309 80.91.229.3 (20 May 2012 17:53:38 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Sun, 20 May 2012 17:53:38 +0000 (UTC) To: musl@lists.openwall.com Original-X-From: musl-return-858-gllmg-musl=m.gmane.org@lists.openwall.com Sun May 20 19:53:37 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 1SWAJt-0000Jn-1d for gllmg-musl@plane.gmane.org; Sun, 20 May 2012 19:53:29 +0200 Original-Received: (qmail 1477 invoked by uid 550); 20 May 2012 17:53:28 -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 1469 invoked from network); 20 May 2012 17:53:28 -0000 Content-Disposition: inline In-Reply-To: <1753849.ANqesc5nEP@main.pennware.com> User-Agent: Mutt/1.5.21 (2010-09-15) Xref: news.gmane.org gmane.linux.lib.musl.general:857 Archived-At: * Richard Pennington [2012-05-20 12:03:20 -0500]: > I want to target several processors, including i386, x86_64, arm, mips, > microblaze, ppc, and ppc64 so it looks like musl support will have to be added > for the currently unsupported processors. yes > I've done some preliminary testing by compiling the Open POSIX Test Suite > (http://posixtest.sourceforge.net) three ways: > 1. with gcc/glibc, x86_64 > 2. with clang/LLVM/glibc, x86_64 > 3. with clang/LLVM/musl, x86_64 nice, unfortunately it does not seem to be maintained and it's not updated to posix 2008: "... error: implicit declaration of function 'usleep'" > The results have been good enough that I'm pretty sure I want to switch: > > [~/ellcc/posixtestsuite] main% grep PASS logfile.musl | wc > 5074 15286 275399 > [~/ellcc/posixtestsuite] main% grep PASS logfile.ecc | wc > 5381 16143 294510 > [~/ellcc/posixtestsuite] main% grep PASS logfile.gcc | wc > 5380 16140 294458 > many tests are broken and thus the build fails eg "functional/threads/schedule/1-1.c:22:1: error: "_XOPEN_SOURCE" redefined" they shouldn't define that in the source file (without undefing it first) "conformance/interfaces/pthread_key_create/1-2.c:44: error: control reaches end of non-void function" there are a couple of similar bad tests "conformance/interfaces/aio_read/9-1.c: In function 'main': conformance/interfaces/aio_read/9-1.c:59: error: implicit declaration of function 'open'" they use open without including fcntl.h etc > Now for my questions: > 1. Can musl be built out of the source tree? I'd like to be able to build > for different processors in different directories. what do you mean by out of the source tree? you can set an install prefix for make install if you want to have the .o files for each target in a separate build directory then you can have several git clones or hack the Makefile > 2. Are the include/bits files the only include files that differ between > processors? no, see eg src/thread/$ARCH or src/math/$ARCH > 3. Are people actively working on other musl ports? I'd wouldn't want to > duplicate their efforts. i don't think so mips port was mentioned on irc at some point but i don't think anyone took it up