Hi Eric, No, this didn't work for me. After a bit of reading on the issue I found out that autoconf generally does not work well with AC_PROG_XXX within a shell if then else. It's in fact considered to be a feature of autoconf (as the designers can't imagine why would the package conditionally depend on a compiler) that the macro is expanded outside of the if/then/else.
However, after removing AC_PROG_F77 from config/gr_fortran.m4, --disable-fortan still does nothing, but at least Python.h succeeds. I think it should be noted that I'm using autoconf 2.64 with libtool 2.2.6a. --Szymon On Thu, Sep 3, 2009 at 4:21 PM, Eric Blossom<e...@comsec.com> wrote: > > Thanks. > > I think a better fix may be in gr_fortran.m4 : > > Can you try this please? > > > > AC_DEFUN([GR_FORTRAN],[ > dnl if you want to generate a different table of interpolator taps, you > need fortran. > dnl we default to off, since almost no one wants to do this. > AC_ARG_ENABLE(fortran, AC_HELP_STRING([--enable-fortran],[enable fortran > (no)]), > [], [enable_fortran=no]) > AM_CONDITIONAL(ENABLE_FORTRAN, test "x$enable_fortran" = xyes) > > if test "x$enable_fortran" = xyes > then > AC_LANG_PUSH(Fortran 77) > AC_PROG_F77 > AC_F77_LIBRARY_LDFLAGS > AC_LANG_POP(Fortran 77) > fi > ]) > > > Thanks! > Eric > _______________________________________________ Patch-gnuradio mailing list Patch-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/patch-gnuradio
