$ ldd /data/workspace/tools/octave3.2.4/bin/octave-3.2.4
liboctinterp.so => /usr/lib64/octave-2.9.9/liboctinterp.so (0x0000003c95c00000)
liboctave.so => /usr/lib64/octave-2.9.9/liboctave.so (0x0000003c94800000)
libcruft.so => /usr/lib64/octave-2.9.9/libcruft.so (0x0000003c93400000)
Thanks,
This is sort of strange. I'm not very good at linker games, but this looks like a linker problem. I'm surprised linking to the old libraries would work (unresolved symbols etc). You said that ./run-octave in the build directory works as expected so clearly, octave was built with the correct libraries. I think ./run-octave is a script that sets LD_LIBRARY_PATH to get the linker to use the compiled but not installed libraries. You could try maybe try setting the LD_LIBRARY_PATH environment variable to the directory inside /data/workspace/tools/octave3.2.4/ that has liboctinterp.so, etc and see if the ldd output picks those versions and then try to run octave-3.2.4 and see if it gets it right. It's not a permanent solution. I'm not sure why 'make install' would get the linking wrong. I haven't seen that before. You're on redhat? FWIW, the development version/snapshots now use libtool.
--judd