Timeline for LD_LIBRARY_PATH Configuration Setup Issues
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 11, 2018 at 1:44 | answer | added | Speeddymon | timeline score: 0 | |
| Jan 10, 2017 at 19:50 | audit | Suggested edits | |||
| Jan 10, 2017 at 20:53 | |||||
| Dec 29, 2016 at 17:52 | vote | accept | Gaurav Bhaskar | ||
| Dec 27, 2016 at 16:55 | answer | added | Lacek | timeline score: 0 | |
| Dec 27, 2016 at 6:57 | comment | added | Gaurav Bhaskar | @Thomas- I believe I have specified the actual problem; I have Pro *C and Pro *Cobol programs. Pro *C uses libraries from ORACLE_HOME where database software is installed and Pro *Cobol uses libraries where Oracle Database Client is used. So any one of them can work at a time, else I get Segmentation Fault error for other one and vice verca. How can I specify different LD_LIBRARY_PATH and force application to use specific one. Let me know. Thanks! | |
| Dec 26, 2016 at 10:26 | comment | added | Thomas | Could you please eloberate the actual problem that occurs. LD_LIBRARY_PATH is normally used to lookup libraries, and yes, if a library is found in the first path of LD_LIBRARY_PATH, that one is used. So if you have different environments that search for the same library but with different properties, you have to specify different LD_LIBRARY_PATH variables. But at the moment the actual problem is not very clear... | |
| Dec 26, 2016 at 6:55 | history | asked | Gaurav Bhaskar | CC BY-SA 3.0 |