octave-maintainers
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: build trouble on MacOS 10.5


From: Rob Mahurin
Subject: Re: build trouble on MacOS 10.5
Date: Mon, 21 Dec 2009 00:36:56 -0500
User-agent: Mutt/1.5.20 (2009-06-14)

On Sun, Dec 20, 2009 at 02:52:28PM -0500, Ben Abbott wrote:
> On Dec 20, 2009, at 2:34 PM, Rob Mahurin wrote:
> > On the theory that it's a library conflict, I complied with 
> > 
> >     ./configure CC=gcc-mp-4.3 CXX=g++-mp-4.3 F77=gfortran-mp-4.3
> >     LDFLAGS=-L/opt/local/lib --without-framework-carbon
> >     --without-qhull --without-z --without-hdf5 --without-fftw3
> >     --without-fftw3f --without-glpk --without-curl
> >     --without-framework-opengl --without-qrupdate --without-amd
> >     --without-camd --without-colamd --without-ccolamd
> >     --without-cholmod --without-cxsparse --without-umfpack
> >     --without-arpack --disable-readline
> > 
> > That gives me a run-octave that runs without crashing.  
[...]
> > Now the build succeeds.  
> > 
> >     $ make check
> >       PASS   5321
> >       FAIL      5
> 
> Maybe we should see if it is just one of the libraries that is
> responsible. Perhaps multiple builds with just one of the
> --without-foobar will tell us which one is the problem?

I'm going the other way, removing --withouts one at a time.  I started
with qhull, since that was mentioned in the patch I submitted (thanks
to Rik for applying it).  I got extra failures when I removed
cxsparse, so I left that one.  About half the --withouts are gone,
with three test failures.

> BTW, you mention that run-octave didn't crash. I assume you mean you
> can run and then quit without error?

Right.  With linking to external libraries restricted, I haven't yet
reproduced the bus error on startup whose backtrace we compared
earlier.

Cheers,
Rob


reply via email to

[Prev in Thread] Current Thread [Next in Thread]