From: Szabolcs Nagy <nsz@port70.net>
To: musl@lists.openwall.com
Subject: Re: Hi and a few questions
Date: Sun, 20 May 2012 19:53:16 +0200 [thread overview]
Message-ID: <20120520175316.GC17860@port70.net> (raw)
In-Reply-To: <1753849.ANqesc5nEP@main.pennware.com>
* Richard Pennington <rich@pennware.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
next prev parent reply other threads:[~2012-05-20 17:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-20 17:03 Richard Pennington
2012-05-20 17:21 ` Rich Felker
2012-05-20 19:57 ` Richard Pennington
2012-05-20 20:49 ` Isaac Dunham
2012-05-20 21:25 ` Rich Felker
2012-05-20 17:53 ` Szabolcs Nagy [this message]
2012-05-20 20:01 ` Richard Pennington
2012-05-20 20:44 ` Richard Pennington
2012-05-20 21:20 ` Rich Felker
2012-05-20 20:28 ` Szabolcs Nagy
2012-05-20 20:36 ` Richard Pennington
2012-05-21 1:54 ` Isaac Dunham
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120520175316.GC17860@port70.net \
--to=nsz@port70.net \
--cc=musl@lists.openwall.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).