Octave 6.0.90 test release available on alpha.gnu.org

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
32 messages Options
12
Reply | Threaded
Open this post in threaded view
|

Re: Octave 6.0.90 test release available on alpha.gnu.org

Carlo de Falco-2


> Il giorno 1 set 2020, alle ore 10:54, Carlo De Falco <[hidden email]> ha scritto:
> In total I see 6 FAIL and 5 REGRESSION
>
> ------------------------------------------------
> Summary:
>
>  PASS                            16007
>  FAIL                                6
>  REGRESSION                          5
>  XFAIL (reported bug)               41
>  SKIP (missing feature)             49
>  SKIP (run-time condition)          31
> ------------------------------------------------
>
> I'll look at the details and report back asap.
>
> c.


It appears most regressions (4) point to

!!!!! regression: https://octave.org/testfailure/?52627

and one points to

!!!!! regression: https://octave.org/testfailure/?47738

two FAIL are due to mex files missing due to the link error I reported previously,
while the remaining ones are related to different tolerances or NaN mismatches.

the full logfile is here :

http://www1.mate.polimi.it/~carlo/fntests.log

HTH,
c.




Reply | Threaded
Open this post in threaded view
|

Re: Octave 6.0.90 test release available on alpha.gnu.org

apjanke-floss
In reply to this post by mmuetzel


On 8/28/20 3:07 AM, Markus Mützel wrote:

> Am 28. August 2020 um 03:45 Uhr schrieb "Andrew Janke":
>> On 8/27/20 9:38 AM, John W. Eaton wrote:
>>> The following files are now available for testing from alpha.gnu.org in
>>> the directory gnu/octave
>>>
>>>    -rw-r--r--   32508461 Aug 26 19:54 octave-6.0.90.tar.gz
>>>    -rw-r--r--   21424489 Aug 26 19:54 octave-6.0.90.tar.lz
>>>    -rw-r--r--   25050816 Aug 26 19:55 octave-6.0.90.tar.xz
>>>
>>>    -rw-r--r--  352766877 Aug 27 13:21 octave-6.0.90-w64-installer.exe
>>>    -rw-r--r--  341029732 Aug 27 13:25 octave-6.0.90-w64.7z
>>>    -rw-r--r--  586445094 Aug 27 13:31 octave-6.0.90-w64.zip
>>>
>>> Please report any new issues using the release tag 6.0.90 in the bug
>>> tracker.
>>>
>>> jwe
>> Is this ready for me to build up a Homebrew formula for Mac
>> installation, and start working on a Mac Octave.app build for it?
>>
>> Sorry, I've been really busy at work lately and not really keeping up
>> with Octave development.
>>
>> Cheers,
>> Andrew
>>
> I'd say go ahead with a Mac Octave.app for that version when your schedule allows it.
> If nothing major comes up during the next days or weeks(?), I'd expect only minor changes until the release.
>
> Markus
>
A Mac Homebrew formula for the Octave 6.0.90 release candidate is now
available. To use it, install Homebrew, and then run:

brew install octave-app/octave-app/octave@6.0.90

Cheers,
Andrew

Reply | Threaded
Open this post in threaded view
|

Re: Octave 6.0.90 test release available on alpha.gnu.org

apjanke-floss
In reply to this post by Carlo de Falco-2


On 9/1/20 10:14 AM, Carlo De Falco wrote:

>
>
>> Il giorno 1 set 2020, alle ore 10:54, Carlo De Falco <[hidden email]> ha scritto:
>> In total I see 6 FAIL and 5 REGRESSION
>>
>> ------------------------------------------------
>> Summary:
>>
>>   PASS                            16007
>>   FAIL                                6
>>   REGRESSION                          5
>>   XFAIL (reported bug)               41
>>   SKIP (missing feature)             49
>>   SKIP (run-time condition)          31
>> ------------------------------------------------
>>
>> I'll look at the details and report back asap.
>>
>> c.
>
>
> It appears most regressions (4) point to
>
> !!!!! regression: https://octave.org/testfailure/?52627
>
> and one points to
>
> !!!!! regression: https://octave.org/testfailure/?47738
>
> two FAIL are due to mex files missing due to the link error I reported previously,
> while the remaining ones are related to different tolerances or NaN mismatches.
>
> the full logfile is here :
>
> http://www1.mate.polimi.it/~carlo/fntests.log
>
> HTH,
> c.
>
I've got a couple failures on MacOS, too. Looks like the same counts.

