Re: gnulib and automake

[John W. Eaton]

On 28-Oct-2009, John W. Eaton wrote:

|   * When linking the final Octave exectuable, libtool generates a
|     src/octave script which handles all the details of LD_LIBRARY_PATH
|     so that Octave can run in the build directory.  The run-octave
|     script no longer does that job.  Instead, it simply sets things
|     like the load path and the info ile directory and calls the
|     src/octave script.  However, since src/octave is a script, we
|     can't run gdb or valgrind on it as before, so debugging with
|     "run-octave -g" is currently broken.  I'd like to fix this, but I
|     don't know what the best solution is.  The generated src/octave
|     script doesn't seem to have a way to handle running a debugger on
|     the real executable file.  What do other libtool-based projects
|     do?

I discovered the "--mode=exec" option for libtool and modified the
run-octave script to use that, so now "run-octave -g" works again.

jwe