DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Pascal Mazon <pascal.mazon@6wind.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] eal: do not try to load library with a local pathname
Date: Fri, 18 Apr 2014 00:47:03 +0200	[thread overview]
Message-ID: <1892856.uUH5QI7dPr@xps13> (raw)
In-Reply-To: <20140415135704.GB3557@hmsreliant.think-freely.org>

> > When loading a library "libfoo.so" (depending on "libbar.so", located in
> > an
> > entirely different folder), with a LD_LIBRARY_PATH=/path/to/libfoo.so", it
> > 
> > returns an error:
> >  EAL: ./libfoo.so: cannot open shared object file: No such file or
> >  directory
> > 
> > If the first dlopen() fails (here, because it can't find all
> > dependencies),
> > the code requires for a second dlopen() that looks for "./libfoo.so". It
> > turns on pathname matching, which does not use LD_LIBRARY_PATH. As a
> > result, it fails because it cannot find "./libfoo.so".
> > 
> > The error message matches the error of the second dlopen(), not the
> > first's.
> > 
> > Do not try to look for a different library ("./"-prefixed) than the one
> > provided in argument. Let the dynamic library management handle it, just
> > provide an appropriate LD_LIBRARY_PATH.
> > 
> > Signed-off-by: Pascal Mazon <pascal.mazon@6wind.com>
> 
> Acked-by: Neil Horman <nhorman@tuxdriver.com>

Applied for version 1.6.0r2.

Thanks, it's a good usability improvement (simpler is better :)
-- 
Thomas

      reply	other threads:[~2014-04-17 22:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-15 13:50 David Marchand
2014-04-15 13:57 ` Neil Horman
2014-04-17 22:47   ` Thomas Monjalon [this message]

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=1892856.uUH5QI7dPr@xps13 \
    --to=thomas.monjalon@6wind.com \
    --cc=dev@dpdk.org \
    --cc=pascal.mazon@6wind.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).