octave-maintainers
[Top][All Lists]
Advanced

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

Re: Test failures associated with FFTW


From: Daniel J Sebald
Subject: Re: Test failures associated with FFTW
Date: Sat, 16 Mar 2013 03:00:07 -0500
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.24) Gecko/20111108 Fedora/3.1.16-1.fc14 Thunderbird/3.1.16

On 03/16/2013 02:45 AM, John W. Eaton wrote:
On 03/16/2013 03:33 AM, Daniel J Sebald wrote:
Rik (maybe),

I ran "make test" and had a failure for

processing
/usr/local/src/octave/octave-dialog/build2/libinterp/dldfcn/fftw.cc-tst


***** testif HAVE_FFTW
def_method = fftw ("planner");
unwind_protect
method = "estimate";
fftw ("planner", method);
assert (fftw ("planner"), method);
method = "measure";
fftw ("planner", method);
assert (fftw ("planner"), method);
method = "patient";
fftw ("planner", method);
assert (fftw ("planner"), method);
method = "exhaustive";
fftw ("planner", method);
assert (fftw ("planner"), method);
method = "hybrid";
fftw ("planner", method);
assert (fftw ("planner"), method);
unwind_protect_cleanup
fftw ("planner", def_method);
end_unwind_protect
!!!!! test failed
value on right hand side of assignment is undefined

My conclusion is that this test is not being properly excluded. I run
lines individually and immediately get:

octave:1> def_method = fftw ("planner");
warning: fftw: this copy of Octave was not configured to use the FFTW3
planner
error: value on right hand side of assignment is undefined

so perhaps somewhere in the "configure" process the HAVE_FFTW should be
defined as null or logical 0???

Doing a search for "HAVE_FFTW" in addition to some other places I find:

config.log:AMCOND_HAVE_FFTW_FALSE=''
config.log:AMCOND_HAVE_FFTW_TRUE='#'
config.status:S["AMCOND_HAVE_FFTW_FALSE"]=""
config.status:S["AMCOND_HAVE_FFTW_TRUE"]="#"

Is something being overlooked there?

What does

octave_config_info ("features")

show? This is a list of all the HAVE_X macros, with the common "HAVE_"
part omitted. On my system, it has FFTW3, but not FFTW, so it looks like
the testif check is wrong.

I'm seeing:

    FFTW3 = 0
    FFTW3F = 0
    FFTW3F_THREADS = 0
    FFTW3_H = 0
    FFTW3_THREADS = 0

OK, I see what you are saying.  That line should read

***** testif HAVE_FFTW3

That is a generated line (fftw.cc-tst, not a script file), so I'll leave that one up to someone who is more adept with that step.

Dan


reply via email to

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