>From: Anthony James Wimmers <address@hidden> >Organization: UVa >Keywords: 200006161438.e5GEchT14323 McIDAS-X 7.6 Linux Tony, >I'm back on task with this mcidas installation. Since we last "talked" I and at least two of my sites have built McIDAS-X 7.6x on RedHat 6.2 Linux. >The last problem we had, >if you remember, was with agetserv. Right, the error was that 'agetserv' could not be run "No such file or directory". To me, this means that agetserv is either munged, not installed, or was never successfully built. My first suspicion is that the version of f2c, libf2c.a, and/or f2c.h that you are trying to use is not the correct one for RedHat 6.x. For my Linux users convenience, I put these files in the unix/760/fortran directory of the passworded McIDAS FTP account (forgive me if we have been down this road before, but I am answering this from home after a long day of scraping paint (stripper fumes :o). The reason that I am suspicious is that use of the wrong f2c/libf2c.a will result in "something" being built for Fortran routines, but they will not run. Even if you did grab these files (hopefully in binary mode), you could still be linking against the incorrect f2c library. Check your LD_LIBRARY_PATH and make sure that the directory into which your copy of libf2c.a (/usr/local/lib) is the first in your LD_LIBRARY_PATH: export LD_LIBRARY_PATH=/usr/local/lib:/lib:/usr/lib Also, make sure that f2c.h gets copied to /usr/local/include (you may have to create this directory!), and f2c gets copied to /usr/local/bin AND that this directory is the on in which f2c is found when you try to run it. >To answer your last question, the >group TOPO *was* set to the datalocation LOCAL-DATA. OK. >Did you answer Jennie >about that, or did we just let it go after this message? The last correspondence I had with either of you two was the one in which I noted that that agetserv might be munged or missing. If you remembered, I offered to logon to the PC if it was accessible over the net and get things rolling. The offer still stands. Tom
NOTE: All email exchanges with Unidata User Support are recorded in the Unidata inquiry tracking system and then made publicly available through the web. If you do not want to have your interactions made available in this way, you must let us know in each email you send to us.