Hmm - OK - I now see where that is mentioned in the web help pages - I
should have looked there first; but why not have configure set them?
Also, most of my experience has been on linux where there is a decided
preference towards building shared libs. For the netCDF build, as
well as the DODS libs, everything seems to be geared towards static
libs. Is there a reason for this? (I don't know - I'm just
wondering).
The Fortran compilers were the g77-3.4, with f2c, and the g95 compiler
from the g95 site, precompiled for AMD64.
thanks for your help
Harry
On Tuesday 22 February 2005 2:04 pm, Ed Hartnett wrote:
> Harry Mangalam <hjm@xxxxxxxxx> writes:
> > Hi there,
> >
> > This is mostly an FYI:
> >
> > I'm building netCDF lib on an opteron /Linux (ubuntu) in 64 bit
> > mode with f77 & f90, gcc 3.4.
> >
> > I can get it to build correctly after modifying the macro.make
> > file to resemble
> >
> > 31 # Compilation:
> > 32 CC = gcc -Df2cFortran <-- had to be manually edited
> > 33 CXX = g++
> > 34 FC = f77
> > 35 F90 = f90
> > 36 CFLAGS = -g
> > 37 CXXFLAGS = -g -O2
> > 38 FFLAGS = -ff2c <--had to be manually edited
> > 39 F90FLAGS
> >
> > When you next re-examine the autoconf process, you might try to
> > detect this platform and add these flags automagically. Our
> > experience with the opteron so far has been pretty good and this
> > may well be a standard platform for large data sets soon.
>
> The intention is that you set these as environment variables before
> running configure.
>
> Can you tell me what fortran compiler the above works with?
>
> Thanks!
>
> Ed
--
Cheers, Harry
Harry J Mangalam - 949 856 2847 (vox; email for fax) - hjm@xxxxxxxxx
<<plain text preferred>>