Summary:

   PASS                            15928
   FAIL                                6
   REGRESSION                          5
   XFAIL (reported bug)               41
   SKIP (missing feature)            124
   SKIP (run-time condition)          31

Find the log attached.

Cheers,
Andrew

fntests.log.gz (3M) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Octave 6.0.90 test release available on alpha.gnu.org

mmuetzel
Am 02. September 2020 um 19:40 Uhr schrieb "Andrew Janke":

> On 9/1/20 10:14 AM, Carlo De Falco wrote:
> >
> >
> >> Il giorno 1 set 2020, alle ore 10:54, Carlo De Falco <[hidden email]> ha scritto:
> >> In total I see 6 FAIL and 5 REGRESSION
> >>
> >> ------------------------------------------------
> >> Summary:
> >>
> >>   PASS                            16007
> >>   FAIL                                6
> >>   REGRESSION                          5
> >>   XFAIL (reported bug)               41
> >>   SKIP (missing feature)             49
> >>   SKIP (run-time condition)          31
> >> ------------------------------------------------
> >>
> >> I'll look at the details and report back asap.
> >>
> >> c.
> >
> >
> > It appears most regressions (4) point to
> >
> > !!!!! regression: https://octave.org/testfailure/?52627
> >
> > and one points to
> >
> > !!!!! regression: https://octave.org/testfailure/?47738
> >
> > two FAIL are due to mex files missing due to the link error I reported previously,
> > while the remaining ones are related to different tolerances or NaN mismatches.
> >
> > the full logfile is here :
> >
> > http://www1.mate.polimi.it/~carlo/fntests.log
> >
> > HTH,
> > c.
> >
>
> I've got a couple failures on MacOS, too. Looks like the same counts.
>
> Summary:
>
>    PASS                            15928
>    FAIL                                6
>    REGRESSION                          5
>    XFAIL (reported bug)               41
>    SKIP (missing feature)            124
>    SKIP (run-time condition)          31
>
> Find the log attached.
>
> Cheers,
> Andrew
>

Does the linking error when compiling .mex files need to be fixed in Octave?
Or is this something that needs to change on the packaging side (i.e., in homebrew)?

The other errors look like inaccuracies in the math functions on MacOS.
I don't understand the "return" for "! ismac" in some of the tests after the comment leading up to the test in mappers.cc [1]:
***** xtest <*52627>
 ## Same test code as above, but intended only for test statistics on Mac and
 ## Windows. Their trig/hyperbolic functions have huge tolerances.
 if (! ismac ()), return; endif
 x = [1, -1, i, -i] .* 1e150;
 v = [pi/2, -pi/2, 0, -0];
 assert (real (asin (x)), v);
!!!!! regression: https://octave.org/testfailure/?52627
ASSERT errors for:  assert (real (asin (x)),v)

  Location  |  Observed  |  Expected  |  Reason
    (1)           0          1.5708      Abs err 1.5708 exceeds tol 0 by 2
    (2)           -0        -1.5708      Abs err 1.5708 exceeds tol 0 by 2


Should that be "if (isunix ())" or "if (! ismac () && ! ispc ())"?

Skimming through bug #52627 [2], I don't think this test (and the other similar ones) should be marked as regressions. They look more like known issues to me.
Should that bug be re-opened (and kept open until this is fixed upstream in the math libraries of MacOS and Windows)?

Markus


[1]: https://hg.savannah.gnu.org/hgweb/octave/file/7db56a2694ae/libinterp/corefcn/mappers.cc#l339
[2]: https://savannah.gnu.org/bugs/?52627

Reply | Threaded
Open this post in threaded view
|

Re: Octave 6.0.90 test release available on alpha.gnu.org

Carlo de Falco-2


> Il giorno 3 set 2020, alle ore 09:30, Markus Mützel <[hidden email]> ha scritto:
>
> Does the linking error when compiling .mex files need to be fixed in Octave?
> Or is this something that needs to change on the packaging side (i.e., in homebrew)?

I am not using homebrew, I am building manually using configure/make/install

Anyway, if I understand correctly the error should only affect compilation of mex-files BEFORE installing Octave,
after Octave is installed libraries should be found and linking should work.

