bugGNU Octave - Bugs: bug #55926, sundials 3.2.1 build: configure...


bug #55926: sundials 3.2.1 build: configure syntax error

Submitter:  A.R. Burgers <arb>
Submitted:  Fri 15 Mar 2019 08:05:16 AM UTC
Category:  Configuration and Build System Severity:  2 - Minor
Priority:  3 - Low Item Group:  Unexpected Error or Warning
Status:  Fixed Assigned to:  None
Originator Name:  Open/Closed:  * Closed
Release:  * dev Operating System:  * GNU/Linux
Fixed Release:  None Planned Release:  None
* Mandatory Fields

Add a New Comment (Rich Markup)

Comment Type & Canned Response:


Fri 15 Mar 2019 05:40:48 PM UTC, comment #4: 

This is fixed for me now, the test is properly quoted because the shell variable may not exist (one test done conditionally inside another test).

Thanks for catching this error.

Mike Miller <mtmiller>
Project Administrator
Fri 15 Mar 2019 05:21:55 PM UTC, comment #3: 

Confirmed here with sundials 3.1.2. The syntax error shows in the configure output. However the results are correct for me. With sundials 3.x it is supposed to fail to include sunlinsol_klu.h even though the file exists.

So the only issue here is silencing the "test: =: unary operator expected" message, not changing any behavior.

Mike Miller <mtmiller>
Project Administrator
Fri 15 Mar 2019 03:48:49 PM UTC, comment #2: 

I built sundials (4.1.0 now) with

The suitesparse part does not propagate to the sunlinsol_klu header, so klu.h is not found. I replaced <klu.h> with <suitesparse/klu.h> after installation in the installed sunlinsol_klu.h, and then the build configures and compiles successfully.

Without that edit I get the "unary operator expected" error from the configure script.

A.R. Burgers <arb>
Fri 15 Mar 2019 10:14:36 AM UTC, comment #1: 

It doesn't find sunlinsol/sunlinsol_klu.h because of this

configure:76957: checking sunlinsol/sunlinsol_klu.h usability
configure:76957: gcc -std=gnu11 -c -O2 -pthread -fopenmp   -DQT_NO_DEBUG=1 -I/home/dusk/aburgers/x86_64/include conftest.c >&5
In file included from conftest.c:599:0:
/home/dusk/aburgers/x86_64/include/sunlinsol/sunlinsol_klu.h:46:17: fatal error: klu.h: No such file or directory
 #include "klu.h"

my klu.h, or at least a klu.h, dwells in include/suitesparse/klu.h

A.R. Burgers <arb>
Fri 15 Mar 2019 08:05:16 AM UTC, original submission:  

I was still at sundials 2.7.1, but dev would not build anymore with https://savannah.gnu.org/bugs/?55911. I upgraded sundials to 3.2.1, and now I can build again, however there are some issues.

checking for sunlinsol/sunlinsol_dense.h... yes
checking whether SUNDIALS IDA includes the SUNLINSOL_DENSE linear solver... yes
checking sunlinsol/sunlinsol_klu.h usability... no
checking sunlinsol/sunlinsol_klu.h presence... no
checking for sunlinsol/sunlinsol_klu.h... no
../octave/configure: line 77091: test: =: unary operator expected
configure: WARNING: SUNDIALS IDA library not configured with SUNLINSOL_KLU or sunlinksol_klu.h is not usable; ode15i and ode15s will not support the sparse Jacobian feature

line 77091 in the configure is the first line of this piece of configure code:

  if test $octave_cv_sundials_sunlinsol_klu = yes \
     && test "x$ac_cv_header_sunlinsol_sunlinsol_klu_h" = xyes; then

$as_echo "#define HAVE_SUNDIALS_SUNLINSOL_KLU 1" >>confdefs.h

    warn_sundials_sunlinsol_klu="SUNDIALS IDA library not configured with SUNLINSOL_KLU or sunlinksol_klu.h is not usable; ode15i and ode15s will not support the sparse Jacobian feature"

  { $as_echo "$as_me:${as_lineno-$LINENO}: WARNING: $warn_sundials_sunlinsol_klu" >&5
$as_echo "$as_me: WARNING: $warn_sundials_sunlinsol_klu" >&2;}


I don't understand yet why it doesn't detect the sunlinsol_klu stuff since I have in my installation dir:


A.R. Burgers <arb>


(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:

No files currently attached


Depends on the following items: None found

Items that depend on this one: None found


Carbon-Copy List
  • -email is unavailable- added by arb (Submitted the item)

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

    Only project members can vote.





    Follow 6 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2019-03-15 mtmiller StatusConfirmed Fixed
        Open/ClosedOpen Closed
    2019-03-15 mtmiller Severity3 - Normal 2 - Minor
        Priority5 - Normal 3 - Low
        Item GroupRegression Unexpected Error or Warning
        StatusNone Confirmed

    Back to the top

    Powered by Savane 3.9