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

Re: 19991207: using "pgf90" under Red Hat Linux 6.1

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.

  • Subject: Re: 19991207: using "pgf90" under Red Hat Linux 6.1
  • Date: Tue, 07 Dec 1999 16:33:46 -0700
Dean,

>Date: Tue, 07 Dec 1999 20:04:21 -0800
>From: "Dean N. Williams" <address@hidden>
>Organization: PCMDI
>To: Steve Emmerson <address@hidden>
>Subject: Re: 19991207: using "pgf90" under Red Hat Linux 6.1
>Keywords: 199912071733.KAA19310

In the above message, you wrote:

>     I'm not sure why, but I had to do the following on my system:
> 
>     ln -s /usr/lib/gcc-lib/i386-redhat-linux/egcs-2.91.66/libgcc.a libgcc.a

If the C compiler on your system needs help finding its own runtime
library, then your development environment has been corrupted.  I
suggest notifying your system administrator.

>     This got me down to the "make test" where I ran into the same
>     ol' problem with Fortran.
> 
> make[2]: Entering directory `/usr/local/src/netcdf-3.5/src/fortran'
> + pgf90 -c -O -w ftest.F
> ar cru   ../libsrc/libnetcdf.a fort-attio.o fort-control.o fort-dim.o 
> fort-genatt.o fort-geninq.o fort-genvar.o
> fort-lib.o fort-misc.o fort-v2compat.o fort-vario.o fort-var1io.o 
> fort-varaio.o fort-varmio.o fort-varsio.o
> ranlib ../libsrc/libnetcdf.a
> pgf90 -o ftest -O -w  ftest.o ../libsrc/libnetcdf.a
> Linking:
> ./ftest
> make[2]: *** [test] Segmentation fault
> make[2]: Leaving directory `/usr/local/src/netcdf-3.5/src/fortran'
> make[1]: *** [subdir_target] Error 1
> make[1]: Leaving directory `/usr/local/src/netcdf-3.5/src'
> make: *** [fortran/test] Error 2

Would you please send me the files "configure.log" and "config.log"
associated with this attempt.

--------
Steve Emmerson   <http://www.unidata.ucar.edu>