From: Szabolcs Nagy <nsz@port70.net>
To: musl@lists.openwall.com
Subject: Re: New INSTALL guide, request for feedback
Date: Wed, 21 Sep 2011 23:19:10 +0200 [thread overview]
Message-ID: <20110921211910.GF5865@port70.net> (raw)
In-Reply-To: <20110921200337.GG132@brightrain.aerifal.cx>
* Rich Felker <dalias@aerifal.cx> [2011-09-21 16:03:37 -0400]:
> Feedback would be appreciated!
>
looks reasonable
sometimes i use musl without installation
- checkout git repo
- edit config.mak, run make
- use the git repo include/ and lib/ paths directly with -isystem, -L
and the -nostd*, crt*.o, -dynamic-linker etc hackery
works well for single file compilations (without dynamic linking
to other libraries) i have a makefile setup for this and just
copy it around when i want to do some quick testing
> gcc 3.x and 4.x are known to work. pcc and LLVM/clang may work but
> are untested, and pcc is known to have some bugs.
>
when building libc.so with other compiler than gcc
the -lgcc in the makefile should be (obviously) changed
(this is the only change needed for pcc that i know of)
(when compiling other code with pcc+musl a -Dalloca=__builtin_alloca is
needed as well, glibc does this define so i guess that's why they don't)
> Correctly-written build systems should not need -D_GNU_SOURCE as part
> of $CC, but many programs do not use feature-test macros correctly and
actually musl does not do fine grain feature testing wrt _BSD_SOURCE
so some correct programs expecting bsd stuff may need _GNU_SOURCE too
(eg quad_t or some xsi functions with bsd origin)
next prev parent reply other threads:[~2011-09-21 21:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-21 20:03 Rich Felker
2011-09-21 21:19 ` Szabolcs Nagy [this message]
2011-09-21 21:45 ` Rich Felker
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=20110921211910.GF5865@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).