On 1/23/19 2:13 PM, Chet Ramey wrote:
Is there any special reason that rpath isn't managed for Bash (similar to
how its managed for readline)?
Because bash, by default, links statically with its own copy of readline.
If you want to do things differently, there is a mechanism: specify the
--rpat
On 1/22/19 2:25 PM, Chet Ramey wrot
The bash link step doesn't do anything with rpath.
The readline Makefiles set rpath to the installed location of the library
at build time (using $libdir), so if you install it somewhere else that's
going to be wrong. It should probably use $(DESTDIR)$(libdir)
On 1/21/19 12:25 AM, Chet Ramey wrote:
Isn't there a linker option you can supply, possibly as part of LDFLAGS,
to embed that into the bash binary?
I pass `-Wl,-rpath-link=$instdir/lib' to LDFLAGS. It sets RPATH properly
on all the programs I install (including libreadline, and many other
bas
Thank you very much for the prompt reply,
On 1/20/19 7:54 PM, Chet Ramey wrote:
On 1/20/19 12:03 PM, Mohammad Akhlaghi wrote:
Dear Bash developers,
I am trying to build Bash for a relatively closed environment where I don't
want the Bash executable to link with the system's libre
Dear Bash developers,
I am trying to build Bash for a relatively closed environment where I
don't want the Bash executable to link with the system's libreadline and
libncursesw, but my own installation of these libraries.
However, even when I configure bash with `--enable-rpath', and add
`-W
