On 11 Nov 2002, Eric Schwartz wrote:

> On a linux system, I've developed a extension to STAF (see previous
> posts) that links to libSTAF.so to provide various bits of
> functionality.  However, I had forgotten that I'd set my
> LD_LIBRARY_PATH to find said library, so it was always loaded
> correctly.
>
> I discovered that it wasn't loading correctly when I ran some CGI code
> I'd written around that extension.  So I did what I do in every other
> programming language, and set ENV['LD_LIBRARY_PATH'] to point to
> /usr/local/staf/lib, where the library resides.  Alas, this did not
> work.  In fact, if I unset LD_LIBRARY_PATH in my environment and tried
> this, it didn't work there either.
>
> I'd suspect myself before I'd suspect ruby, but in this case, I think
> I've covered all my bases.  Comments are welcome.

why not compile the module using LD_RUN_PATH?  relying on LD_LIBRARY_PATH is
evil ;-)

-a

-- 

 ====================================
 | Ara Howard
 | NOAA Forecast Systems Laboratory
 | Information and Technology Services
 | Data Systems Group
 | R/FST 325 Broadway
 | Boulder, CO 80305-3328
 | Email: ahoward / fsl.noaa.gov
 | Phone:  303-497-7238
 | Fax:    303-497-7259
 ====================================