Re: error building GUI on Mac OS-X 10.6.8

[Ben Abbott]

On Mar 30, 2013, at 3:28 PM, Ben Abbott wrote:

> On Feb 26, 2013, at 2:49 AM, c. wrote:
> 
>> On 22 Feb 2013, at 14:10, Ben Abbott <address@hidden> wrote:
>> 
>>> On Feb 22, 2013, at 6:57 AM, c. wrote:
>>> 
>>>> 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.
>>> 
>>> Opps!   My mistake.  On MacOS X the GUI needs the patch jwe posted to the 
>>> list earlier in the week.
>>> 
>>>     
>>> https://mailman.cae.wisc.edu/pipermail/octave-maintainers/2013-February/032152.html
>>> 
>>> It's attached.
>>> 
>>> Ben
>>> 
>>> <diffs.txt>
>> 
>> Ben,
>> Thanks now I can see the GUI on mountain lion …
>> c.
> 
> Carlo,
> 
> I've not been able to run the GUI for a couple of weeks now.  When I tried it 
> today, it runs again.  Fonts display nicely.  The only problem I see is that 
> opening a file in the editor causes Octave to abort.  In any event, things 
> are getting better.
> 
> In the event, anyone is interested in the crash log, I've attached it.
> 
> Ben

The crash may not be a MacOS or macports issue.  Presently I'm using a local 
port for qscintilla.  The problem may lie there.

Ben