Hi Michael, I checked config.log and found the error around Python.h because fortran compiler is not exist. So, I installed the fortran compiler for mac osx from http://r.research.att.com/tools/, the error message on config.log looks different now but still around Python.h usability,
Warning: conftest.f:2: Illegal preprocessor directive Please find full config.log from http://pastebin.ca/1903253 Is gnuradio required specific fortran compiler to be used? I check from MacPorts for fortran and found these, [Downloads/gnuradio-3.2.2] > search fortran adaptor @12.0 (lang) Parallel Fortran compiliation system cfitsio @3.250 (science) C access to FITS data files with optional Fortran wrappers fgsl @0.9.3 (math, science) Fortran interface to the GNU scientific library fpp @1.1 (devel) Fortran preprocessor for FORTRAN 77 and Fortran 90 programs ftidy @7.2 (lang) Fortran Tidy g95 @0.92 (lang) Another GNU Fortran 95 compiler p5-extutils-f77 @1.16 (perl) Helper for linking C with Fortran subroutines pgplot @5.2.2 (graphics, devel) C/Fortran graphics library py-f2py @2.43.239_1831 (python) Fortran to Python Interface Generator qd @2.3.11 (devel, math) C++/Fortran-90 double-double and quad-double package - Rasyid On Jul 19, 2010, at 4:42 AM, Michael Dickens wrote: > On Jul 18, 2010, at 3:35 AM, Ninja wrote: >> checking for Python include path... /usr/local/include/python2.6 >> checking Python.h usability... no >> checking Python.h presence... no >> checking for Python.h... no >> configure: error: cannot find usable Python headers >> >> what is the meaning of "configure: error: cannot find usable Python >> headers"?the Python.h is there, and I already tried using original python >> from apple, python from MacPython, and compile manually but same result >> occurred. Above sample was taken from python compiled manually. > > Although you can compile some packages from source and have them work, you > will often be missing patches that provide full functionality. I -highly- > recommend using a package manager such as Fink or MacPorts -- where such > patches are already incorporated. > > That said, if you look at the 'config.log' file & search for "Python.h" you > should find whatever the issue/s is/are. Without seeing that log, there's > very little any of us can do to be of assistance -- I've checked out the > configure M4 script (config/gr_python.m4) and it should work correctly for > your setup. - MLD
_______________________________________________ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
