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: Ben Abbott
Subject: Re: error building GUI on Mac OS-X 10.6.8
Date: Sat, 11 Aug 2012 10:53:14 -0400

On Aug 11, 2012, at 10:34 AM, Ben Abbott wrote:

> 
> On Aug 11, 2012, at 6:18 AM, Torsten wrote:
> 
>> On 11.08.2012 09:40, Michael Goffioul wrote:
>>> On Sat, Aug 11, 2012 at 5:12 AM, Ben Abbott <address@hidden
>>> <mailto:address@hidden>> wrote:
>>> 
>>> 
>>>   On Aug 11, 2012, at 12:00 AM, Ben Abbott wrote:
>>> 
>>>> 
>>>> On Aug 10, 2012, at 10:05 PM, John W. Eaton wrote:
>>>> 
>>>>> On 10-Aug-2012, Ben Abbott wrote:
>>>>> 
>>>>> | On Aug 10, 2012, at 9:10 PM, John W. Eaton wrote:
>>>>> |
>>>>> | > On 10-Aug-2012, Thomas Yengst wrote:
>>>>> | >
>>>>> | > | I successfully built the development version with help from
>>>   Ben. Finally, success on OS-X. Now I'm trying to build Jacob's GUI
>>>   and run into something that I haven't seen on the maintainers list.
>>>>> | > |
>>>>> | > | I did the following;:
>>>>> | > | hg update gui
>>>>> | > | hg pull
>>>>> | > | cd gui
>>>>> | > | qmake
>>>>> | > | make
>>>>> | > |
>>>>> | > | ... and got fairly far into the compile before....
>>>>> | >
>>>>> | > I'm not sure what is causing the compile problems, but I've
>>>   recently
>>>>> | > changed the build system so that you should now just do
>>>   ./autogen.sh
>>>>> | > in the source tree and then configure in the build tree, then
>>>   make.
>>>>> | > You don't need to run qmake or cd to the gui directory to run
>>>   make,
>>>>> | > just do it from the top-level directory
>>>>> | >
>>>>> | > See also this message about a minor problem that I'm working
>>>   on fixing
>>>>> | > but have not checked in yet:
>>>>> | >
>>>>> | >
>>>   
>>> https://mailman.cae.wisc.edu/pipermail/octave-maintainers/2012-August/029359.html
>>>>> | >
>>>>> | > If you still have problems, then please report the details.
>>>>> | >
>>>>> | > Thanks,
>>>>> | >
>>>>> | > jwe
>>>>> |
>>>>> | My tip is ...
>>>>> 
>>>>> In Mercurial, "tip" is just the most recent changeset.
>>>>> 
>>>>> Please use "hg id" instead.  That will tell you the branch you are on
>>>>> and the changeset id that you have on that branch.
>>>>> 
>>>>> | ../qterminal/libqterminal/moc_QTerminal.cpp:10:30: fatal error:
>>>   thread/QTerminal.h: No such file or directory
>>>>> | compilation terminated.
>>>>> | ../qterminal/libqterminal/moc_QTerminalInterface.cpp:10:39:
>>>   fatal error: thread/QTerminalInterface.h: No such file or directory
>>>>> | compilation terminated.
>>>>> 
>>>>> On your system, what directories are these files in?
>>>>> 
>>>>> jwe
>>>> 
>>>> $ hg id
>>>> 2eb789da13c3 (gui)
>>>> 
>>>> The files are both in "gui/qterminal/libqterminal"
>>>> 
>>>>     gui/qterminal/libqterminal/QTerminal.h
>>>>     gui/qterminal/libqterminal/QTerminalInterface.h
>>>> 
>>>> I don't have a "thread" subdirectory.
>>>> 
>>>> Ben
>>> 
>>>   I manually modified the sources to remove the "thread/".  The build
>>>   now ends with ...
>>> 
>>>   /bin/sh ../../libtool  --tag=CXX   --mode=compile
>>>   /opt/local/bin/g++-mp-4.5 -DHAVE_CONFIG_H -I. -I../..
>>>    -I/opt/local/include -I/opt/local/include/QtCore
>>>   -I/opt/local/include/QtGui -I/opt/local/include/QtNetwork
>>>   -I./../qterminal/libqterminal -I./m-editor -I./octave-adapter
>>>   -I./qtinfo -I./../../libcruft/misc -I../../liboctave
>>>   -I./../../liboctave -I../../src/interp-core -I./../../src
>>>   -I./../../src/interp-core -I./../../src/interpfcn
>>>   -I./../../src/octave-value -I./../../src/operators
>>>   -I./../../src/parse-tree -D_THREAD_SAFE -pthread
>>>   -I/opt/local/include  -pipe -O0 -g -m64 -ggdb3 -gstabs
>>>   -D_THREAD_SAFE -pthread -D_THREAD_SAFE -pthread -MT
>>>   liboctgui_la-octave-link.lo -MD -MP -MF
>>>   .deps/liboctgui_la-octave-link.Tpo -c -o liboctgui_la-octave-link.lo
>>>   `test -f 'octave-adapter/octave-link.cc' || echo
>>>   './'`octave-adapter/octave-link.cc
>>>   libtool: compile:  /opt/local/bin/g++-mp-4.5 -DHAVE_CONFIG_H -I.
>>>   -I../.. -I/opt/local/include -I/opt/local/include/QtCore
>>>   -I/opt/local/include/QtGui -I/opt/local/include/QtNetwork
>>>   -I./../qterminal/libqterminal -I./m-editor -I./octave-adapter
>>>   -I./qtinfo -I./../../libcruft/misc -I../../liboctave
>>>   -I./../../liboctave -I../../src/interp-core -I./../../src
>>>   -I./../../src/interp-core -I./../../src/interpfcn
>>>   -I./../../src/octave-value -I./../../src/operators
>>>   -I./../../src/parse-tree -D_THREAD_SAFE -pthread
>>>   -I/opt/local/include -pipe -O0 -g -m64 -ggdb3 -gstabs -D_THREAD_SAFE
>>>   -pthread -D_THREAD_SAFE -pthread -MT liboctgui_la-octave-link.lo -MD
>>>   -MP -MF .deps/liboctgui_la-octave-link.Tpo -c
>>>   octave-adapter/octave-link.cc  -fno-common -DPIC -o
>>>   .libs/liboctgui_la-octave-link.o
>>>   m-editor/find-dialog.cc: In member function 'void
>>>   find_dialog::search_next()':
>>>   m-editor/find-dialog.cc:150:39: error: no matching function for call
>>>   to 'QsciScintilla::findFirst(QString, bool, bool, bool, bool, bool,
>>>   int&, int&, bool, bool)'
>>>   /opt/local/include/Qsci/qsciscintilla.h:604:18: note: candidate is:
>>>   virtual bool QsciScintilla::findFirst(const QString&, bool, bool,
>>>   bool, bool, bool, int, int, bool)
>>>   make[4]: *** [liboctgui_la-find-dialog.lo] Error 1
>>>   make[4]: *** Waiting for unfinished jobs....
>>>   mv -f .deps/liboctgui_la-octave-link.Tpo
>>>   .deps/liboctgui_la-octave-link.Plo
>>> 
>>>   I have qscintilla-2.4.6_0 installed.
>>> 
>>> 
>>> 
>>> You need a newer version of qscintilla. I have 2.6.1, and previously I
>>> had 2.5.x (and it used to work as well).
>>> 
>>> Michael.
>>> 
>> 
>> Hello,
>> 
>> I was not aware that the last boolean parameter of findFirst() used for
>> find/replace in the editor was not added before 2011 in version 2.5 of
>> qscintilla.
>> 
>> This parameter 'posix' controls the interpretation of regular
>> expressions ("If posix is true then a regular expression is treated in a
>> more POSIX compatible manner by interpreting bare ( and ) as tagged
>> sections rather than \( and \)."). The parameter is optional (false by
>> default) and I think it can be dropped for compatibility with older
>> versions of qscintilla (see attached patch).
>> 
>> Torsten                      
>> 
>> <findFirst.diff>
> 
> That fixed the problem.  My build now continues.
> 
> Ben

The the "thread" subdirectory references removed and the findFirst.diff patch 
applied, my build completes.  When I run, I encounter ...

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.
panic: Segmentation fault: 11 -- stopping myself...
attempting to save variables to `octave-workspace'...

The first two lines show up 17 times. I cut the other 16 out above.

Same result from gdb, and the backtrace is empty.

Ben







reply via email to

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