mailing list of musl libc
 help / color / mirror / code / Atom feed
From: "Bortis Kevin" <Kevin.Bortis@ruf.ch>
To: <musl@lists.openwall.com>
Subject: AW: Third draft of musl documentation/manual
Date: Mon, 9 Sep 2013 14:09:46 +0200	[thread overview]
Message-ID: <A03AEC930CBB4D46B9E527D599CFF4D304D47B9F@srvm-mail01-shl.ruf.group> (raw)
In-Reply-To: <20130906042043.GF20515@brightrain.aerifal.cx>

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.

====================================
* `../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.
====================================

  Kevin

> -----Ursprüngliche 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
> 
> 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.
> 
> Rich


  parent reply	other threads:[~2013-09-09 12:09 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-01  4:41 Initial " Rich Felker
2013-09-01  9:43 ` Luca Barbato
2013-09-01 16:57   ` Rich Felker
2013-09-02  0:08     ` Luca Barbato
2013-09-02  7:12       ` Ivan Kanakarakis
2013-09-01 13:45 ` Vasily Kulikov
2013-09-01 16:54   ` Rich Felker
2013-09-02  7:11 ` Christian Wiese
2013-09-06  1:12 ` Second " Rich Felker
2013-09-06  2:41   ` Szabolcs Nagy
2013-09-06  2:57     ` Rich Felker
2013-09-06  4:20 ` Third " Rich Felker
2013-09-06 15:14   ` Szabolcs Nagy
2013-09-06 15:47     ` Rich Felker
2013-09-07 14:50       ` Szabolcs Nagy
2013-09-08 19:22   ` Ivan Kanakarakis
2013-09-09 11:42   ` AW: " Bortis Kevin
2013-09-09 12:09   ` Bortis Kevin [this message]
2013-09-09 15:49     ` 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=A03AEC930CBB4D46B9E527D599CFF4D304D47B9F@srvm-mail01-shl.ruf.group \
    --to=kevin.bortis@ruf.ch \
    --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).