mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Laurent Bercot <ska-dietlibc@skarnet.org>
To: musl@lists.openwall.com
Subject: Re: perl native musl, ldd
Date: Thu, 02 Apr 2015 22:48:17 +0200	[thread overview]
Message-ID: <551DAB11.50304@skarnet.org> (raw)
In-Reply-To: <551DA936.2070302@safe.ca>

On 02/04/2015 22:40, Jean-Marc Pigeon wrote:
> 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).

  Yeah, there's no way this is gonna work. Dependencies are not
only about dynamic libraries, they could be about executable files,
data files, or something else entirely. ldd would only give you a
very partial idea of a package's dependencies.


> If you have a better way (more standard) to propose not using
> ldd that will be a good thing. idea?

  I'm afraid there's no easy way - you cannot automate dependency
tracking. If you're going to package software, you will have to
manually list all the dependencies for every single one of your
packages.

-- 
  Laurent



  reply	other threads:[~2015-04-02 20:48 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 [this message]
2015-04-02 21:08         ` Nathan McSween
2015-04-02 21:09         ` u-wsnj
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=551DAB11.50304@skarnet.org \
    --to=ska-dietlibc@skarnet.org \
    --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).