building on macOS?

classic Classic list List threaded Threaded
56 messages Options
123
Reply | Threaded
Open this post in threaded view
|

Re: building on macOS?

Dmitri A. Sergatskov


On Tue, Nov 6, 2018 at 12:42 PM Dmitri A. Sergatskov <[hidden email]> wrote:
Back to the original problem. Just now building the latest tip on linux with make -j8 I got:

<<<<
  GEN      doc/interpreter/splinefit3.png
  GEN      doc/interpreter/splinefit4.png
  GEN      doc/interpreter/splinefit6.png
  MAKEINFO ../doc/interpreter/octave.info
  TEXI2DVI doc/interpreter/octave.dvi
  MAKEINFO doc/interpreter/octave.html/.octave-html-stamp
/usr/bin/texi2dvi: etex exited with bad status, quitting.
make[2]: *** [Makefile:30580: doc/interpreter/octave.dvi] Error 1
make[2]: *** Waiting for unfinished jobs....
make[2]: Leaving directory '/d2/home/dima/src/octave/gcc_def'
make[1]: *** [Makefile:26948: all-recursive] Error 1
make[1]: Leaving directory '/d2/home/dima/src/octave/gcc_def'
make: *** [Makefile:10811: all] Error 2
>>>>

Re-running "make -j8" :

<<<<
GEN      doc/interpreter/octave.html/splinefit4.png
  GEN      doc/interpreter/octave.html/splinefit6.png
  GEN      doc/interpreter/octave.html/octave.css
  GEN      doc/interpreter/octave_interpreter.qhc
  TEXI2DVI doc/interpreter/octave.dvi
/usr/bin/texi2dvi: etex exited with bad status, quitting.
make[2]: *** [Makefile:30580: doc/interpreter/octave.dvi] Error 1
make[2]: Leaving directory '/d2/home/dima/src/octave/gcc_def'
make[1]: *** [Makefile:26948: all-recursive] Error 1
make[1]: Leaving directory '/d2/home/dima/src/octave/gcc_def'
make: *** [Makefile:10811: all] Error 2
>>>>

Running "make V=1" -- finished building w/o problem.

This is on Fedora 29.

I played with this a little more.

If I just delete doc/ (in the build directory) and re-run make -j8 it finishes fine.
If i remove entire octave directory and re-do entire (clone/update/bootstap/configure)
it crashes again with the same error:

GEN      doc/interpreter/octave.html/splinefit4.png
  GEN      doc/interpreter/octave.html/splinefit6.png
  GEN      doc/interpreter/octave.html/octave.css
  DVIPS    doc/refcard/refcard-letter.ps
  DVIPS    doc/refcard/refcard-a4.ps
  GEN      doc/interpreter/octave_interpreter.qhc
  TEXI2DVI doc/interpreter/octave.dvi
/usr/bin/texi2dvi: etex exited with bad status, quitting.
make[2]: *** [Makefile:30580: doc/interpreter/octave.dvi] Error 1
make[2]: Leaving directory '/d2/home/dima/src/octave/gcc_def'
make[1]: *** [Makefile:26948: all-recursive] Error 1
make[1]: Leaving directory '/d2/home/dima/src/octave/gcc_def'

Running "make -j8 V=1" finishes build w/o error.

Since there is no actual crash -- there is nothing in the logs...

Dmitri.
--



 

Dmitri.
--


Reply | Threaded
Open this post in threaded view
|

Re: building on macOS?

apjanke-floss
In reply to this post by Sebastian Schöps

On 11/7/18 3:01 PM, Sebastian Schöps wrote:

> Carlo de Falco-2 wrote
>> $ hg bisect -g
>> The first bad revision is:
>> changeset:   25994:332be8be16eb
>> user:        John W. Eaton &lt;
>> jwe@
>> &gt;
>> date:        Fri Sep 28 18:18:09 2018 -0400
>> summary:     dynamically load qt graphics
>>
>> can someone confirm that a00379f6f8c4 builds correctly while 332be8be16eb
>> fails?
> so far I can confirm that a00379f6f8c4 builds correctly.
>
> Sebastian
>
Building from the head of the repo on macOS 10.13.6 with Xcode 10 works
OK for me: no crashes or errors during the build. Though I do get a
bunch of error messages after the build finishes:


   GEN      src/octave-cli-5.0.0
   GEN      doc/interpreter/doc-cache

Octave successfully built.  Now choose from the following:

    ./run-octave    - to run in place to test before installing
    make check      - to run the tests
    make install    - to install (PREFIX=/tmp/test-octave)

    HG ID for this build is "920a4ad8043b"

