From: u-wsnj@aetey.se
To: musl@lists.openwall.com
Subject: Re: perl native musl, ldd
Date: Thu, 2 Apr 2015 23:09:14 +0200 [thread overview]
Message-ID: <20150402210914.GG4456@example.net> (raw)
In-Reply-To: <551DA936.2070302@safe.ca>
On Thu, Apr 02, 2015 at 04:40:22PM -0400, Jean-Marc Pigeon wrote:
> > I would not say reporting the symbols is a bug, rather that the packager
> > is kind of relying on UB. Is there a specification of how a program called
> > "ldd" shall format its output and which data shall be present?
> Packager Relying on ldd UB, sure!.
> Using ldd was the best way I found to list one package all
> dependencies (looking at ELF file type ans searching for
> required external components).
I am using ldd to find the libraries necessary for binaries and had to
adjust my "one-liner" scripts when I moved on from glibc to musl ldd.
I would suggest that it is your scripts which are to be (easily) adjusted,
not the ldd which from my perspective works just fine, for a purpose very
similar to yours.
> If you have a better way (more standard) to propose not using
> ldd that will be a good thing. idea?
There is no such standard because the concept of a "dependency
on a component" exists only in a context of a certain packaging
system. Software in general does not belong to a single such context,
so there is no clear notion of components, different parties do have
different views.
Rune
next prev parent reply other threads:[~2015-04-02 21:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-02 15:53 Jean-Marc Pigeon
2015-04-02 16:18 ` Rich Felker
2015-04-02 18:17 ` Jean-Marc Pigeon
2015-04-02 18:48 ` u-wsnj
2015-04-02 20:40 ` Jean-Marc Pigeon
2015-04-02 20:48 ` Laurent Bercot
2015-04-02 21:08 ` Nathan McSween
2015-04-02 21:09 ` u-wsnj [this message]
2015-04-02 21:26 ` Rich Felker
2015-04-02 21:34 ` Szabolcs Nagy
2015-04-03 0:57 ` Jean-Marc Pigeon
2015-04-03 1:18 ` bug? in musl libc failed to preserve ownership for Jean-Marc Pigeon
2015-04-03 2:15 ` 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=20150402210914.GG4456@example.net \
--to=u-wsnj@aetey.se \
--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).