Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Mon, 9 Sep 2013 14:09:46 +0200
From: "Bortis Kevin" <>
To: <>
Subject: AW: Third draft of musl documentation/manual

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.


> -----Urspr√ľngliche Nachricht-----
> Von: Rich Felker []
> Gesendet: Freitag, 6. September 2013 06:21
> An:
> 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

Powered by blists - more mailing lists

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.