[Top][All Lists]

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

Re: fft support on octave

From: Kai Torben Ohlhus
Subject: Re: fft support on octave
Date: Fri, 13 Dec 2019 16:49:17 +0900
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.2.1

On 12/13/19 3:48 PM, niraj pandey wrote:
> On Fri, Dec 13, 2019 at 12:14 PM Kai Torben Ohlhus <address@hidden>
>> On 12/13/19 3:14 PM, niraj pandey wrote:
>>> Hi ,
>>> Could you pls help me how to build octave with fft support. I used the
>>> following command to build octave but still getting issue.
>>> octave:1> fft(0:255)
>>> error: fft: support for FFTW was unavailable or disabled when liboctave
>>> was built
>>> ./configure --prefix=/home/niraj/oc CFLAGS=-fPIC CXXFLAGS=-fPIC
>>> --enable-shared --with-gui --with-qt
>>> --with-blas=/v5.1.0/BLAS-3.8.0/blas_LINUX.a
>>> --with-lapack=/v5.1.0/lapack-3.8.0/liblapack.a --enable-float
>>> --enable-sse --with-fftw3-includedir=/tmp/fftw/include/
>>> --with-fftw3-libdir=/tmp/fftw/lib
>>> Config.log says:   configure:69014: WARNING: FFTW3 library not found.
>>> The slower FFTPACK library will be used instead.
>>> Thanks
>>> Niraj
>> Dear Niraj,
>> Still I do not understand why you deploy libraries in the "/tmp"
>> directory, which is on usual Linux system a volatile TeMPorary
>> directory.  Can't you use your user's /home/niraj directory for all
>> libraries instead?  This might be one root of trouble.
>> Can you describe, how you installed the FFTW3 library on your system?
>> HTH,
>> Kai
> Hello Kai,
> I used the following command to install FFTW3.
> ./configure --prefix=/home/niraj/fftw --enable-float --enable-sse
> To install the tool on /tmp area first is just check all the
> dependencies required by that tool . Once I identify all the
> dependencies I install the tool on production area through some
> automated process :)
> Thanks
> Niraj

Can you submit a small portion of config.log around the error

>>> configure:69014: WARNING: FFTW3 library not found.

Usually there is a program which is compiled during ./configure and this
normally contains the compiler output which might be helpful to get to
the root of the trouble.


reply via email to

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