Re: Segmentation fault when compiling octave

[Jordi Gutiérrez Hermoso]

On 27 September 2012 16:05, Feuerbacher, Alan
<address@hidden> wrote:
> Jordi wrote:
>
>> Can you adapt these instructions and produce a stack trace?
>>
>>     http://octave.1599824.n4.nabble.com/GNU-Octave-3-6-3-Released-
>> tp4643700p4643765.html
>
> Surprisingly, it didn't crash. 840 tests passed, 1 failed, and the last 
> output was "Program exited normally". Then "bt" output "No stack."
>
> I don't know if this helps, but just running "./run-octave" in the
> build directory (..../octave-3.6.3) gives the segmentation fault.

Yes, that. Does "./run-octave -g" not crash? Can you try doing this
and running some tests? I mean, "./run-octave -g", then "run" inside
gdb, then "demo surf" inside Octave?

> When I run ldd on them, the output from ldd octave shows 3 octave
> related libraries "not found" and just a few of the expected
> libraries listed.

Yes, this is correct and expected. Part of the run-octave script's job
is to temporarily set the right paths to find those libraries (they're
also in your build tree) so you can run Octave in-place in the build
tree.

- Jordi G. H.