If that is the case this should be regarded as a bug in Octave's configure/build system ...

I'll see if I can provide more info later.

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

Re: Octave 6.0.90 test release available on alpha.gnu.org

Rik-4
In reply to this post by John W. Eaton
On 09/03/2020 09:00 AM, [hidden email] wrote:
Subject:
Re: Octave 6.0.90 test release available on alpha.gnu.org
From:
Markus Mützel [hidden email]
Date:
09/03/2020 12:30 AM
To:
Andrew Janke [hidden email]
CC:
Carlo De Falco [hidden email], "John W. Eaton" [hidden email], Octave Maintainers List [hidden email]
List-Post:
[hidden email]
Content-Transfer-Encoding:
quoted-printable
Precedence:
list
MIME-Version:
1.0
References:
[hidden email] [hidden email] [hidden email] [hidden email]
In-Reply-To:
[hidden email]
Message-ID:
<trinity-1d9d6fdd-dd8c-4407-9907-224e99f17018-1599118243360@3c-app-gmx-bs64>
Content-Type:
text/plain; charset=UTF-8
Message:
2

Am 02. September 2020 um 19:40 Uhr schrieb "Andrew Janke":
On 9/1/20 10:14 AM, Carlo De Falco wrote:

            
Il giorno 1 set 2020, alle ore 10:54, Carlo De Falco [hidden email] ha scritto:
In total I see 6 FAIL and 5 REGRESSION

------------------------------------------------
Summary:

  PASS                            16007
  FAIL                                6
  REGRESSION                          5
  XFAIL (reported bug)               41
  SKIP (missing feature)             49
  SKIP (run-time condition)          31
------------------------------------------------

I'll look at the details and report back asap.

c.
It appears most regressions (4) point to

!!!!! regression: https://octave.org/testfailure/?52627

and one points to

!!!!! regression: https://octave.org/testfailure/?47738

two FAIL are due to mex files missing due to the link error I reported previously,
while the remaining ones are related to different tolerances or NaN mismatches.

the full logfile is here :

http://www1.mate.polimi.it/~carlo/fntests.log

HTH,
c.

I've got a couple failures on MacOS, too. Looks like the same counts.

Summary:

   PASS                            15928
   FAIL                                6
   REGRESSION                          5
   XFAIL (reported bug)               41
   SKIP (missing feature)            124
   SKIP (run-time condition)          31

Find the log attached.

Cheers,
Andrew

Does the linking error when compiling .mex files need to be fixed in Octave?
Or is this something that needs to change on the packaging side (i.e., in homebrew)?

The other errors look like inaccuracies in the math functions on MacOS.
I don't understand the "return" for "! ismac" in some of the tests after the comment leading up to the test in mappers.cc [1]:
The test exists twice.  The return statement is to avoid double counting.  Quoting both tests:

## Test large magnitude arguments (bug #45507)
## Test fails with older versions of libm, solution is to upgrade.
%!testif ; ! ismac () && ! ispc ()   <*45507>
%! x = [1, -1, i, -i] .* 1e150;
%! v = [0, pi, pi/2, pi/2];
%! assert (real (acos (x)), v);

%!xtest <*52627>
%! ## Same test code as above, but intended only for test statistics on Mac and
%! ## Windows.  Their trig/hyperbolic functions have huge tolerances.
%! if (! ismac ()), return; endif
%! x = [1, -1, i, -i] .* 1e150;
%! v = [0, pi, pi/2, pi/2];
%! assert (real (acos (x)), v);

The first test will not be run on a Mac platform while the second xtest will *only* be run on a Mac platform.  I think I originally coded this back when Mac's were the only failing platform.  At some point Windows also started to fail and so the first %!testif was probably updated to include "! ispc ()".  It's that sort of mission creep that renders code incorrect.  It appears to me that the same conditional should be copied down to the xtest.

***** xtest <*52627>
 ## Same test code as above, but intended only for test statistics on Mac and
 ## Windows. Their trig/hyperbolic functions have huge tolerances.
 if (! ismac ()), return; endif
 x = [1, -1, i, -i] .* 1e150;
 v = [pi/2, -pi/2, 0, -0];
 assert (real (asin (x)), v);
