octave-maintainers
[Top][All Lists]
Advanced

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

Re: error building GUI on Mac OS-X 10.6.8


From: c.
Subject: Re: error building GUI on Mac OS-X 10.6.8
Date: Fri, 22 Feb 2013 12:57:07 +0100

On 20 Feb 2013, at 14:25, Ben Abbott <address@hidden> wrote:

> More detail than you need, but in case it is useful for someone else, I use 
> ...
> 
> (1) ./bootstrap
> (2) macports_configure.sh
> (3) make -j4
> 
> My configure script assumes MacPorts is installed and uses gcc 4.5 by default.
> 
> My first guess is that qscintilla is not installed.
> 
> I have the include file in /opt/local/include/Qsci/qsciscintilla.h
> 
> Ben

Your first guess was right, just installing qscintilla allowed the build to 
finish.
I am now getting this error when starting the GUI:

./run-octave 
The process has forked and you cannot use this CoreFoundation functionality 
safely. You MUST exec().
Break on 
__THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__()
 to debug.

so I can't even get the "welcome" dialog to show up.
The settings I am now using for configure (derived from your script) are the 
following:

---------------
../octave/configure                                        \
    CC=/opt/local/bin/gcc-mp-4.5                           \
    CFLAGS="-pipe -O2 -m64"                                \
    CPPFLAGS="-D_THREAD_SAFE -I/opt/local/include"         \
    LDFLAGS="-L/opt/local/lib -m64"                        \
    CXX=/opt/local/bin/g++-mp-4.5                          \
    CXXFLAGS="-pipe -O2 -m64"                              \
    F77=/opt/local/bin/gfortran-mp-4.5                     \
    FFLAGS="-pipe -O2 -m64"                                \
    LLVM_CONFIG=/opt/local/bin/llvm-config-mp-3.1          \
    --with-lapack="-ldotwrp -Wl,-framework -Wl,Accelerate" \
    --prefix=/opt/octave/3.7                               \
    --enable-gui                                           \
    --enable-jit                                           \
    --disable-java                                         \
    --with-framework-carbon
---------------

Can you see anything important I am missing? 
The only differences I see are that I am using "-O2" instead of "-O0" and 
linking 
to framework Accelerate rather than Atlas, but I don't think these are relevant 
as far as 
the GUI is concerned, are they?

Could you show the output of 

head -n 10 config.log

to help me spot other differences?

Thank you very much!
c.

reply via email to

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