/var/folders/_4/9mx5ryp52bb_z6drbcbrhwl40000gn/T/bfbM3nHdn8:112: Unknown
command `codequoteundirected'.
/var/folders/_4/9mx5ryp52bb_z6drbcbrhwl40000gn/T/bfbM3nHdn8:1411:
Unknown command `leq'.
/var/folders/_4/9mx5ryp52bb_z6drbcbrhwl40000gn/T/bfbM3nHdn8:1411:
Misplaced {.
/var/folders/_4/9mx5ryp52bb_z6drbcbrhwl40000gn/T/bfbM3nHdn8:1411:
Misplaced }.
/var/folders/_4/9mx5ryp52bb_z6drbcbrhwl40000gn/T/bfbM3nHdn8:7694:
Unknown command `leq'.
/var/folders/_4/9mx5ryp52bb_z6drbcbrhwl40000gn/T/bfbM3nHdn8:7694:
Misplaced {.
/var/folders/_4/9mx5ryp52bb_z6drbcbrhwl40000gn/T/bfbM3nHdn8:7694:
Misplaced }.
/var/folders/_4/9mx5ryp52bb_z6drbcbrhwl40000gn/T/bfbM3nHdn8:7694:
Unknown command `leq'.
/var/folders/_4/9mx5ryp52bb_z6drbcbrhwl40000gn/T/bfbM3nHdn8:7694:
Misplaced {.
/var/folders/_4/9mx5ryp52bb_z6drbcbrhwl40000gn/T/bfbM3nHdn8:7694:
Misplaced }.
/var/folders/_4/9mx5ryp52bb_z6drbcbrhwl40000gn/T/bfbM3nHdn8:13662:
Unknown command `leq'.
/var/folders/_4/9mx5ryp52bb_z6drbcbrhwl40000gn/T/bfbM3nHdn8:13662:
Misplaced {.
/var/folders/_4/9mx5ryp52bb_z6drbcbrhwl40000gn/T/bfbM3nHdn8:13662:
Misplaced }.
/var/folders/_4/9mx5ryp52bb_z6drbcbrhwl40000gn/T/bfbM3nHdn8:13762:
Unknown command `geq'.
/var/folders/_4/9mx5ryp52bb_z6drbcbrhwl40000gn/T/bfbM3nHdn8:13762:
Misplaced {.
/var/folders/_4/9mx5ryp52bb_z6drbcbrhwl40000gn/T/bfbM3nHdn8:13762:
Misplaced }.
/var/folders/_4/9mx5ryp52bb_z6drbcbrhwl40000gn/T/bfbM3nHdn8:13815:
Unknown command `leq'.
/var/folders/_4/9mx5ryp52bb_z6drbcbrhwl40000gn/T/bfbM3nHdn8:13815:
Misplaced {.
/var/folders/_4/9mx5ryp52bb_z6drbcbrhwl40000gn/T/bfbM3nHdn8:13815:
Misplaced }.
...

Cheers,
Andrew

Reply | Threaded
Open this post in threaded view
|

Re: building on macOS?

bpabbott
Administrator
> On Nov 7, 2018, at 18:37, Andrew Janke <[hidden email]> wrote:
>
>
>> On 11/7/18 3:01 PM, Sebastian Schöps wrote:
>> Carlo de Falco-2 wrote
>>> $ hg bisect -g
>>> The first bad revision is:
>>> changeset:   25994:332be8be16eb
>>> user:        John W. Eaton &lt;
>>> jwe@
>>> &gt;
>>> date:        Fri Sep 28 18:18:09 2018 -0400
>>> summary:     dynamically load qt graphics
>>>
>>> can someone confirm that a00379f6f8c4 builds correctly while 332be8be16eb
>>> fails?
>> so far I can confirm that a00379f6f8c4 builds correctly.
>>
>> Sebastian
>>
> Building from the head of the repo on macOS 10.13.6 with Xcode 10 works OK for me: no crashes or errors during the build. Though I do get a bunch of error messages after the build finishes:
>
>
>   GEN      src/octave-cli-5.0.0
>   GEN      doc/interpreter/doc-cache
>
> Octave successfully built.  Now choose from the following:
>
>    ./run-octave    - to run in place to test before installing
>    make check      - to run the tests
>    make install    - to install (PREFIX=/tmp/test-octave)
>
>    HG ID for this build is "920a4ad8043b"
>
> /var/folders/_4/9mx5ryp52bb_z6drbcbrhwl40000gn/T/bfbM3nHdn8:112: Unknown command `codequoteundirected'.
> /var/folders/_4/9mx5ryp52bb_z6drbcbrhwl40000gn/T/bfbM3nHdn8:1411: Unknown command `leq'.
> /var/folders/_4/9mx5ryp52bb_z6drbcbrhwl40000gn/T/bfbM3nHdn8:1411: Misplaced {.
> /var/folders/_4/9mx5ryp52bb_z6drbcbrhwl40000gn/T/bfbM3nHdn8:1411: Misplaced }.
> /var/folders/_4/9mx5ryp52bb_z6drbcbrhwl40000gn/T/bfbM3nHdn8:7694: Unknown command `leq'.
> /var/folders/_4/9mx5ryp52bb_z6drbcbrhwl40000gn/T/bfbM3nHdn8:7694: Misplaced {.
> /var/folders/_4/9mx5ryp52bb_z6drbcbrhwl40000gn/T/bfbM3nHdn8:7694: Misplaced }.
> /var/folders/_4/9mx5ryp52bb_z6drbcbrhwl40000gn/T/bfbM3nHdn8:7694: Unknown command `leq'.
> /var/folders/_4/9mx5ryp52bb_z6drbcbrhwl40000gn/T/bfbM3nHdn8:7694: Misplaced {.
> /var/folders/_4/9mx5ryp52bb_z6drbcbrhwl40000gn/T/bfbM3nHdn8:7694: Misplaced }.
> /var/folders/_4/9mx5ryp52bb_z6drbcbrhwl40000gn/T/bfbM3nHdn8:13662: Unknown command `leq'.
> /var/folders/_4/9mx5ryp52bb_z6drbcbrhwl40000gn/T/bfbM3nHdn8:13662: Misplaced {.
> /var/folders/_4/9mx5ryp52bb_z6drbcbrhwl40000gn/T/bfbM3nHdn8:13662: Misplaced }.
> /var/folders/_4/9mx5ryp52bb_z6drbcbrhwl40000gn/T/bfbM3nHdn8:13762: Unknown command `geq'.
> /var/folders/_4/9mx5ryp52bb_z6drbcbrhwl40000gn/T/bfbM3nHdn8:13762: Misplaced {.
> /var/folders/_4/9mx5ryp52bb_z6drbcbrhwl40000gn/T/bfbM3nHdn8:13762: Misplaced }.
> /var/folders/_4/9mx5ryp52bb_z6drbcbrhwl40000gn/T/bfbM3nHdn8:13815: Unknown command `leq'.
> /var/folders/_4/9mx5ryp52bb_z6drbcbrhwl40000gn/T/bfbM3nHdn8:13815: Misplaced {.
> /var/folders/_4/9mx5ryp52bb_z6drbcbrhwl40000gn/T/bfbM3nHdn8:13815: Misplaced }.
> ...
>
> Cheers,
> Andrew
>

