[Top][All Lists]

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

Re: 2 questions

From: Wil Turner
Subject: Re: 2 questions
Date: Fri, 9 Jul 2004 14:29:37 -0400

I must be doing (or not doing) something else, because I am already using libtool 1.5.6 and experiencing these 2 problems.

I grep'd around a bit and found that my aclocal.m4 file (generated automatically by aclocal) has the following section:

dnl And a similar setup for Fortran 77 support
    [define([AC_PROG_F77], defn([AC_PROG_F77])[AC_LIBTOOL_F77

Is this the source of the checks for the fortran compiler and any ideas on why aclocal is putting it there?



On Jul 7, 2004, at 5:37 PM, Dalibor Topic wrote:

Bob Friesenhahn wrote:
This extra junk is coming from libtool (list at address@hidden). Probably the other projects are not using libtool. The next major release of libtool will allow you to specify the languages that should be configured.
On Wed, 7 Jul 2004, Wil Turner wrote:
Hi all,

I'm still getting to know the whole autoconf/automake/libtool system, so I apologize if these questions are really stupid...

1) configure is checking for Fortran compilers, but my project doesn't use Fortran. I found one of the fortran commands in the aclocal.m4 file that was generated by aclocal. Any ideas why aclocal thinks I need fortran?

2) I notice some other GNU projects I've compiled don't have the "checking the maximum length of command line arguments" test, which is time consuming. I'd like to get rid of this if possible. How?

Yep, and the second qustion has been largely solved with recent versions of libtool. Try libtool 1.5.6.

dalibor topic

reply via email to

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