Re: Weird ldd problem

2021-07-21 Thread Christos Zoulas
In article , Chavdar Ivanov wrote: >I have to read more to understand it though... It is a kernel issue. The kernel is passing an executable pathname that is not an absolute path and RTLD correctly refuses to honor $ORIGIN. christos

Re: Weird ldd problem

2021-07-18 Thread RVP
On Sun, 18 Jul 2021, Chavdar Ivanov wrote: The main difference is indeed ... (RPATH) Library rpath: [$ORIGIN/:$ORIGIN/../../lib/libast:$ORIGIN/cmds:$ORIGIN/../../lib/libdll] I have to read more to understand it though... $ORIGIN? That's yet another way to locate shared

Re: Weird ldd problem

2021-07-18 Thread RVP
On Sun, 18 Jul 2021, Chavdar Ivanov wrote: # file ksh93 ksh93: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /usr/libexec/ld.elf_so, for NetBSD 9.99.45, with debug_info, not stripped # ldd ./ksh93 ./ksh93: -lm.0 => /usr/lib/libm.so.0 -lc.12

Re: Weird ldd problem

2021-07-18 Thread Chavdar Ivanov
On Sun, 18 Jul 2021 at 10:26, RVP wrote: > > On Sun, 18 Jul 2021, Chavdar Ivanov wrote: > > > # file ksh93 > > ksh93: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), > > dynamically linked, interpreter /usr/libexec/ld.elf_so, for NetBSD > > 9.99.45, with debug_info, not stripped > > # ldd

Weird ldd problem

2021-07-18 Thread Chavdar Ivanov
Hi, Not really a problem, but is bugging me, I have no clue why this happens. I used to follow the ksh93 development branch and regularly used to build it for -current. The last one I built was circa February 2020 (${.sh.version} -> 2020.0.0-beta1-222-g8cf92b28), apparently for NetBSD 9.99.45. It