Okay, some thoughts:

- To me from Linux/Solaris background, it's LD_LIBRARY_PATH and it names
the *directories* in which shared objects will be found.
- In Lin/Sol yo make the path include any dir containing any .so you
need whose path is not coded in the executable itself, excepting the system
library dirs (/lib and /usr/lib).
- Remember to EXPORT the LD_LIBRARY_PATH after you set it.
- LD_LIBRARY_PATH=/foo/bar:/foo/bar/woof:/arf/azotic; export

On Sun, Jan 1, 2017 at 2:39 PM, Pete Helgren <pete@xxxxxxxxxx> wrote:

The question is where to set it and what to include in it. I noticed that
WRKENVVAR *JOB showed quite a few environment variables that were set by
the install script so, following that logic, I when ahead and used
ADDENVVAR 'LD_LIBRARY_LIST' and included '/QOpenSys/usr/lib'. The install
still fails.

I can also add it to my .profile and see if that makes a difference. As I
understand it, the library is needed at run time, so I have a couple of
ideas that I may try to retain the install and then start the database
daemon, which is where I *think* this guys is failing. Maybe add a copy to
the PATH on the startup script and see what that does....

Pete Helgren
GIAC Secure Software Programmer-Java
Twitter - Sys_i_Geek IBM_i_Geek

On 12/31/2016 8:02 PM, Jack Woehr wrote:

Can you set LD_LIBRARY_LIST and try the script again

This is the IBMi Open Source Roundtable (OpenSource) mailing list
To post a message email: OpenSource@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/opensource
or email: OpenSource-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/opensource.

As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2022 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.