[Top][All Lists]

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

Re: Strange LT_INIT behavior

From: Peter O'Gorman
Subject: Re: Strange LT_INIT behavior
Date: Thu, 21 May 2009 00:06:45 -0500

On May 18, 2009, at 7:56 PM, Jeff Squyres wrote:

Nifty idea!

Unfortunately, it runs into a bit of a snag -- AC_PROG_F77 first checks for g77; we have long-since overridden this ordering with our own:

AC_PROG_F77([gfortran g77 f77 xlf frt ifort pgf77 fort77 fl32 af77])

If I move up LT_INIT to shortly after AC_PROG_CC (but before AC_PROG_CXX|F77|F90), then C++ Libtool tests come *after* AC_PROG_CXX, but the Libtool tests for F77 seem to come *before* we call AC_PROG_F77, and therefore call AC_PROG_F77 with the default ordering; not the ordering that we want.

Hence, g77 is found instead of gfortran. This, unfortunately, is a dealbreaker for us. :-(

Is there another way?

Oh, yuck, libtool.m4 redefines AC_PROG_F77 (and AC_PROG_CXX, AC_PROG_FC etc) in such a way that the arguments are discarded. I will try to work up a libtool patch for this over the weekend.

Thanks (and sorry),
Peter O'Gorman

reply via email to

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