AC_F77_WRAPPERS cannot be AC_DEFUN'ed

2003-08-14 Thread Denis Barbier
Hi, consider this simple test: configure.ac AC_INIT([foo], [1.0]) AC_DEFUN([FORTRAN_CHECK], [ AC_PROG_CC AC_PROG_F77 AC_F77_WRAPPERS ]) FORTRAN_CHECK AC_OUTPUT End of configure.ac = With autoconf 2.57 and current CVS snapshot, here is what happens: $ .

Re: configure.in vs. configure.ac clash

2002-03-04 Thread Denis Barbier
On Sat, Mar 02, 2002 at 03:59:32PM +0100, Alexandre Duret-Lutz wrote: > >>> "gd" == Guido Draheim <[EMAIL PROTECTED]> writes: > > gd> while trying to create an rpm for the mp4h project, I jumped on the > gd> following problem: > > gd> - the toplevel configure has configure.ac > gd> - a subdi

Re: [f77] Disable C comments in config.h

2001-09-03 Thread Denis Barbier
On Mon, Sep 03, 2001 at 09:55:34AM +0200, Akim Demaille wrote: [...] > Denis> Hi, AIX Fortran compiler dislikes C comments in config.h; it > Denis> would be nice to have a macro to disable such comments (i mean > Denis> a documented macro ;)), [...] > Anyway, back to this issue: what do you mean

[f77] Disable C comments in config.h

2001-08-31 Thread Denis Barbier
Hi, AIX Fortran compiler dislikes C comments in config.h; it would be nice to have a macro to disable such comments (i mean a documented macro ;)), or maybe check for this feature in AC_PROG_F77 and remove them automagically. Denis

Re: autoconf-2.50c released

2001-07-16 Thread Denis Barbier
On Mon, Jul 16, 2001 at 10:35:29AM +0200, Akim Demaille wrote: > >>>>> "Denis" == Denis Barbier <[EMAIL PROTECTED]> writes: > > Denis> Hi Akim, > > Hi! > > Denis> is there a (good ;)) reason why Autoconf 2.50 do not respect > Denis&

Re: autoconf-2.50c released

2001-07-14 Thread Denis Barbier
On Sat, Jul 14, 2001 at 07:48:40PM +0200, Akim Demaille wrote: > > This is our release candidate but for the remaining F77 issues. > Please, test it hard, make it suffer. [...] Hi Akim, is there a (good ;)) reason why Autoconf 2.50 do not respect its own advice, e.g. by not renaming configure.i

Re: Fortran name-mangling scheme fails on HP-UX 11.11

2001-06-29 Thread Denis Barbier
On Fri, Jun 29, 2001 at 11:44:23AM -0500, John W. Eaton wrote: > On 28-Jun-2001, Steven G. Johnson <[EMAIL PROTECTED]> wrote: > > | On Thu, 28 Jun 2001, Denis Barbier wrote: > | > But there is no reason for AC_F77_WRAPPERS to require > | > AC_F77_LIBRARY_LDFLAGS; in _A

Re: Fortran name-mangling scheme fails on HP-UX 11.11

2001-06-28 Thread Denis Barbier
On Thu, Jun 28, 2001 at 04:45:54PM -0400, Steven G. Johnson wrote: > On Thu, 28 Jun 2001, Denis Barbier wrote: > > But there is no reason for AC_F77_WRAPPERS to require > > AC_F77_LIBRARY_LDFLAGS; in _AC_F77_NAME_MANGLING one may simply (well, > > i have no idea whether

Re: Fortran name-mangling scheme fails on HP-UX 11.11

2001-06-28 Thread Denis Barbier
On Tue, Jun 26, 2001 at 10:27:20AM -0400, Steven G. Johnson wrote: > This is actually a problem in AC_F77_LIBRARY_LDFLAGS, and may represent > the first general failure of the library detection scheme that we use. > Sigh.. > > If I correctly understand what you wrote, then your Fortran compiler >

Including config.h in Fortran preprocessed files

2001-06-21 Thread Denis Barbier
Hi, there is another glitch with Fortran on HP-UX 11.11. When mixing C and Fortran source files, it is convenient to include config.h in .F files when some symbols have to be checked. But F77_FUNC prints a two-line comment in config.h, which is not discarded by HP Fortran preprocessor, and compil

Fortran name-mangling scheme fails on HP-UX 11.11

2001-06-21 Thread Denis Barbier
Hi, config.log and configure.in are attached, let me know if you need more informations. The detection works fine when calling ./configure LPATH=/opt/fortran90/lib/pa2.0/:/opt/fortran90/lib/:/usr/lib/:/opt/langtools/lib/ Denis This file contains any messages produced by compilers while

Re: TODO for 2.51, aiming at a release *this* week

2001-06-09 Thread Denis Barbier
On Sat, Jun 09, 2001 at 09:04:10PM +0200, Akim Demaille wrote: [...] > If someone thinks there is something which _must_ be done for 2.51, > please, speak now. Or fill a PR. Hi Akim and others, i did not read this mailing-list for months, so forgive me if this suggestion has already been discus