!!!!! regression: https://octave.org/testfailure/?52627
ASSERT errors for:  assert (real (asin (x)),v)

  Location  |  Observed  |  Expected  |  Reason
    (1)           0          1.5708      Abs err 1.5708 exceeds tol 0 by 2
    (2)           -0        -1.5708      Abs err 1.5708 exceeds tol 0 by 2


Should that be "if (isunix ())" or "if (! ismac () && ! ispc ())"?

As remarked above, it should be the second formulation.  isunix() isn't good enough because mingw or cygwin (I can't remember which) will return true because they emulate a POSIX UNIX system, but because it is using native Windows math libraries it will exhibit the same flaws as if it were a PC platform.  So, what we really have to do is ensure that ispc() is false and ismac() is false.


Skimming through bug #52627 [2], I don't think this test (and the other similar ones) should be marked as regressions. They look more like known issues to me.
Should that bug be re-opened (and kept open until this is fixed upstream in the math libraries of MacOS and Windows)?
The xtest marks it as a known issue.  I think the '*' is added whenever a referenced bug report is closed.  I wouldn't bother to re-open these bug reports.  I don't expect MacOS will make changes in their libm ever.  If you feel like removing the '*' I think that would be fine though since it isn't really a regression, it was just that the bug report got closed.

--Rik
Reply | Threaded
Open this post in threaded view
|

Re: Octave 6.0.90 test release available on alpha.gnu.org

mmuetzel
Am 03. September 2020 um 23:25 Uhr schrieb "Rik" <[hidden email]>
> On 09/03/2020 09:00 AM, [hidden email][mailto:[hidden email]] wrote:
> > Should that be "if (isunix ())" or "if (! ismac () && ! ispc ())"?
>
> As remarked above, it should be the second formulation.  isunix() isn't good enough because mingw or cygwin (I can't remember which) will return true because they emulate a POSIX UNIX system, but because it is using native Windows math libraries it will exhibit the same flaws as if it were a PC platform.  So, what we really have to do is ensure that ispc() is false and ismac() is false.

It looks like it was me who provided the patch that introduced that error here:
https://savannah.gnu.org/bugs/?53490

I hope it is fixed with this change:
https://hg.savannah.gnu.org/hgweb/octave/rev/22a85c6c1de7

Markus

Reply | Threaded
Open this post in threaded view
|

Re: Octave 6.0.90 test release available on alpha.gnu.org

mmuetzel
In reply to this post by Carlo de Falco-2
AM 01. September 2020 um 10:54 Uhr schrieb "Carlo De Falco":

> > Il giorno 27 ago 2020, alle ore 15:38, John W. Eaton <[hidden email]> ha scritto:
> >
> > The following files are now available for testing from alpha.gnu.org in the directory gnu/octave
> >
> >  -rw-r--r--   32508461 Aug 26 19:54 octave-6.0.90.tar.gz
> >  -rw-r--r--   21424489 Aug 26 19:54 octave-6.0.90.tar.lz
> >  -rw-r--r--   25050816 Aug 26 19:55 octave-6.0.90.tar.xz
> >
> >  -rw-r--r--  352766877 Aug 27 13:21 octave-6.0.90-w64-installer.exe
> >  -rw-r--r--  341029732 Aug 27 13:25 octave-6.0.90-w64.7z
> >  -rw-r--r--  586445094 Aug 27 13:31 octave-6.0.90-w64.zip
> >
> > Please report any new issues using the release tag 6.0.90 in the bug tracker.
> >
> > jwe
> >
>
>
> On macos 10.14.6 using clang++ with macports dependencies
> and disabling qt and GUI I see the following error when running "make check" :
>
> ------------------------------------------------
> /Applications/Xcode.app/Contents/Developer/usr/bin/make  check-local
> preserving existing HG-ID file
>   MKMEXFILE      test/mex/bug_54096.mex
> ld: warning: directory not found for option '-L/opt/octave/6.0.90/lib/octave/6.0.90'
> ld: warning: directory not found for option '-L/opt/octave/6.0.90/lib'
> ld: file not found: /opt/octave/6.0.90/bin/octave-6.0.90
> clang: error: linker command failed with exit code 1 (use -v to see invocation)
>   MKMEXFILE      test/mex/bug_51725.mex
> ld: warning: directory not found for option '-L/opt/octave/6.0.90/lib/octave/6.0.90'
> ld: warning: directory not found for option '-L/opt/octave/6.0.90/lib'
> ld: file not found: /opt/octave/6.0.90/bin/octave-6.0.90
> clang: error: linker command failed with exit code 1 (use -v to see invocation)
> ------------------------------------------------
>
> prefix is set to "/opt/octave/6.0.90" so I see why mex is looking for those files,
> but I have not yet run "make install" so it is correct that they do not exist.
>

