new SuiteSparse 3.7.0 breaks octave

[mlewis1973]

Octave installed fine last week with @3.4.0_2 @3.7.0_0 compiled fine, but problems with octave port install

Undefined symbols for architecture x86_64:
  "_cholmod_start", referenced from:
      _umf_i_cholmod in libumfpack.a(umf_i_cholmod.o)
  "_cholmod_transpose", referenced from:
      _umf_i_cholmod in libumfpack.a(umf_i_cholmod.o)
  "_cholmod_analyze", referenced from:
      _umf_i_cholmod in libumfpack.a(umf_i_cholmod.o)
  "_cholmod_free_sparse", referenced from:
      _umf_i_cholmod in libumfpack.a(umf_i_cholmod.o)
  "_cholmod_free_factor", referenced from:
      _umf_i_cholmod in libumfpack.a(umf_i_cholmod.o)
  "_cholmod_print_common", referenced from:
      _umf_i_cholmod in libumfpack.a(umf_i_cholmod.o)
  "_cholmod_finish", referenced from:
      _umf_i_cholmod in libumfpack.a(umf_i_cholmod.o)
ld: symbol(s) not found for architecture x86_64
collect2: ld returned 1 exit status
make[2]: *** [liboctave.dylib] Error 1

[mlewis1973]

octave-devel seems to like SuiteSparse 3.7.0, but has runtime problems...... will let someone else open a ticket on that

[mlewis1973]

I can confirm that reverting to SuiteSparse 3.2.0_2 (83774) restores building of octave port. There is a minor issue with liboctave and embedding octave in other programs. Appears to be a malloc and free being called from different libraries...... I will follow up on that on octave-dev and Help-octave mailing lists.

[mlewis1973]

Probably related to #32754

[eborisch (Eric A. Borisch)]

Hopefully fixed in r88691. I've kept the move of metis to a variant (within SuiteSparse) to enable binary distribution of SuiteSparse and py2N-scipy; if there are still problems with that change for Octave, please report it here.

I'm not closing this ticket as I haven't tested this change within Octave. If someone gives it a go please report back.