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.
>From: Unidata User Support <address@hidden> >Organization: Unidata Program Center/UCAR >Keywords: McIDAS-X 7.8 addendum mapcoord.c Hi, If you are not the appropriate contact for Unidata McIDAS-X related issues, or if you personally did not download Unidata McIDAS since October 4, please pass this email along the appropriate person. The addresses of this email were seen to have downloaded Unidata McIDAS-X 7.8 with addendum 7.803 (released on October 4). This release/addendum contained modifications to the C source routine mapcoord.c which were incorrect. The the bad code will cause segmentation violations when running POINT source contouring routines (e.g., SFCCON, RAOBCON, etc.) with invocations that do not specify the MAP projection. Here are some of examples for illustration: - will not work - SFCCON T USA LATEST RAOBCON Z 500 NA 12 - will work - SFCCON T USA LATEST PRO=CONF SFCCON T USA LATEST PRO=MERC RAOBCON Z 500 NA 12 PRO=MERC You should, therefore, update your source distributions with the newly modified version of mapcoord.c and then rebuild the applications dependent on it. Here is the easiest way to accomplish this task: 1) login to the machine(s) where you build McIDAS-X as the user 'mcidas' 2) re-grab the addendum containing 7.803 code: cd mcidas7.8/update ftp ftp.unidata.ucar.edu <user> umcidas <pass> XXXXXX cd unix/780/bugfix binary get mcupdate.tar.Z quit 3) extract mapcoord.c from the mcupdate.tar.Z compressed tarball: zcat mcupdate.tar.Z | tar xvf - ../src/mapcoord.c 4) rebuild and reinstall applications: cd ../src touch mapcoord.c (to make sure that its timestamp is newer than libmcidas.a) make mcx If you using a vendor-supplied Fortran compiler (i.e., not gcc/f2c) you should be done (the new executables will still be linked to the ones in ~mcidas/bin). If you are using gcc/f2c, you will need to relink the relinked applications to the installation bin directory. The absolute easiest way to do this is: make install.bin I chose to not make a new addendum with the mapcoord.c modifications since the number of users that downloaded distributions that needed modification is small. Sorry for the hassle... Tom Yoksas