Hi Andrew,

If you “./run-octave”, plot a figure and quit, do you get a seg-fault?

Ben
Reply | Threaded
Open this post in threaded view
|

Re: building on macOS?

apjanke-floss


On 11/7/18 10:05 PM, Ben Abbott wrote:

>> On Nov 7, 2018, at 18:37, Andrew Janke <[hidden email]> wrote:
>>
>>
>>> On 11/7/18 3:01 PM, Sebastian Schöps wrote:
>>> Carlo de Falco-2 wrote
>>>> $ hg bisect -g
>>>> The first bad revision is:
>>>> changeset:   25994:332be8be16eb
>>>> user:        John W. Eaton &lt;
>>>> jwe@
>>>> &gt;
>>>> date:        Fri Sep 28 18:18:09 2018 -0400
>>>> summary:     dynamically load qt graphics
>>>>
>>>> can someone confirm that a00379f6f8c4 builds correctly while 332be8be16eb
>>>> fails?
>>> so far I can confirm that a00379f6f8c4 builds correctly.
>>>
>>> Sebastian
>>>
>> Building from the head of the repo on macOS 10.13.6 with Xcode 10 works OK for me: no crashes or errors during the build. Though I do get a bunch of error messages after the build finishes:
>>
>>
>>    GEN      src/octave-cli-5.0.0
>>    GEN      doc/interpreter/doc-cache
>>
>> Octave successfully built.  Now choose from the following:
>>
>>     ./run-octave    - to run in place to test before installing
>>     make check      - to run the tests
>>     make install    - to install (PREFIX=/tmp/test-octave)
>>
>>     HG ID for this build is "920a4ad8043b"
>>
>> /var/folders/_4/9mx5ryp52bb_z6drbcbrhwl40000gn/T/bfbM3nHdn8:112: Unknown command `codequoteundirected'.
>> /var/folders/_4/9mx5ryp52bb_z6drbcbrhwl40000gn/T/bfbM3nHdn8:1411: Unknown command `leq'.
>> /var/folders/_4/9mx5ryp52bb_z6drbcbrhwl40000gn/T/bfbM3nHdn8:1411: Misplaced {.
>> /var/folders/_4/9mx5ryp52bb_z6drbcbrhwl40000gn/T/bfbM3nHdn8:1411: Misplaced }.
>> /var/folders/_4/9mx5ryp52bb_z6drbcbrhwl40000gn/T/bfbM3nHdn8:7694: Unknown command `leq'.
>> /var/folders/_4/9mx5ryp52bb_z6drbcbrhwl40000gn/T/bfbM3nHdn8:7694: Misplaced {.
>> /var/folders/_4/9mx5ryp52bb_z6drbcbrhwl40000gn/T/bfbM3nHdn8:7694: Misplaced }.
>> /var/folders/_4/9mx5ryp52bb_z6drbcbrhwl40000gn/T/bfbM3nHdn8:7694: Unknown command `leq'.
>> /var/folders/_4/9mx5ryp52bb_z6drbcbrhwl40000gn/T/bfbM3nHdn8:7694: Misplaced {.
>> /var/folders/_4/9mx5ryp52bb_z6drbcbrhwl40000gn/T/bfbM3nHdn8:7694: Misplaced }.
>> /var/folders/_4/9mx5ryp52bb_z6drbcbrhwl40000gn/T/bfbM3nHdn8:13662: Unknown command `leq'.
>> /var/folders/_4/9mx5ryp52bb_z6drbcbrhwl40000gn/T/bfbM3nHdn8:13662: Misplaced {.
>> /var/folders/_4/9mx5ryp52bb_z6drbcbrhwl40000gn/T/bfbM3nHdn8:13662: Misplaced }.
>> /var/folders/_4/9mx5ryp52bb_z6drbcbrhwl40000gn/T/bfbM3nHdn8:13762: Unknown command `geq'.
>> /var/folders/_4/9mx5ryp52bb_z6drbcbrhwl40000gn/T/bfbM3nHdn8:13762: Misplaced {.
>> /var/folders/_4/9mx5ryp52bb_z6drbcbrhwl40000gn/T/bfbM3nHdn8:13762: Misplaced }.
>> /var/folders/_4/9mx5ryp52bb_z6drbcbrhwl40000gn/T/bfbM3nHdn8:13815: Unknown command `leq'.
>> /var/folders/_4/9mx5ryp52bb_z6drbcbrhwl40000gn/T/bfbM3nHdn8:13815: Misplaced {.
>> /var/folders/_4/9mx5ryp52bb_z6drbcbrhwl40000gn/T/bfbM3nHdn8:13815: Misplaced }.
>> ...
>>
>> Cheers,
>> Andrew
>>
> Hi Andrew,
>
> If you “./run-octave”, plot a figure and quit, do you get a seg-fault?
>
> Ben
Nevermind: my `configure` wasn't picking up my Qt correctly. When I
build it with Qt, I get the same segfault during the build process as
you folks.

Andrew

Reply | Threaded
Open this post in threaded view
|

Re: building on macOS?

bpabbott
Administrator
In reply to this post by bpabbott
> On Nov 6, 2018, at 3:54 PM, Ben Abbott <[hidden email]> wrote:
>
>> On Nov 6, 2018, at 15:38, John W. Eaton <[hidden email]> wrote:
>>
>> On 11/06/2018 05:12 PM, Carlo De Falco wrote:
>>>> On 6 Nov 2018, at 22:41, Sebastian Schöps <[hidden email]> wrote:
>>>>
>>>> Dmitri A. Sergatskov wrote
>>>>> Running "make V=1" -- finished building w/o problem.
>>>>> This is on Fedora 29.
>>>>
>>>> I have the same issue on macOS (default branch, with Gui) and "make V=1"
>>>> does not help here...
>>>> ...
>>>> /bin/sh run-octave --norc --silent --no-history --path
>>>> /private/tmp/octave-octave-app-20181106-78235-s9u83m/doc/interpreter/ --eval
>>>> "interpimages ('doc/interpreter/', 'interpn', 'txt');"
>>>> fatal: caught signal Segmentation fault: 11 -- stopping myself...
>>>>
>>>> Sebastian
>>> I completed the bisection search, this seems to be the first bad revision for me :
>>> $ hg bisect -g
>>> The first bad revision is:
>>> changeset:   25994:332be8be16eb
>>> user:        John W. Eaton <[hidden email]>
>>> date:        Fri Sep 28 18:18:09 2018 -0400
>>> summary:     dynamically load qt graphics
>>> can someone confirm that a00379f6f8c4 builds correctly while 332be8be16eb fails?
>>
>> Can someone also run the failing version under gdb or get a core file and run gdb on that and the octave-gui executable and see where the segfault happens?
>>
>> jwe
>
> Apple’s clang supports lldb. run-octave needs to be adjusted to use lldb.
>
> I was looking at this yesterday. I think all the needed translation info is at the link below.
>
> https://lldb.llvm.org/lldb-gdb.html
>
> Ben


The last working version is a00379f6f8c4 (fminsearch.m: Accept problem structure for Matlab compatibility).

Changesets 332be8be16eb thru 56ac36b5f7b0 are unable to build __init_qt__.la.

56ac36b5f7b0: eliminate unnecessary use of this-> in member function

        clang: error: linker command failed with exit code 1 (use -v to see invocation)
        make[2]: *** [libgui/graphics/__init_qt__.la] Error 1

Changeset 14e844f1459a fixes the __init_qt__.la build problem.

14e844f1459a: fix linking of __init_qt__.la on Windows systems (bug #54881)

After fixing this problem, when the qt toolkit is used, Octave seg-faults when exiting.

        fatal: caught signal Segmentation fault: 11 -- stopping myself...
        make[2]: *** [doc/interpreter/convhull.txt] Segmentation fault: 11
        make[2]: *** Deleting file `doc/interpreter/convhull.txt’

