[Octave-bug-tracker] [bug #63799] Build failure with 64-bit SuiteSparse

[Arun Giridhar]

URL:
  <https://savannah.gnu.org/bugs/?63799>

                 Summary: Build failure with 64-bit SuiteSparse
                 Project: GNU Octave
               Submitter: arungiridhar
               Submitted: Mon 13 Feb 2023 11:42:51 AM EST
                Category: Libraries
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: Build Failure
                  Status: None
             Assigned to: None
         Originator Name: 
        Originator Email: 
             Open/Closed: Open
                 Release: dev
         Discussion Lock: Any
        Operating System: GNU/Linux
           Fixed Release: None
         Planned Release: 9.1.0 (current default)


    _______________________________________________________

Follow-up Comments:


-------------------------------------------------------
Date: Mon 13 Feb 2023 11:42:51 AM EST By: Arun Giridhar <arungiridhar>
I started getting these documentation build errors when building the current
default branch of Octave (hg id 6bf833d96cbe):


  GEN      doc/interpreter/spchol.eps
  GEN      doc/interpreter/spchol.pdf
  GEN      doc/interpreter/spchol.png
DPOTRF: parameter number 2 is invalid
fatal: caught signal Segmentation fault -- stopping myself...
DPOTRF: parameter number 2 is invalid
fatal: caught signal Segmentation fault -- stopping myself...
DPOTRF: parameter number 2 is invalid
fatal: caught signal Segmentation fault -- stopping myself...
make[2]: *** [Makefile:31920: doc/interpreter/spchol.pdf] Segmentation fault
(core dumped)
make[2]: *** Waiting for unfinished jobs....
make[2]: *** [Makefile:31930: doc/interpreter/spchol.png] Segmentation fault
(core dumped)
make[2]: *** [Makefile:31910: doc/interpreter/spchol.eps] Segmentation fault
(core dumped)


On digging, it turned out to be a problem with how certain numerical libraries
are now being packaged on Arch Linux and its derivatives.

It seems that suitesparse was recently changed to suitesparse64, prompted by
sundials, and it now uses 64-bit BLAS and LAPACK. However, Octave's configure
picks "libblas" and "liblapack" which in turn point to a 32-bit BLAS and
LAPACK libraries (in my case, OpenBlas from the openblas-lapack AUR package).

One workaround for making Octave build with documentation now is to explicitly
pass the configure options

--with-blas="blas64" --with-lapack="lapack64"
-

Unfortunately that subsequently crashes in "make check" with

  libinterp/corefcn/chol.cc-tst ..................................fatal:
caught signal Segmentation fault -- stopping myself...


The other workaround is to disable building documentation and to let Octave
pick the 32-bit BLAS and LAPACK for everything, which passes "make check" but
disables some suitesparse functions.

I tried to remove the 32-bit openblas-lapack AUR package to see if forcing a
single library version would help matters, but because it provides "libblas"
and "liblapack" it cannot be removed without also removing python-numpy and
arpack.

Since Octave requires all three libraries (arpack, sundials, and suitesparse /
suitesparse64) for full functionality, I am copying the Arch package
maintainers Antonio Rojas (suitesparse64, octave, cblas64, openblas64,
lapack64), and David Runge (arpack) for their thoughts on how to resolve this
conflict.







    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?63799>

_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/