Re: Proper way to link Fortran with C++

inker name for a Fortran identifier). Regards, Steven G. Johnson

Re: Proper way to link Fortran with C++

inker name for a Fortran identifier). Regards, Steven G. Johnson

Re: How to get AC_DEFINE to generate a macro, e.g., #define incr(x) ((x)+1) ?

EFINE for a macro, you need to use AH_TEMPLATE to give its config.h.in template separately. The following works for me: AH_TEMPLATE([INCR], [increment]) AC_DEFINE([INCR(x)], [((x)+1)]) Cordially, Steven G. Johnson

Why doesn't F9x support use AC_FC_SRCEXT?

any .f90 file on the compilation line and $FCFLAGS_f95 before any .f95 file. (Note that this *cannot* be done in autoconf, because all autoconf could do would be to append something to $FCFLAGS, which will fail. Read the AC_FC_SRCEXT documentation.) Cordially, Steven G. Johnson PS. This

Re: Fortran 9x support

On Thu, 9 Oct 2003, Sander Niemeijer wrote: > I can understand keeping F77/FFLAGS/FLIBS/AC_PROG_F77 for backwards > compatibility. However, the current approach is to keep using these > macros and variables for f77 and use the new FC* ones only for f90 and > upwards. My question is whether it is no

Re: Fortran 9x support

Steven G. Johnson wrote: I've attached a draft of the documentation for the new macros. PS. The attachment is plain ASCII text; I momentarily forgot about Microsoft in giving it a ".doc" ending (for "documentation").

Fortran 9x support

might do: foo.o: foo.f90 $(FC) -c $(FCFLAGS) $(FCFLAGS_f90) foo.f90 Cordially, Steven G. Johnson fortran.doc Description: MS-Word document

canonical autogen.sh?

I really like the autogen.sh file that comes with most GNOME programs, and steal it for many of my own programs. This sort of thing is quite useful for people using tools like automake and autoconf. Has there been any consideration of putting together a "standard" autogen.sh script and including

Re: Libraries with sources in subdirectories?

On 30 May 2001, Tim Van Holder wrote: > > > You can even arrange to have the objects kept in subdirectories using: > > > AUTOMAKE_OPTIONS = subdir-objects > > > This option isn't really documented yet, but it is on my to-do list. > > > > I assume you mean that bar/baz.c is normally built as b

Re: Libraries with sources in subdirectories?

e only things delaying automake 1.5. > And right now I know of no bugs that must be fixed for the release. That's good to hear; coming on the heels of autoconf 2.50 and libtool 1.4, the GNU toolchain is getting a much-needed overhaul. I would love to see the new release within the next couple of months. Cordially, Steven G. Johnson

Libraries with sources in subdirectories?

any tips! Cordially, Steven G. Johnson