Thank you for testing.

I pushed the patches here:
https://hg.savannah.gnu.org/hgweb/octave/rev/2717d1cceee2
https://hg.savannah.gnu.org/hgweb/octave/rev/463c1f9bfadc

Looking at the build log of the GitHub runner:
https://github.com/gnu-octave/octave/actions/runs/8617107213/job/23616293574

I'm guessing the two attached patches should help with the symbols that aren't exported currently.


(file #55930, file #55931)

(see also Discourse thread https://octave.discourse.group/t/do-we-have-buildbots-for-dev-10-0-0-octave/5480)

Since a few days the bytecode-interpreter branch of default Octave cannot get crossbuilt anymore. AFAICS it may have started with this cset:
abdb846bafe8 "Instantiate octave_base_matrix and octave_base_scalar template classes".
That is, merging the cset before (714c6d2e253e "maint: Merge stable to default.") with the bytecode-interpreter branch (cset af9c0617f9f9 "maint: Merge default to bytecode-interpreter.") from a day earlier leads to a successful crossbuild, merging the b.-i. branch with later csets yields crossbuild failures.
Why it builds fine for Linux but not for Windows is beyond me. Apparently mxe-octave is a bit more fragile?

I just tried with a clean checkout updated to the bytecode-interpreter branch. It builds and AFAICS runs fine on Linux, although with a few warnings, a.o., these:

  CXX      libinterp/octave-value/liboctave_value_la-ov-float.lo
../dev/libinterp/octave-value/ov-base-mat-inst.cc:34:30: warning: type attributes ignored after type is already defined [-Wattributes]
   34 | template class OCTINTERP_API octave_base_matrix<boolNDArray>;
      |                              ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
../dev/libinterp/octave-value/ov-base-mat-inst.cc:44:30: warning: type attributes ignored after type is already defined [-Wattributes]
   44 | template class OCTINTERP_API octave_base_matrix<ComplexNDArray>;
      |                              ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
../dev/libinterp/octave-value/ov-base-mat-inst.cc:45:30: warning: type attributes ignored after type is already defined [-Wattributes]
   45 | template class OCTINTERP_API octave_base_matrix<FloatComplexNDArray>;
      |                              ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
../dev/libinterp/octave-value/ov-base-mat-inst.cc:46:30: warning: type attributes ignored after type is already defined [-Wattributes]
   46 | template class OCTINTERP_API octave_base_matrix<FloatNDArray>;
      |                              ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
../dev/libinterp/octave-value/ov-base-mat-inst.cc:47:30: warning: type attributes ignored after type is already defined [-Wattributes]
   47 | template class OCTINTERP_API octave_base_matrix<NDArray>;
      |                              ^~~~~~~~~~~~~~~~~~~~~~~~~~~
../dev/libinterp/octave-value/ov-base-mat-inst.cc:129:30: warning: type attributes ignored after type is already defined [-Wattributes]
  129 | template class OCTINTERP_API octave_base_matrix<Cell>;
      |                              ^~~~~~~~~~~~~~~~~~~~~~~~

but crossbuilding the resulting dist archive leads to a failure.

I asked on Discourse about buildbots for default Octave, but AFAIU there are no buildbots for the bytecode-interpreter branch. So it seems bytecode-interpreter build failures go largely unnoticed then, am I right?

I'll cc Petter (creator of the bytecode-interpreter branch).

Compressed buildlog of mxe-octave attached.