[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Solaris: patches to run-octave.in
|
From: |
John W. Eaton |
|
Subject: |
Re: Solaris: patches to run-octave.in |
|
Date: |
Mon, 03 Dec 2007 21:31:35 -0500 |
On 4-Dec-2007, David Bateman wrote:
| 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.
OK, then I don't know what change we should make here, but I do know
that I'd prefer to avoid conditionals on the OS type in deciding how
to avoid this problem.
jwe