Re: getting libtool to not call AC_PROG_FC and AC_PROG_F77...

[Ed Hartnett]

Ralf Wildenhues <address@hidden> writes:

> * Mike Frysinger wrote on Tue, Jan 16, 2007 at 11:48:31PM CET:
>> On Tuesday 16 January 2007 17:30, Ed Hartnett wrote:
>> > When I call AC_PROG_LIBTOOL it seems to call AC_PROG_F77 and
>> > AC_PROG_FC, but I don't want it to.
>> 
>> this should be fixed in the latest cvs, just not latest release
>
> Bzzt.  Wrong.  (Also note that Ed is using a CVS version that's new
> enough.)

Ralf, you are abandoning your usual politeness!

Hung over today from too much of that wonderful German beer? ;-)

> Incidentally, the code in the link you posted could help Ed.  But I'll
> add that there is no way we can guarantee this to remain functional.
> I don't know if it's feasible for Libtool to guarantee that you can
> split the compiler and its shared library creation bits.  Someone with
> time could try to look into it...
>

I think I have it sorted out, and the important fact to remember is
that the libtool calling of these macros will not matter *if* F77 and
FC are already set.

The problems I was having had to do with situations where there was no
fortran 90 compiler, but there was a fortran 77 compiler. In that
case, my configure script was setting F77 but not FC.

Libtool noticed that FC is not set, and so it sets it, mucking
everything up for me.

I fixed the problem by making sure that, in this case, F77 and FC are
both set (to the same thing).

This stop libtool from messing with them, and everything works fine
for me now (until I find the next problem ;-).

Thanks for all the replies, and Ralf, try some vitamin B and a good
strong cup of coffee! ;-)

Thanks!

Ed

-- 
Ed Hartnett  -- address@hidden