Date: Tue, 12 Jan 2016 22:27:29 +0000 From: "Montgomery-Smith, Stephen" <stephen@missouri.edu> To: Don Lewis <truckman@FreeBSD.org>, "stephen@FreeBSD.org" <stephen@FreeBSD.org> Cc: "ports-committers@freebsd.org" <ports-committers@freebsd.org>, "svn-ports-all@freebsd.org" <svn-ports-all@freebsd.org>, "svn-ports-head@freebsd.org" <svn-ports-head@freebsd.org> Subject: Re: svn commit: r405907 - head/Mk Message-ID: <56957DCF.3090209@missouri.edu> In-Reply-To: <201601122148.u0CLmJvF087237@gw.catspoiler.org> References: <201601122148.u0CLmJvF087237@gw.catspoiler.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 01/12/2016 03:48 PM, Don Lewis wrote: > On 12 Jan, Stephen Montgomery-Smith wrote: >> Author: stephen >> Date: Tue Jan 12 19:56:13 2016 >> New Revision: 405907 >> URL: https://svnweb.freebsd.org/changeset/ports/405907 >> >> Log: >> - Svn revision 405533 upgraded /math/octave to version 4.0.0. This ve= rsion >> of octave segfaults with FreeBSD. Many of the octave-forge-* ports = don't >> build, and those that build don't work. So they are all being marke= d >> broken until it is fixed. >=20 > It's actually octave-gui that is segfaulting. The cause is that the > executable is bringing in both libstdc++ and libc++, and the reason for > that is likely the addition of USE_GCC=3Dyes to the port Makefile that wa= s > done at the same time as the version upgrade. >=20 > I have no idea what happens if USE_GCC=3Dyes is removed from the Makefile= . > there may be problems with compiling the source with the combination of > clang and gfortran. I'll give it a try, though. >=20 > Another possibility would be do disable the gui. Looking at configure, > there is a --disable-gui option that we don't expose as a port option. I > don't know what libraries are needed by the gui, but of all the > libraries in LIB_DEPENDS, libfltk.so, libftgl.so, and libqscintilla2.so > are the ones that are linked to libc++.so. >=20 > Unfortunately, "octave --no-gui" doesn't work. It still tries to run > octave-gui and dies. >=20 >=20 >=20 I had a different experience. The octave-cli command segfaulted for me. I run it through gdb (version 7.10) and valgrind after building octave with the "-g" option set. It looks like the error takes place before any code is actually run, indicating that probably global data allocation may be the problem. The error is freeing the NULL pointer.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?56957DCF.3090209>