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

[John Marino]

Follow-up Comment #2, bug #38175 (project octave):

okay, I'll try to get a stacktrace but I have to set things up to do it.  It
was in a builder that automatically flushes the wrkdirs before.

" The second issue is that the build script hangs if run-octave segfaults. [I
very much don't see this.]"

Well, it happens 100% of the time when being built in pkgsrc and ports.  It
causes a bulk build to completely stop in pkgsrc (because they are serial) and
it logs up a core set in ports (poudriere has parallel builds).  This isn't
new, it's been doing it as long as I've tried to build with gcc 4.7.

Actually I'm using DragonFly BSD.  It can build from FreeBSD's ports.  I can
guarantee all fortran packages are built with the same fortran compiler (as
there is only one available).

Especially with gcc handling, there is significant difference between FreeBSD
and DragonFly while building ports.  The two platforms don't build octave with
the same compiler (even if it did, gcc has a lot of system-specific config
files).  Fortran on DragonFly passes very high on the gcc testsuite though, at
least as high as FreeBSD.





    _______________________________________________________

Reply to this item at:

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

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