perl module compilation question

[joseph wholey]

In order to successfully run a "make test" on a specific perl module, I had to export LD_LIBRARY_PATH. After I did that, "make test" and subsequently "make install" ran without issue. What are the ramifications of a reboot, or even someone else logging in and not having LD_LIBRARY_PATH exported? Will the PERL module work?
i.e. the perl module was applied for the db2 dba's. If I "su" to the db2 instance, and issue "echo $LD_LIBRARY_PATH", it points to the db2 instances sqllib path(/rpcjqhome/rpcjq/sqllib/lib). When I compiled the module as root (LD_LIBRARAY_PATH was not set to anything). So I exported LD_LIBRARY_PATH to /opt/IBM/db2/V8.1/lib64. Can anyone provide clarification as to how this will work or if it will work? Thanks.

[Stuart Browne]

Why not add it to the system-wide '/etc/ld.so.conf' (or into '/etc/ld.so.conf.d/db2.conf') and re-run 'ldconfig'?

[joseph wholey]

Thanks for the info... that is a big help. However, would you happen to know what kind of results to expect with what I did?

[Heironimus]

If your module needs LD_LIBRARY_PATH and it's not set you'll get an error when it tries to load telling you that it can't find some shared library.

[joseph wholey]

I needed to export the LD_LIBRARY_PATH in order to successfully compile the modules. My dba's have logged in and confirmed that all is working as they expect. Their LD_LIBRARY_PATH does not point to the same place that I exported the LD_LIBRARY_PATH to.