Speculation on my part, but this may be related to the problem with cleaning up qt before exiting.

        https://savannah.gnu.org/bugs/index.php?50025

Ben


Reply | Threaded
Open this post in threaded view
|

Re: building on macOS?

Carlo de Falco-2


Il giorno gio 8 nov 2018, 06:40 Ben Abbott <[hidden email]> ha scritto:

The last working version is a00379f6f8c4 (fminsearch.m: Accept problem structure for Matlab compatibility).

Changesets 332be8be16eb thru 56ac36b5f7b0 are unable to build __init_qt__.la.

56ac36b5f7b0: eliminate unnecessary use of this-> in member function

        clang: error: linker command failed with exit code 1 (use -v to see invocation)
        make[2]: *** [libgui/graphics/__init_qt__.la] Error 1

Changeset 14e844f1459a fixes the __init_qt__.la build problem.

14e844f1459a: fix linking of __init_qt__.la on Windows systems (bug #54881)

After fixing this problem, when the qt toolkit is used, Octave seg-faults when exiting.

        fatal: caught signal Segmentation fault: 11 -- stopping myself...
        make[2]: *** [doc/interpreter/convhull.txt] Segmentation fault: 11
        make[2]: *** Deleting file `doc/interpreter/convhull.txt’

Speculation on my part, but this may be related to the problem with cleaning up qt before exiting.

        https://savannah.gnu.org/bugs/index.php?50025

Ben

I can confirm all inservations reported by Ben so the issue is not related to the Mojave upgrade but it's a general problem for qt on the Mac.
c.
Reply | Threaded
Open this post in threaded view
|

Re: building on macOS?

bpabbott
Administrator
On Nov 7, 2018, at 11:36 PM, Carlo de Falco <[hidden email]> wrote:

Il giorno gio 8 nov 2018, 06:40 Ben Abbott <[hidden email]> ha scritto:

The last working version is a00379f6f8c4 (fminsearch.m: Accept problem structure for Matlab compatibility).

Changesets 332be8be16eb thru 56ac36b5f7b0 are unable to build __init_qt__.la.

56ac36b5f7b0: eliminate unnecessary use of this-> in member function

        clang: error: linker command failed with exit code 1 (use -v to see invocation)
        make[2]: *** [libgui/graphics/__init_qt__.la] Error 1

Changeset 14e844f1459a fixes the __init_qt__.la build problem.

14e844f1459a: fix linking of __init_qt__.la on Windows systems (bug #54881)

After fixing this problem, when the qt toolkit is used, Octave seg-faults when exiting.

        fatal: caught signal Segmentation fault: 11 -- stopping myself...
        make[2]: *** [doc/interpreter/convhull.txt] Segmentation fault: 11
        make[2]: *** Deleting file `doc/interpreter/convhull.txt’

Speculation on my part, but this may be related to the problem with cleaning up qt before exiting.

        https://savannah.gnu.org/bugs/index.php?50025

Ben

I can confirm all inservations reported by Ben so the issue is not related to the Mojave upgrade but it's a general problem for qt on the Mac.
c.

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 “…”.

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');”

Ben



octave-gui.log (80K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: building on macOS?

John W. Eaton
Administrator
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.

jwe

Reply | Threaded
Open this post in threaded view
|

Re: building on macOS?

Carlo de Falco-2


Il giorno mar 13 nov 2018, 09:20 John W. Eaton <[hidden email]> ha scritto:
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)? 

For me that does work but then, when I exit Octave I get the segfault. 

The qt toolkit should still be registered and should work
as long as you are not using the -cli option for run-octave.

jwe

c.
Reply | Threaded
Open this post in threaded view
|

Re: building on macOS?

Sebastian Schöps
Carlo de Falco-2 wrote
> For me that does work but then, when I exit Octave I get the segfault.

When using the gui interactively the freeze on exit can be fixed by the
patch from  https://savannah.gnu.org/bugs/?50025. However, recently, i.e.
after a00379f6f8c4, using 'eval' as for the docs causes a crash.

Sebastian




--
Sent from: http://octave.1599824.n4.nabble.com/Octave-Maintainers-f1638794.html

Reply | Threaded
Open this post in threaded view
|

Re: building on macOS?

bpabbott
Administrator
In reply to this post by Carlo de Falco-2
On Nov 13, 2018, at 12:32 AM, Carlo de Falco <[hidden email]> wrote:

Il giorno mar 13 nov 2018, 09:20 John W. Eaton <[hidden email]> ha scritto:
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)? 

