On Sun, Jan 22, 2017 at 09:23:18PM -0500, Sergio Durigan Junior wrote:
> On Sunday, January 22 2017, Adrian Bunk wrote:
>...
> > But the worst is that this cannot work properly with multiarch.
> > On my multiarch enabled system I might be using either the
> > i386 newlisp package or the amd64 newlisp package.
> > I might have both the i386 and the amd64 version of the library
> > to load installed.
> > As long as newlisp searches in the same paths in both cases,
> > it is guaranteed to not find the correct library in at least
> > one case.
>
> Hm, I totally understand the problem, but I've been struggling to find a
> good solution for this. Of course, I don't want to search on all the
> valid paths for all architectures supported by Debian. Instead, the
> solution would be to check the supported archs on the fly and adjust the
> paths accordingly. What do you think?
>...
Why does newlib try to do anything with paths at all?
In the end it passes the name to dlopen(), and if it would just pass a
filename with soname (e.g. libpq.so.5) the dynamic linker would search
the correct paths automatically.
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