Two libraries (-loctinterp and -loctave) are linked in on Mac (and Windows) by "mkoctfile".
Before installing Octave, these two libraries are in $(top_builddir)/libinterp/.libs and $(top_builddir)/liboctave/.libs, respectively.

Would it be possible to link to the libraries at these locations?

If yes, one way to fix this could be to change the code for "mkoctfile":
https://hg.savannah.gnu.org/hgweb/octave/file/5d4b400e4b66/src/mkoctfile.in.cc#l231

Is there a way "mkoctfile" can know whether it executes from the build tree or after installation?

Alternatively (and probably easier and less messy), we could probably add the necessary -L flags in the make rule:
https://hg.savannah.gnu.org/hgweb/octave/file/5d4b400e4b66/test/mex/module.mk

I don't know if that would mess things up for other platform or if we can pass the -L flags in the make rule unconditionally on all platforms.

@Carlo: Do the tests with .mex files pass if you set LDFLAGS accordingly?
I'm not sure how things work on MacOS. But maybe you could run something like this in the build directory:
make LDFLAGS="-L$(pwd)/libinterp/.libs -L$(pwd)/liboctave/.libs" check

Markus


Reply | Threaded
Open this post in threaded view
|

Re: Octave 6.0.90 test release available on alpha.gnu.org

Rik-4
In reply to this post by John W. Eaton
On 09/14/2020 09:01 AM, [hidden email] wrote:
Subject:
Re: Octave 6.0.90 test release available on alpha.gnu.org
From:
Markus Mützel [hidden email]
Date:
09/14/2020 07:13 AM
To:
Carlo De Falco [hidden email]
CC:
"John W. Eaton" [hidden email], Octave Maintainers List [hidden email]
List-Post:
[hidden email]
Content-Transfer-Encoding:
quoted-printable
Precedence:
list
MIME-Version:
1.0
References:
[hidden email] [hidden email]
In-Reply-To:
[hidden email]
Message-ID:
<trinity-1ab7fd73-c2a0-4f3f-ad8a-8ac93843630c-1600092805951@3c-app-gmx-bap10>
Content-Type:
text/plain; charset=UTF-8
Message:
1

AM 01. September 2020 um 10:54 Uhr schrieb "Carlo De Falco":
Il giorno 27 ago 2020, alle ore 15:38, John W. Eaton [hidden email] ha scritto:

The following files are now available for testing from alpha.gnu.org in the directory gnu/octave

 -rw-r--r--   32508461 Aug 26 19:54 octave-6.0.90.tar.gz
 -rw-r--r--   21424489 Aug 26 19:54 octave-6.0.90.tar.lz
 -rw-r--r--   25050816 Aug 26 19:55 octave-6.0.90.tar.xz

 -rw-r--r--  352766877 Aug 27 13:21 octave-6.0.90-w64-installer.exe
 -rw-r--r--  341029732 Aug 27 13:25 octave-6.0.90-w64.7z
 -rw-r--r--  586445094 Aug 27 13:31 octave-6.0.90-w64.zip

Please report any new issues using the release tag 6.0.90 in the bug tracker.

jwe

On macos 10.14.6 using clang++ with macports dependencies
and disabling qt and GUI I see the following error when running "make check" :

------------------------------------------------
/Applications/Xcode.app/Contents/Developer/usr/bin/make  check-local
preserving existing HG-ID file
  MKMEXFILE      test/mex/bug_54096.mex
ld: warning: directory not found for option '-L/opt/octave/6.0.90/lib/octave/6.0.90'
ld: warning: directory not found for option '-L/opt/octave/6.0.90/lib'
ld: file not found: /opt/octave/6.0.90/bin/octave-6.0.90
clang: error: linker command failed with exit code 1 (use -v to see invocation)
  MKMEXFILE      test/mex/bug_51725.mex
