DPDK patches and discussions
 help / color / mirror / Atom feed
From: Bruce Richardson <bruce.richardson@intel.com>
To: Robin Jarry <rjarry@redhat.com>
Cc: <dev@dpdk.org>, Olivier Matz <olivier.matz@6wind.com>,
	Ferruh Yigit <ferruh.yigit@xilinx.com>
Subject: Re: [PATCH v6] usertools: rewrite pmdinfo
Date: Wed, 28 Sep 2022 11:53:04 +0100	[thread overview]
Message-ID: <YzQnkPMcQ83xq5Yy@bricha3-MOBL.ger.corp.intel.com> (raw)
In-Reply-To: <CN7U39JC5Z3S.2RB26GEZP64OX@marty>

On Wed, Sep 28, 2022 at 08:51:39AM +0200, Robin Jarry wrote:
> Bruce Richardson, Sep 26, 2022 at 17:17:
> > > * fixed typo: /etc/ld.so.conf/*.conf -> /etc/ld.so.conf.d/*.conf
> >
> > I am a little uncertain about doing this parsing, and worried it may be a
> > bit fragile. The main file for ld.so still is ld.so.conf, which, on my
> > system anyway, does indeed just have an include for *.conf in the .d
> > directory. However, is it possible that there are systems out there that
> > still have entries in ld.so.conf and possibly elsewhere?
> >
> > I think my preference would still be to shell out to ldconfig and query its
> > database, or to shell out to ldd to get the dependencies of a .so from
> > there. I just think it may be more robust, but at the cost of running some
> > shell commands.
> >
> > However, I don't feel strongly about this, so if others prefer the
> > pure-python ld.so.conf parsing approach better, I'm ok with that.
> 
> I was also concerned with parsing ld.so.conf files. However, I did not
> find a way to get ldconfig simply to print the folders that are to be
> analyzed. This would require some regexp parsing of ldconfig output:
> 
>   ldconfig -vNX 2>/dev/null | sed -nre 's,^(/.*): \(from .*\)$,\1,p'
> 
> I don't know which way is the least hacky.
>
How about "ldconfig -p" and just using the list of libraries given to match
against those requested in the elf file, rather than worrying about
directories at all?

  reply	other threads:[~2022-09-28 10:53 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-13 10:58 [PATCH] " Robin Jarry
2022-09-13 11:29 ` Ferruh Yigit
2022-09-13 11:49   ` Robin Jarry
2022-09-13 13:50     ` Ferruh Yigit
2022-09-13 13:59       ` Robin Jarry
2022-09-13 14:17         ` Ferruh Yigit
2022-09-13 14:17 ` Bruce Richardson
2022-09-13 19:42 ` [PATCH v2] " Robin Jarry
2022-09-13 20:54   ` Ferruh Yigit
2022-09-13 21:22     ` Robin Jarry
2022-09-14 11:46       ` Ferruh Yigit
2022-09-15  9:18         ` Robin Jarry
2022-09-20  9:08 ` [PATCH v3] " Robin Jarry
2022-09-20 10:10   ` Ferruh Yigit
2022-09-20 10:12     ` Robin Jarry
2022-09-20 10:42 ` [PATCH v4] " Robin Jarry
2022-09-20 14:08   ` Olivier Matz
2022-09-20 17:48   ` Ferruh Yigit
2022-09-20 17:50     ` Ferruh Yigit
2022-09-21  7:27       ` Thomas Monjalon
2022-09-21  8:02         ` Ferruh Yigit
2022-09-20 19:15     ` Robin Jarry
2022-09-21  7:58       ` Ferruh Yigit
2022-09-21  9:57         ` Ferruh Yigit
2022-09-22 11:58 ` [PATCH v5] " Robin Jarry
2022-09-22 12:03   ` Bruce Richardson
2022-09-22 15:12   ` Ferruh Yigit
2022-09-26 11:55   ` Olivier Matz
2022-09-26 12:52   ` Robin Jarry
2022-09-26 13:44 ` [PATCH v6] " Robin Jarry
2022-09-26 15:17   ` Bruce Richardson
2022-09-28  6:51     ` Robin Jarry
2022-09-28 10:53       ` Bruce Richardson [this message]
2022-09-28 11:12         ` Robin Jarry
2022-10-04 19:29 ` [PATCH v7] " Robin Jarry
2022-10-10 22:44   ` Thomas Monjalon
2022-10-12 15:16     ` Olivier Matz
2022-10-12 16:16       ` Thomas Monjalon
2022-10-12 16:30         ` Robin Jarry
2022-10-12 16:44           ` Thomas Monjalon
2022-10-12 16:48             ` Robin Jarry
2022-10-12 20:40               ` Thomas Monjalon

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=YzQnkPMcQ83xq5Yy@bricha3-MOBL.ger.corp.intel.com \
    --to=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@xilinx.com \
    --cc=olivier.matz@6wind.com \
    --cc=rjarry@redhat.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.
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).