[Octave-bug-tracker] [bug #38175] 3.6.4rc1 doesn't build with gfortran from gcc 4.7, script never exits after segfault

[Jordi Gutiérrez Hermoso]

Update of bug #38175 (project octave):

                  Status:                    None => Need Info              

    _______________________________________________________

Follow-up Comment #1:

> It always segfaults during the build.

Can you please produce a stack trace? Go into
/wrkdirs/math/octave/work/octave-3.6.4-rc1/doc/interpreter, execute the same
run-octave command but prepend -g, and then follow these instructions:

http://wiki.octave.org/Debugging_Octave#Producing_a_stack_trace

> The second issue is that the build script hangs if run-octave segfaults.

I very much don't see this. Are you sure it's genuinely hanging or is Octave
just taking a long time to save the workspace? Do you see any CPU activity?
(It's not really a core dump, when Octave crashes, it tries to save the
current workspace.) Furthermore, run-octave is a very simple bash script for
running Octave in the build dir, you can read it yourself. This should not be
the source of trouble with the build hanging.

Also, since you're using FreeBSD, I assume you're building everything from
source yourself. If so, are you using the same gfortran version for building
Octave as well as its BLAS dependencies and any other Fortran dependencies?
It's very easy to miscompile a BLAS. Are you sure that part is working
correctly? I'm halfway through a FreeBSD ports build myself, but I had already
started some ports on an older gcc before bootstrapping a newer one, so I had
to restart everything with the same gcc.

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?38175>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/