For me that does work but then, when I exit Octave I get the segfault. 

The qt toolkit should still be registered and should work
as long as you are not using the -cli option for run-octave.

jwe

c.

Being a big more methodical this time. I have a shell script file …

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

This seg-faults. I’ve tried to run the gui manually (i.e. no —path or —eval options). Something changed for the gui. Readline looks to be not working and fputs is throwing errors. I’ll look into these first.

Ben
Reply | Threaded
Open this post in threaded view
|

Re: building on macOS?

bpabbott
Administrator
On Nov 13, 2018, at 7:24 AM, Ben Abbott <[hidden email]> wrote:

On Nov 13, 2018, at 12:32 AM, Carlo de Falco <[hidden email]> wrote:

Il giorno mar 13 nov 2018, 09:20 John W. Eaton <[hidden email]> ha scritto:
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)? 

For me that does work but then, when I exit Octave I get the segfault. 

The qt toolkit should still be registered and should work
as long as you are not using the -cli option for run-octave.

jwe

c.

Being a big more methodical this time. I have a shell script file …

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

This seg-faults. I’ve tried to run the gui manually (i.e. no —path or —eval options). Something changed for the gui. Readline looks to be not working and fputs is throwing errors. I’ll look into these first.

Ben

The readline trouble went away after I pull, update, make.

