[Top][All Lists]

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

Re: [autoconf] How to deal problems in current autoconf version of M4 ma

From: Giulio Paci
Subject: Re: [autoconf] How to deal problems in current autoconf version of M4 macros
Date: Fri, 03 Feb 2012 19:05:57 +0100
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:8.0) Gecko/20120104 Icedove/8.0


On 02/03/2012 05:21 PM, suzuki toshiya wrote:
> I'm not sure if I'm understanding the situation correctly,
> but if the trouble occurs in the generation of configure,
> I propose to consider an inclusion of script to
> the project.
The problem is that generating configure with current version (2.68) of
autoconf ends in a configure script that is not able to guess proper
settings for fortran compilers in some environments.

> You can check the version of automake/autoconf
> and control the options to give aclocal, automake, autoconf,
> thus, you can add /or ignore the directory including
> your own fortran.m4 by changing "-I xxx" option.
If I understand correctly you are suggesting to add a directory with a
replacement for fortran.m4 and conditionally include that directory
depending on the tools version. Is it right?
Will the tools chose my own version of fortran.m4 instead of the
autoconf one, using this approach (and why?)?
Is it possible to achieve something similar that also works with autoreconf?

> Giulio Paci wrote:
>> Hi to all,
>>      some time ago I converted a project (
>> build system from a simple Makefile to autoconf+automake.
>> The project needs a fortran compiler. Unfortunately the fortran.m4 file
>> shipped with autoconf 2.68 seems not to work on many current OSes (my
>> own, just to give an example). After investigating a little bit I
>> provided a patch for autoconf that was included in the development tree.
>> Time has passed, the last autoconf release is still 2.68, users keeps
>> complaining and it is difficult to setup a system that is suitable to
>> create a proper configure script.
>> My question is: is there any easy/clear way to include a patched
>> fortran.m4 file within the project and use that version only if autoconf
>> version is less than 2.69? Is there a more elegant fix to that?
>> Bests,
>>      Giulio.
>> _______________________________________________
>> Autoconf mailing list
>> address@hidden

reply via email to

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