[Top][All Lists]

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

Re: building on macOS?

From: John W. Eaton
Subject: Re: building on macOS?
Date: Tue, 13 Nov 2018 03:20:21 -0500
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1

On 11/12/2018 05:53 PM, Ben Abbott wrote:

Some additional info.

1) The seg-fault is producible manually, and only happens when the qt toolkit is used.

2) The seg-fault does not occur when the gui is run manually. The seg-fault does occur when using —eval “…”.

This suggests that there is some initialization that is not happening when using --eval that does happen when using the gui, but I don't see what that might be.

The log attached results with  ...

./run-octave --gui --norc --silent --no-history --path /Users/bpabbott/Development/mercurial/default/sources/doc/interpreter/ --eval "interpimages ('doc/interpreter/', 'interpn', 'txt');”

If you use all the same options except the --eval "CODE" part, then execute the interpimages function call, does that work?

Similarly, but without the --gui option (so you start with a command line prompt)? The qt toolkit should still be registered and should work as long as you are not using the -cli option for run-octave.


reply via email to

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