[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Solaris: patches to run-octave.in
From: |
David Bateman |
Subject: |
Re: Solaris: patches to run-octave.in |
Date: |
Tue, 04 Dec 2007 02:40:47 +0100 |
User-agent: |
Thunderbird 1.5.0.7 (X11/20060921) |
John W. Eaton wrote:
> On 4-Dec-2007, David Bateman wrote:
>
> | Moritz Borgmann wrote:
> | >> In any case, I don't think we absolutely have to exec Octave in the
> | >> script. David, would removing LD_PRELOAD and the exec fix the problem
> | >> for you?
> | >
> | > To conclude the discussion, I propose the following patchset:
> | >
> |
> | The problem is that issues only occurred for me when there was an API
> | mismatch between the installed libraries and the ones in the build tree.
> | I suppose we can artificially create this situation by changing the api
> | version numbers between the installed libraries and those in the build
> | tree and testing your patch.. I'll try to do that sometime this week to
> | test this.
>
> Could you also just build and install, run the run-octave script in
> the build tree and then use lsof to see which libraries are opened for
> the copy of Octave that you started?
>
> jwe
>
lsof gives
octave 17379 adb014 mem REG 3,5 368797 6071630
/opt/octave-2.9/lib/octave-2.9.17+/libcruft.so.2.9.17+
octave 17379 adb014 mem REG 3,5 48572777 6071632
/opt/octave-2.9/lib/octave-2.9.17+/liboctave.so.2.9.17+
octave 17379 adb014 mem REG 3,5 78730472 6071634
/opt/octave-2.9/lib/octave-2.9.17+/liboctinterp.so.2.9.17+
when the patch is applied and ./run-octave is used. These are the
installed libraries. Without the patch I get
octave 17724 adb014 mem REG 3,6 368813 67193566
/home/adb014/nobackup/perso/octave/cvs/octave-nosuitesparse/libcruft/libcruft.so
octave 17724 adb014 mem REG 3,6 47899802 51365632
/home/adb014/nobackup/perso/octave/cvs/octave-nosuitesparse/liboctave/liboctave.
so
which are the versions in my build tree. So this doesn't seem to fix the
problem I had.
D.