Lines Matching refs:to
7 OpenSSL uses the compiler to link programs and shared libraries
10 OpenSSL's generated Makefile uses the C compiler command line to
12 objects. Because of this, any linking option that's given to the
16 to read your compiler documentation to figure out what is acceptable,
17 and `ld(1)` to figure out what linker options are available.
25 binaries will not find them and therefore fail to run, unless they get
30 you. It's therefore advisable to set it explicitly when configuring,
31 unless the libraries are to be installed in directories that you know
32 to be in the default list.
40 Possible options to set the runtime shared library search path include
50 them to the Makefile that they build. (In fact, all arguments starting
57 includes the variable LIBRPATH, which is a convenience variable to be
64 On modern ELF based systems, there are two runtime search paths tags to
77 Exactly which of `DT_RPATH` or `DT_RUNPATH` is set by default appears to
78 depend on the system. For example, according to documentation,
79 `DT_RPATH` appears to be deprecated on Solaris in favor of `DT_RUNPATH`,
83 How to choose which runtime search path tag is to be set depends on
84 your system, please refer to ld(1) for the exact information on your
85 system. As an example, the way to ensure the `DT_RUNPATH` is set on
86 Debian GNU/Linux systems rather than DT_RPATH is to tell the linker to
93 for runtime search path relative to the directory containing current
104 circumstances, it would be sufficient to link with OpenSSL shared library
106 also cases when you'd have to explicitly specify runtime search path
111 latter is likely to require special care because linkers usually look
112 for shared libraries first and tend to remain "blind" to static OpenSSL
113 libraries. Referring to system documentation would suffice, if not for
115 differently, add `_a` suffix to link with them, e.g. `-lcrypto_a`.
