> It should look in paths relative to LD_LIBRARY_PATH, do you see it
> doesn't happen ?
>
The problem is, for dlopen relative/absolute names LD_LIBRARY_PATH
is not used.
The man for dlopen says:
If filename contains a slash ("/"), then it is interpreted as a (relative or
absolute) pathname.
On Mon, Oct 16, 2017 at 8:48 AM, Bystricky, Juro
wrote:
> I don’t think you can use LD_LIBRARY_PATH due to the hardcoded relative path
> in "../libnettle.so”.
It should look in paths relative to LD_LIBRARY_PATH, do you see it
doesn't happen ?
>
> I could, however, change the patch from "/usr/li
I don’t think you can use LD_LIBRARY_PATH due to the hardcoded relative path in
"../libnettle.so”.
I could, however, change the patch from "/usr/lib/libnettle.so" to
“libnettle.so”, removing any paths.
That way LD_LIBRARY_PATH can be used if needed. But in the end it will load
the library fro
On Fri, Oct 13, 2017 at 12:24 PM Juro Bystricky
wrote:
> This patch changes the result of the nettle dlopen-test
> from FAIL to PASS. The test used to fail because the test could not
> find and load libnettle.so.
> This patch fixes this by using absolute path instead of relative.
>
> This was the
This patch changes the result of the nettle dlopen-test
from FAIL to PASS. The test used to fail because the test could not
find and load libnettle.so.
This patch fixes this by using absolute path instead of relative.
This was the only test out of 88 that used to fail.
Signed-off-by: Juro Bystric
