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.
i might be able to clear up some evident confusion here. firstly, we (unidata) have a couple linux systems: two (including sunshine.unidata.ucar.edu which the uname was run on) are running redhat6.1 and one running redhat5.2. all systmes have all the latest patches and also the latest linux kernel (2.2.13) installed. kernels do not generally affect non-operating system type operations, compiling included. redhat6.1 was distributed with kernel version 2.2.12-20. secondly, and more importantly, although i haven't been privy to this conversation, i gather that you, dean, are having trouble compiling a program using fort77 and/or pgf90. i don't know anything about pgf90, but it appears that you are using a redhat6.1 system that was updated from a redhat5.x system, so i have some clues for you concerning fort77 and glibc. here's the scoop: redhat moved to glibc2.1 with redhat6.x, whereas redhat5.x used glibc2.0. there are some strong incompatibilities between the two, mostly (that i've heard about) concerning the symbols stdin, stderr,...,_IO_stderr,etc. stdin, stderr,...were changed from constants to variables, which can cause compiling issues. _IO_stderr is the symbol referring to the constant definition of stderr. there is also a linking issue with object files/libraries compiled with glibc2.0 headers linked on a glibc2.1 system concerning the _IO_stderr symbol. obviously the details here are confusing (to me anyway), so if you are dealing with this stuff, then seek them out. another interesting tidbit is that redhat did not include the f2c or fort77 packages with redhat6.x. so if you have these packages on your redhat6.1 system, then they are probably left over from the redhat5.x install (or some other install), and thus were compiled using the older glibc2.0. this is a problem on your redhat6.x system! to resolve these problems here at unidata, i deleted these packages off our redhat6.x systems, and recompiled the redhat5.2 source rpms (with no modifications) on the 6.x systems. i recommend that you do this also. (the specific source package names are fort77-1.14a-4.src.rpm and f2c-19970805-3.src.rpm). contact me if you need more detail on the procedure; it's not very tricky, and there are a couple shortcuts by using rpm -b (or see the man page). -sandy a sysadmin at unidata Steve Emmerson wrote: > Dean, > > >Date: Thu, 09 Dec 1999 21:14:11 +0000 > >From: "Dean N. Williams" <address@hidden> > >Organization: PCMDI > >To: Steve Emmerson <address@hidden> > >Subject: Re: 19991207: "make nf_test/test" failure: Red Hat Linux 6.1: fort77 > >Keywords: 199912071733.KAA19310 > > In the above message, you wrote: > > > Can you tell me if you are using Red Hat Linux 6.1 or Linux from some > > other company? > > Our Linux is from Red Hat. > > $ uname -a > Linux sunshine.unidata.ucar.edu 2.2.13 #5 SMP Mon Nov 29 12:41:02 MST > 1999 i686 unknown > > > I think the problem with me not being able to run ./ftest > > with fort77 and pgf90 is because of Linux. I'm not sure about the > > version > > 2.2.12-20 on my system and 2.2.13 on your system. It would appear that > > your version is more up-to-date. (Where did you get it? ) > > >From Red Hat. I've CC'ed our sys-admin. He might be able to give you > more details. > > > I am hoping if I get the fort77 to work, then pgf90 will work as well. > > But I > > need to know why your Linux platform builds properly with fort77 and my > > Linux platform croaks. > > Regards, > Steve Emmerson <http://www.unidata.ucar.edu>