Hi, Eric
Toby's suggestion helped me solve the problem. If I
configure "without" the --enable-sse option, then
everything works well. Is --enable-sse option
necessary here?
Thanks to you guys
Sachi
--- Eric Blossom <[EMAIL PROTECTED]> wrote:
> On Sat, Apr 02, 2005 at 11:03:48PM -0800, Sachi
> wrote:
> > Hi, Eric
> >
> > I have checked it with gdb, it returned:
> >
> > (gdb) continue
> > Continuing.
> >
> > Program received signal SIGSEGV, Segmentation
> fault.
> > [Switching to Thread -1208514880 (LWP 1030)]
> > 0x007eb73f in m2fv_64_0 () from
> > /usr/local/lib/libfftw3f.so.3
> >
> > Then gdb stopped. I didn't use any breakpoints in
> the
> > code. BTW: I can run the demos provided by
> wxPython.
> >
> > Can you sqeeze any information from this? Or what
> > should I do next?
> > Thanks for your time
> > Sachi
>
> This is good info. It's blowing up libfftw3f, the
> FFTW code.
> Haven't ever seen that failure.
>
> I'd suggest building fftw from source (www.fftw.org)
> using the
> --enable-single --enable-sse --enable-shared
> configure options, and
> then after it's built make sure that its "make
> check" passes.
>
> If this fixes the problem, there may be a problem
> with the libfftw3f
> library distributed with FC3.
>
> Eric
>
__________________________________
Yahoo! Messenger
Show us what our next emoticon should look like. Join the fun.
http://www.advision.webevents.yahoo.com/emoticontest
_______________________________________________
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