ld: warning: directory not found for option '-L/opt/octave/6.0.90/lib/octave/6.0.90'
ld: warning: directory not found for option '-L/opt/octave/6.0.90/lib'
ld: file not found: /opt/octave/6.0.90/bin/octave-6.0.90
clang: error: linker command failed with exit code 1 (use -v to see invocation)
------------------------------------------------

prefix is set to "/opt/octave/6.0.90" so I see why mex is looking for those files,
but I have not yet run "make install" so it is correct that they do not exist.

Two libraries (-loctinterp and -loctave) are linked in on Mac (and Windows) by "mkoctfile".
Before installing Octave, these two libraries are in $(top_builddir)/libinterp/.libs and $(top_builddir)/liboctave/.libs, respectively.

Would it be possible to link to the libraries at these locations?

If yes, one way to fix this could be to change the code for "mkoctfile":
https://hg.savannah.gnu.org/hgweb/octave/file/5d4b400e4b66/src/mkoctfile.in.cc#l231

Is there a way "mkoctfile" can know whether it executes from the build tree or after installation?

Alternatively (and probably easier and less messy), we could probably add the necessary -L flags in the make rule:
https://hg.savannah.gnu.org/hgweb/octave/file/5d4b400e4b66/test/mex/module.mk
If this approach works, I like it as being a minimal change.

--Rik

I don't know if that would mess things up for other platform or if we can pass the -L flags in the make rule unconditionally on all platforms.

@Carlo: Do the tests with .mex files pass if you set LDFLAGS accordingly?
I'm not sure how things work on MacOS. But maybe you could run something like this in the build directory:
make LDFLAGS="-L$(pwd)/libinterp/.libs -L$(pwd)/liboctave/.libs" check

Markus
Reply | Threaded
Open this post in threaded view
|

Re: Octave 6.0.90 test release available on alpha.gnu.org

mmuetzel
In reply to this post by mmuetzel
Am 14. September 2020 um 18:46 Uhr schrieb "Rik":
> Am 14. September 2020 um 16:13 Uhr schrieb "Markus Mützel":
> > Alternatively (and probably easier and less messy), we could probably add the necessary -L flags in the make rule:
> > https://hg.savannah.gnu.org/hgweb/octave/file/5d4b400e4b66/test/mex/module.mk
>
> If this approach works, I like it as being a minimal change.
>

Please, see the attached patch.
It would be nice if someone on MacOS could test this.

Markus

build_mkmexfile.patch (2K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Octave 6.0.90 test release available on alpha.gnu.org

John W. Eaton
Administrator
On 9/14/20 1:31 PM, Markus Mützel wrote:

> Am 14. September 2020 um 18:46 Uhr schrieb "Rik":
>> Am 14. September 2020 um 16:13 Uhr schrieb "Markus Mützel":
>>> Alternatively (and probably easier and less messy), we could probably add the necessary -L flags in the make rule:
>>> https://hg.savannah.gnu.org/hgweb/octave/file/5d4b400e4b66/test/mex/module.mk
>>
>> If this approach works, I like it as being a minimal change.
>>
>
> Please, see the attached patch.
> It would be nice if someone on MacOS could test this.

Yes, it would be good to know whether that works.  But either way, I'd
like to make another test release this week.

jwe



Reply | Threaded
Open this post in threaded view
|

Re: Octave 6.0.90 test release available on alpha.gnu.org

mmuetzel
Am 14. September 2020 um 21:39 Uhr schrieb "John W. Eaton":

> On 9/14/20 1:31 PM, Markus Mützel wrote:
> > Am 14. September 2020 um 18:46 Uhr schrieb "Rik":
> >> Am 14. September 2020 um 16:13 Uhr schrieb "Markus Mützel":
> >>> Alternatively (and probably easier and less messy), we could probably add the necessary -L flags in the make rule:
> >>> https://hg.savannah.gnu.org/hgweb/octave/file/5d4b400e4b66/test/mex/module.mk
> >>
> >> If this approach works, I like it as being a minimal change.
> >>
> >
> > Please, see the attached patch.
> > It would be nice if someone on MacOS could test this.
>
> Yes, it would be good to know whether that works.  But either way, I'd
> like to make another test release this week.
>
> jwe
>

I pushed a similar patch to stable here:
https://hg.savannah.gnu.org/hgweb/octave/rev/b12ff2cea46a

Let's see how this will turn out.

Markus


12