"Doug Turner" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > Adrian M wrote: > > Hi... > > When I moved from 1.0 to 1.3 ( and head branch mozilla ), I noticed that all > > the dlopen() calls for loading the shared objects from within the > > "components" directory > > are now made with: > > dlopen( "./components/libsomething.so", ... ) as opposed to 1.0 which > > were made with the full path: > > dlopen( > > "/home/someuser/cvs/mozilla.org/1.0/mozilla/dist/bin/componenets/libsomethin > > g.so", ... ). > > > > Is this the correct behaviour? > > As a result we have to do: > > cd /home/someuser/cvs/mozilla.org/1.0/mozilla/dist/bin > > ./mozilla > > > > We cannot run > > /home/someuser/cvs/mozilla.org/1.0/mozilla/dist/bin/mozilla from anyplace. > > > > Is there something I can do ( an option to the configure script etc ) that > > will make mozilla be run from anywhere? What I'm missing? > > > > Thanks, > > Adrian > > Most people use the run-mozilla.sh script with allows for this, if I am > not mistaken.
But I'm running the run-mozilla.sh ( running .../mozilla/dist/bin/mozilla will actually invoke the run-mozilla.sh ). I tried to run .../mozilla/dist/bin/run-mozilla.sh mozilla-bin with the same result. Always the dlopen( ) is done with dlopen( "./components/lib*.so", ... ), not with the full path - no matter how your LD_LIBRARY_PATH and other env var are set. Let's say LD_LIBRARY_PATH points to /cvs/mozilla.org/mozilla/dist/bin:/cvs/mozilla.org/mozilla/dist/bin/componen ts/:... The dlopen( "./components/lib*.so", ... ) fails on our system if the program is not run from dist/bin/ - is this a system call problem or is that the expected behaviour ? Thanks, Adrian > I think some of this will go away when we complete bug 193442. > > Regards, > > Doug Turner >
