From: Rich Felker <dalias@aerifal.cx>
To: musl@lists.openwall.com
Subject: Re: Summary of 1.0 marketing plan/scheme/nefarious plot from IRC.
Date: Tue, 4 Dec 2012 18:22:45 -0500 [thread overview]
Message-ID: <20121204232245.GK20323@brightrain.aerifal.cx> (raw)
In-Reply-To: <20121204150122.04c11f37.idunham@lavabit.com>
On Tue, Dec 04, 2012 at 03:01:22PM -0800, Isaac Dunham wrote:
> > > - c99 compiler with support for gcc-style assembly language.
>
> Also needs weak symbols.
Yes, thanks for pointing this out.
> In real life this works out to "gcc, clang, or pcc"; there are
> unidentified issues with Open64, icc might or might not work, and
> same for Path64 and Sun Studio for Linux.
I suspect firm is very close to working, and tinycc mob branch might
also be close to working. icc is almost surely working unless there's
some trivial issue; it supports everything we need. The Open64 (or was
it path?) issues seem to be generating spurious relocations in the
shared library; it should be working fine for static linking.
> > > It would be nice if there was some kind of "musl manual". If you
> > > want to write a program against the musl libc, what does it provide?
> > > (HTML is fine, man page format is kinda archaic these days. This is
> > > mostly posix, but not entirely.)
>
> For some folks, but not all.
> (I prefer local documentation that can be viewed without a web-browser...)
I think markdown, or something roughly equivalent, would be preferred.
HTML and other formats could be generated from it if needed.
> I still think that documenting what functions we support should be
> mainly done in the linux-manpages project, which has fairly good
> coverage and notes libc differences.
What do you mean by this? You want linux-manpages to cover documenting
what musl supports?
> > In addition to this, certain functions in the standards have
> > implementation-defined behaviors, which means an implementation is
> > required to document what behavior it provides. One thing we should
> > definitely document is iconv and locale behavior. Compiling a complete
> Speaking of which, will musl support the "ASCII" and "" aliases for the C locale, or is that just bloat? (iirc, these were the issues with R that made libiconv necessary)
> > list of the implementation-defined behavior musl needs to document
> > would be a good project someone could help out with between now and
> > 1.0.
> <snip>
> > > Dynamic vs static linking, "what is a dynamic linker and wazzit
> > > _do_". Something on the whole "how to tell if your binary is built
> > > against musl or some other libc, how to tell if it's statically or
> > > dynamically linked" (fun with ldd and readelf -a), long ago I wrote
> > > an intro to cross compiling if that's worth linking to... Stuff.
> >
> > Yes, the "how to tell what libc a binary is linked against?" is
> > actually a really good FAQ topic (a question that really arises
> > frequently).
>
> I use "strings $BINARY | grep ld.*so"; this lets me see the libc
> required to run it (or if it's static) as well as arch.
Well for static binaries, there's a lot more work. Also, incorrectly
built (broken toolchain) dynamic-linked musl binaries could show
/lib/ld-linux.so.2 as the program interpreter and "mostly" work
(breaking in subtle ways) as long as the glibc dynamic linker is
present on the system, so a good FAQ answer would at least cover this
possibility and how to check for it.
Rich
next prev parent reply other threads:[~2012-12-04 23:22 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-30 2:21 idunham
2012-12-01 2:04 ` Rob Landley
2012-12-01 4:06 ` Rich Felker
2012-12-01 8:18 ` Isaac Dunham
2012-12-04 20:48 ` Rob Landley
2012-12-04 21:45 ` Rich Felker
2012-12-04 23:01 ` Isaac Dunham
2012-12-04 23:22 ` Rich Felker [this message]
2012-12-05 0:58 ` Rob Landley
-- strict thread matches above, loose matches on Subject: below --
2012-11-29 20:50 Rob Landley
2012-11-29 21:15 ` Justin Cormack
2012-11-29 21:51 ` Luca Barbato
2012-11-30 1:30 ` Rich Felker
2012-12-01 0:04 ` Rob Landley
2012-11-30 9:21 ` Rob Landley
2012-11-30 11:08 ` Szabolcs Nagy
2012-12-01 2:00 ` Rob Landley
2012-11-30 1:27 ` Rich Felker
2012-11-30 8:11 ` Truls Becken
2012-11-30 14:29 ` Luca Barbato
2012-11-30 19:05 ` Rich Felker
2012-11-30 20:16 ` nwmcsween
2012-11-30 20:20 ` Rich Felker
2012-11-30 20:32 ` nwmcsween
2012-11-30 20:25 ` Szabolcs Nagy
2012-11-30 20:26 ` Rich Felker
2012-11-30 21:14 ` Luca Barbato
2012-11-30 21:26 ` Rich Felker
2012-12-01 0:04 ` Rob Landley
2012-11-30 4:38 ` Jens Staal
2012-11-30 7:08 ` Daniel Bainton
2012-11-30 13:26 ` Hiltjo Posthuma
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=20121204232245.GK20323@brightrain.aerifal.cx \
--to=dalias@aerifal.cx \
--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).