Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Sun, 20 May 2012 19:53:16 +0200
From: Szabolcs Nagy <nsz@...t70.net>
To: musl@...ts.openwall.com
Subject: Re: Hi and a few questions

* Richard Pennington <rich@...nware.com> [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

Powered by blists - more mailing lists

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.