Running gui, then plotting, and existing produces the seg-fault.

I must have made a mistake earlier.

Ben
Reply | Threaded
Open this post in threaded view
|

Re: building on macOS?

Carlo de Falco-2


> On 13 Nov 2018, at 16:34, Ben Abbott <[hidden email]> wrote:
>
> The readline trouble went away after I pull, update, make.
>
> Running gui, then plotting, and existing produces the seg-fault.
>
> I must have made a mistake earlier.
>
> Ben


I just built b2a96efc88eb+ if I run Octave from the command line without the --gui option,
the following causes a crash :

$ ./run-octave
>> plot (randn(3))
>> exit
fatal: caught signal Segmentation fault: 11 -- stopping myself...
Segmentation fault: 11

while this doesn't :

$ ./run-octave
>> plot (randn(3))
>> close
>> exit

and indeed, with the attached patch applied the build works without errors for me.
notice that the "pause (.1)" seems to be required to completely avoid the crash.

c.


open_kEClIYyW.txt (864 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: building on macOS?

bpabbott
Administrator
> On Nov 13, 2018, at 9:17 AM, Carlo De Falco <[hidden email]> wrote:
>
>
>> On 13 Nov 2018, at 16:34, Ben Abbott <[hidden email]> wrote:
>>
>> The readline trouble went away after I pull, update, make.
>>
>> Running gui, then plotting, and existing produces the seg-fault.
>>
>> I must have made a mistake earlier.
>>
>> Ben
>
>
> I just built b2a96efc88eb+ if I run Octave from the command line without the --gui option,
> the following causes a crash :
>
> $ ./run-octave
>>> plot (randn(3))
>>> exit
> fatal: caught signal Segmentation fault: 11 -- stopping myself...
> Segmentation fault: 11
>
> while this doesn't :
>
> $ ./run-octave
>>> plot (randn(3))
>>> close
>>> exit
>
> and indeed, with the attached patch applied the build works without errors for me.
> notice that the "pause (.1)" seems to be required to completely avoid the crash.
>
> c.
>
> <open_kEClIYyW.txt>

Carlo,

The patch worked for me. I tried replacing “pause (0.1)” with “drawnow ()”, but that didn’t work.

Ben
Reply | Threaded
Open this post in threaded view
|

Re: building on macOS?

Pantxo
bpabbott wrote
>> On Nov 13, 2018, at 9:17 AM, Carlo De Falco &lt;

> carlo.defalco@

> &gt; wrote:
>>
>>
>>> On 13 Nov 2018, at 16:34, Ben Abbott &lt;

> bpabbott@

> &gt; wrote:
>>>
>>> The readline trouble went away after I pull, update, make.
>>>
>>> Running gui, then plotting, and existing produces the seg-fault.
>>>
>>> I must have made a mistake earlier.
>>>
>>> Ben
>>
>>
>> I just built b2a96efc88eb+ if I run Octave from the command line without
>> the --gui option,
>> the following causes a crash :
>>
>> $ ./run-octave
>>>> plot (randn(3))
>>>> exit
>> fatal: caught signal Segmentation fault: 11 -- stopping myself...
>> Segmentation fault: 11
>>
>> while this doesn't :
>>
>> $ ./run-octave
>>>> plot (randn(3))
>>>> close
>>>> exit
>>
>> and indeed, with the attached patch applied the build works without
>> errors for me.
>> notice that the "pause (.1)" seems to be required to completely avoid the
>> crash.
>>
>> c.
>>
>>
> <open_kEClIYyW.txt>
> Carlo,
>
> The patch worked for me. I tried replacing “pause (0.1)” with “drawnow
> ()”, but that didn’t work.
>
> Ben

Hi,

Did anyone post a bug report about this build failure? I am wondering if the
preliminary patch for bug #55226
(https://savannah.gnu.org/bugs/index.php?55226) could help. Can someone try
it out?

Pantxo



--
Sent from: http://octave.1599824.n4.nabble.com/Octave-Maintainers-f1638794.html

Reply | Threaded
Open this post in threaded view
|

Re: building on macOS?

bpabbott
Administrator
> On Dec 18, 2018, at 23:43, Pantxo <[hidden email]> wrote:
>
> bpabbott wrote
>>> On Nov 13, 2018, at 9:17 AM, Carlo De Falco &lt;
>
>> carlo.defalco@
>
>> &gt; wrote:
>>>
>>>
>>>> On 13 Nov 2018, at 16:34, Ben Abbott &lt;
>
>> bpabbott@
>
>> &gt; wrote:
>>>>
>>>> The readline trouble went away after I pull, update, make.
>>>>
>>>> Running gui, then plotting, and existing produces the seg-fault.
>>>>
>>>> I must have made a mistake earlier.
>>>>
>>>> Ben
>>>
>>>
>>> I just built b2a96efc88eb+ if I run Octave from the command line without
>>> the --gui option,
>>> the following causes a crash :
>>>
>>> $ ./run-octave
>>>>> plot (randn(3))
>>>>> exit
>>> fatal: caught signal Segmentation fault: 11 -- stopping myself...
>>> Segmentation fault: 11
>>>
>>> while this doesn't :
>>>
>>> $ ./run-octave
>>>>> plot (randn(3))
>>>>> close
>>>>> exit
>>>
>>> and indeed, with the attached patch applied the build works without
>>> errors for me.
>>> notice that the "pause (.1)" seems to be required to completely avoid the
>>> crash.
>>>
>>> c.
>>>
>>>
>> <open_kEClIYyW.txt>
>> Carlo,
>>
>> The patch worked for me. I tried replacing “pause (0.1)” with “drawnow
>> ()”, but that didn’t work.
>>
>> Ben
>
> Hi,
>
> Did anyone post a bug report about this build failure? I am wondering if the
> preliminary patch for bug #55226
> (https://savannah.gnu.org/bugs/index.php?55226) could help. Can someone try
> it out?
>
> Pantxo

Hi Pantxo

I have not filed a bug report.

When I have time, I’ll take a look at the patch you’ve suggested and follow up.

Ben

Reply | Threaded
Open this post in threaded view
|

Re: building on macOS?

bpabbott
Administrator
> On Dec 19, 2018, at 8:36 AM, Ben Abbott <[hidden email]> wrote:
>
>> On Dec 18, 2018, at 23:43, Pantxo <[hidden email]> wrote:
>>
>> bpabbott wrote
>>>> On Nov 13, 2018, at 9:17 AM, Carlo De Falco &lt;
>>
>>> carlo.defalco@
>>
>>> &gt; wrote:
>>>>
>>>>
>>>>> On 13 Nov 2018, at 16:34, Ben Abbott &lt;
>>
>>> bpabbott@
>>
>>> &gt; wrote:
>>>>>
>>>>> The readline trouble went away after I pull, update, make.
>>>>>
>>>>> Running gui, then plotting, and existing produces the seg-fault.
>>>>>
>>>>> I must have made a mistake earlier.
>>>>>
>>>>> Ben
>>>>
>>>>
>>>> I just built b2a96efc88eb+ if I run Octave from the command line without
>>>> the --gui option,
>>>> the following causes a crash :
>>>>
>>>> $ ./run-octave
>>>>>> plot (randn(3))
>>>>>> exit
>>>> fatal: caught signal Segmentation fault: 11 -- stopping myself...
>>>> Segmentation fault: 11
>>>>
>>>> while this doesn't :
>>>>
>>>> $ ./run-octave
>>>>>> plot (randn(3))
>>>>>> close
>>>>>> exit
>>>>
>>>> and indeed, with the attached patch applied the build works without
>>>> errors for me.
>>>> notice that the "pause (.1)" seems to be required to completely avoid the
>>>> crash.
>>>>
>>>> c.
>>>>
>>>>
>>> <open_kEClIYyW.txt>
>>> Carlo,
>>>
>>> The patch worked for me. I tried replacing “pause (0.1)” with “drawnow
>>> ()”, but that didn’t work.
>>>
>>> Ben
>>
>> Hi,
>>
>> Did anyone post a bug report about this build failure? I am wondering if the
>> preliminary patch for bug #55226
>> (https://savannah.gnu.org/bugs/index.php?55226) could help. Can someone try
>> it out?
>>
>> Pantxo
>
> Hi Pantxo
>
> I have not filed a bug report.
>
> When I have time, I’ll take a look at the patch you’ve suggested and follow up.
>
> Ben

Hi Pantxo,

The patch for bug #55226 didn’t help with this.

Ben


Reply | Threaded
Open this post in threaded view
|

Re: building on macOS?

Carlo de Falco-2


> On 19 Dec 2018, at 14:56, Ben Abbott <[hidden email]> wrote:
>>
> Hi Pantxo,
>
> The patch for bug #55226 didn’t help with this.
>
> Ben

Hi Ben,

As you tested this I assume you managed to build a recent development release on macos?
Can you also confirm whether or not bug #55033 ( https://savannah.gnu.org/bugs/?55033 )still exists?

Thanks,
c.


Reply | Threaded
Open this post in threaded view
|

Re: building on macOS?

bpabbott
Administrator
> On Dec 19, 2018, at 10:59 PM, Carlo De Falco <[hidden email]> wrote:
>
>> On 19 Dec 2018, at 14:56, Ben Abbott <[hidden email]> wrote:
>>>
>> Hi Pantxo,
>>
>> The patch for bug #55226 didn’t help with this.
>>
>> Ben
>
> Hi Ben,
>
> As you tested this I assume you managed to build a recent development release on macos?
> Can you also confirm whether or not bug #55033 ( https://savannah.gnu.org/bugs/?55033 )still exists?
>
> Thanks,
> c.

Hi Carlo,

I assume it is still necessary to install Octave in order to build oct-files? I typically only install using homebrew.

Sebastian / Andrew,

Do you have a port that I can tap which will build using the latest sources?

Ben


Reply | Threaded
Open this post in threaded view
|

Re: building on macOS?

Carlo de Falco-2


> On 20 Dec 2018, at 12:36, Ben Abbott <[hidden email]> wrote:
>
> Hi Carlo,
>
> I assume it is still necessary to install Octave in order to build oct-files? I typically only install using homebrew.
>
> Sebastian / Andrew,
>
> Do you have a port that I can tap which will build using the latest sources?
>
> Ben

Yes, I think you need to install to test this ...
But you could also just share the file src/mkoctfile.cc from your build directory as the wrong flags are set in there for me.

c.




123