[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #55950] building default with sundials 4.x fai

From: Mike Miller
Subject: [Octave-bug-tracker] [bug #55950] building default with sundials 4.x fails to detect KLU in configure
Date: Mon, 18 Mar 2019 14:41:26 -0400 (EDT)
User-agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/73.0.3683.75 Safari/537.36


                 Summary: building default with sundials 4.x fails to detect
KLU in configure
                 Project: GNU Octave
            Submitted by: mtmiller
            Submitted on: Mon 18 Mar 2019 11:41:25 AM PDT
                Category: Configuration and Build System
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: Unexpected Error
                  Status: None
             Assigned to: None
         Originator Name: 
        Originator Email: 
             Open/Closed: Open
         Discussion Lock: Any
                 Release: dev
        Operating System: GNU/Linux



I have finally gotten time to build and install my own copy of sundials 4.1.
When running configure with CPPFLAGS and LDFLAGS pointing to this copy of
sundials, configure finds it, but does not automatically detect that the
library was built with KLU support. It definitely is, the only problem still
seems to be the link to the klu.h header file.

Excerpt from config.log

configure:70899: checking sunlinsol/sunlinsol_klu.h usability
configure:70899: gcc -c -g -O2 -fstack-protector-strong -Wformat
-Werror=format-security -pthread -fopenmp   -D_FORTIFY_SOURCE=2
-I/home/mike/sd/include conftest.c >&5
In file included from conftest.c:604:
/home/mike/sd/include/sunlinsol/sunlinsol_klu.h:34:10: fatal error: klu.h: No
such file or directory
 #include <klu.h>

But sundials 4 was adapted to allow the application to include klu.h in its
own way and not depend on the path being exactly klu.h. So configure needs to
test for the header file this way for the feature tests to pass.

If I fudge the configure feature test results by passing the following five
cache variables that I know should be passing on my system


then configure passes with all sundials features enabled for the v4 API, and
'make' succeeds and all tests pass, no features disabled.

The point here is to avoid requiring the user to pass
'-I/usr/include/suitesparse' when building Octave with current versions of
sundials, configure needs to include klu.h under different alternative names
in the sundials tests just like it does in the '__ode15__.cc' source file.


Reply to this item at:


  Message sent via Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]