From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/4028 Path: news.gmane.org!not-for-mail From: "Bortis Kevin" Newsgroups: gmane.linux.lib.musl.general Subject: AW: Third draft of musl documentation/manual Date: Mon, 9 Sep 2013 14:09:46 +0200 Message-ID: References: <20130901044106.GA29630@brightrain.aerifal.cx> <20130906042043.GF20515@brightrain.aerifal.cx> Reply-To: musl@lists.openwall.com NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Trace: ger.gmane.org 1378728601 32097 80.91.229.3 (9 Sep 2013 12:10:01 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 9 Sep 2013 12:10:01 +0000 (UTC) To: Original-X-From: musl-return-4032-gllmg-musl=m.gmane.org@lists.openwall.com Mon Sep 09 14:10:05 2013 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 1VJ0I8-0000Kl-8b for gllmg-musl@plane.gmane.org; Mon, 09 Sep 2013 14:10:04 +0200 Original-Received: (qmail 15888 invoked by uid 550); 9 Sep 2013 12:10:03 -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 15879 invoked from network); 9 Sep 2013 12:10:03 -0000 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message In-Reply-To: <20130906042043.GF20515@brightrain.aerifal.cx> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [musl] Third draft of musl documentation/manual Thread-Index: Ac6quIN2rlLizJpgRGiQL4hLEFvhvgCm+Ovg X-Scanned-By: MIMEDefang 2.69 on 195.141.2.10 Xref: news.gmane.org gmane.linux.lib.musl.general:4028 Archived-At: What happens if /etc/ld-musl-$(ARCH).path is: * present, but not readable? * present, but corrupt? Does it always fallback to the default "/lib:/usr/local/lib:/usr/lib"? The manual text does not describe these cases. =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D * `../etc/ld-musl-$(ARCH).path`, taken relative to the location of the "program interpreter" specified in the program's headers - if present, this will be processed as a text file containing the shared library search path, with components delimited by newlines or colons. If absent, a default path of `"/lib:/usr/local/lib:/usr/lib"` will be used. Not used by static-linked programs. =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Kevin > -----Urspr=FCngliche Nachricht----- > Von: Rich Felker [mailto:dalias@aerifal.cx] > Gesendet: Freitag, 6. September 2013 06:21 > An: musl@lists.openwall.com > Betreff: Re: [musl] Third draft of musl documentation/manual >=20 > Here is the third version of the docs/manual draft, with a lot more = content > filled in, some of it based on previous comments. The biggest task = left is > filling in all the implementation-defined behavior. For plain C = functions, > J.3.12 gives a nice checklist of things to document, but POSIX has a = lot more > things which are specified as implementation-defined for which I don't = have > such a nice checklist. > Ideas on how to build one would be great. >=20 > Rich