octave-maintainers
[Top][All Lists]
Advanced

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

Re: compiling development sources on mac


From: Rob Mahurin
Subject: Re: compiling development sources on mac
Date: Sat, 19 Dec 2009 12:46:33 -0500
User-agent: Mutt/1.5.20 (2009-06-14)

On Sat, Dec 19, 2009 at 12:19:08PM -0500, Ben Abbott wrote:
> On Dec 19, 2009, at 12:08 PM, Rob Mahurin wrote:
> > On Sat, Dec 19, 2009 at 11:57:12AM -0500, Ben Abbott wrote:
> >>>> I use Fink for my dependencies. Fink uses gcc 4.4.2 when it
> >>>> can. Since FLKT does not build with non-Apple compilers on Mac OSX,
> >>>> Fink uses gcc 4.2.1 for FLTK. Mixing gcc 4.4.2 and 4.4.1 appears to
> >>>> be a problem for me since libtool was added (I get a bus-error when
> >>>> I try to run octave).
> >>> 
> >>> I was seeing the same thing (trouble linking with the MacPorts fltk)
> >>> but I was able to install fltk from source, built with the MacPorts
> >>> compilers, and link it with octave-3.2.3.
> >> 
> >> If you're able to produce a working binary, please let me know which
> >> gcc you use for FLTK? ... and what compiler are you use for the
> >> fortran dependencies.
> > 
> > I configured fltk-1.1.9 with the command
> > 
> >     ./configure CC=gcc-mp-4.3 CXX=g++-mp-4.3
> 
> Does the build produce a quartz or x11 result?

Clicking the window created by a plot changes the OSX menu bar to read
"octave", rather than "x11", so I guess it is quartz.

> > and make sure that /usr/local/bin/fltk-config showed up in my path
> > before the macports /opt/local/bin/fltk-config.  Then I was able to
> > build octave-3.2.3 with
> > 
> >     ./configure CC=gcc-mp-4.3 CXX=g++-mp-4.3 F77=gfortran-mp-4.3 
> > LDFLAGS=-L/opt/local/lib LIBS=-lmetis
> > 
> > and successfully use backend("fltk") from within the binary.
> 
> I'm also able to build and run 3.2.3. It is the developer's sources
> (which uses libtool) that are giving trouble :-(
> 
> With 3.2.3, I'm able to use FLTK-aqua/quartz. I haven't tried x11 yet.

We're at the same spot, then.

Cheers,
Rob


reply via email to

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