oss-sec mailing list archives
Re: Fixing the glibc runtime linker
From: Casper.Dik () oracle com
Date: Fri, 20 Feb 2015 10:22:53 +0100
FWIW, relative RPATHs are quite fundamental to our test execution environment, and any patch that unconditionally ignores them would have to be reverted in our tree.
But wouldn't that make the libraries and executables less reliable? They can pick up random libraries or cause some delays when one of the relative paths points to a NFS mounted directory. Any reason you can't change to using LD_LIBRARY_PATH for testing? I've run into relative directories and even /net/xxx/ search paths but I believe these should never be used as part of a binary distribution. Casper
Current thread:
- Re: Fixing the glibc runtime linker, (continued)
- Re: Fixing the glibc runtime linker Tim Brown (Feb 19)
- Re: Fixing the glibc runtime linker Paul Pluzhnikov (Feb 19)
- Re: Fixing the glibc runtime linker Rich Felker (Feb 19)
- Re: Fixing the glibc runtime linker Paul Pluzhnikov (Feb 19)
- Re: Fixing the glibc runtime linker Rich Felker (Feb 19)
- Re: Fixing the glibc runtime linker Paul Pluzhnikov (Feb 20)
- Re: Fixing the glibc runtime linker Tim Brown (Feb 20)
- Re: Fixing the glibc runtime linker Rich Felker (Feb 20)
- Re: Fixing the glibc runtime linker Paul Pluzhnikov (Feb 20)
- Re: Fixing the glibc runtime linker Rich Felker (Feb 20)
- Re: Fixing the glibc runtime linker Tim Brown (Feb 19)
- Re: Fixing the glibc runtime linker Paul Pluzhnikov (Feb 20)
- Re: Fixing the glibc runtime linker Rich Felker (Feb 21)