Re: Passing LD_RUN_PATH through to the linker

2022-12-17 Thread Tim Rice
Hi Kevin, On 12/15/22 1:29 PM, Kevin R. Bulgrien wrote: >> On OpenServer, I usually just build with the SONAME being a full path name. >> >> I am attaching a patch to the libtool 2.4.6 generated during >> a libssh2-1.8.0 build. >> >> Once all testing is complete, I do >> .. >> rm

Re: Passing LD_RUN_PATH through to the linker

2022-12-15 Thread Kevin R. Bulgrien
> On OpenServer, I usually just build with the SONAME being a full path name. > > I am attaching a patch to the libtool 2.4.6 generated during > a libssh2-1.8.0 build. > > Once all testing is complete, I do > .. > rm src/libssh2.la > SCOABSPATH=1 ; export SCOABSPATH > gmake 2>&1 | tee x.log

Re: Passing LD_RUN_PATH through to the linker

2022-12-15 Thread Tim Rice
Kevin, On Wed, 14 Dec 2022, Kevin R. Bulgrien wrote: > During attempts to build top-of-tree libssh2 on a dinosaur (SCO OpenServer > 5.0.7), > an issue with loading indirect dependencies of libssh2.so is occurring. They > can > be worked around by setting LD_LIBRARY_PATH at run-time, however

Re: Passing LD_RUN_PATH through to the linker

2022-12-15 Thread Kevin R. Bulgrien
> On this platform, ld does not have a switch that acts like -rpath but will > write DT_RPATH when LD_RUN_PATH is defined in the environment and ld -R > will cause DT_RUNPATH creation in the linked binary. > > Not having stumbled on a way to modify the project in a way that leaves > DT_RPATH