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.
Hi, re: > I replaced both makefiles, keeping an eye on file sizes as my marker. I'm > assuming you meant for the second makefile to go > into /home/mcidas/mcidas2021/xcd/src/makefile so that's where I put it. Exactly. re: > Make all xrd as well as make install.all install.xrd both went off without > error, looks like you got it! One of the things that was not being done was removal of the: ~mcidas/mcidas2021/jasper/build-jasper directory, so one of the updates in the main makefile was aimed at addressing this. Since this directory was not being removed during a 'make clobber', it is possible that it staying around was the cause of libjasper.a being saved in the build-jasper/lib directory instead of a build-jasper/lib64 directory. Can you check your build so see which library subdirectory was created for your most recent installation? NB: this would only have changed if you did the 'make clobber' after installing the two reworked 'makefile's and then did a full build and installation: <as 'mcidas'> -- extract and copy the main makefile to ~mcidas/mcidas2021/src -- extract and copy the XCD makefile to the ~mcidas/mcidas2021/xcd/src directory cd ~mcidas/mcidas2021/src make clobber make all xrd && make install.all install.xrd OR make all xrd install.all install.xrd re: > As an aside, I noticed I have a /home/mcidas/mcidas directory, nothing in > there except for an empty directory "data." Based on the timestamps though > it looks like ~/mcidas is getting made on each install. Is there a reason > for these empty dirs? For an installation on a server, this directory is used for debug output and some other things. For an installation like yours and mine, this directory is largely unused, but it being there is still needed to match SSEC's installation procedure. Cheers, Tom -- **************************************************************************** Unidata User Support UCAR Unidata Program (303) 497-8642 P.O. Box 3000 address@hidden Boulder, CO 80307 ---------------------------------------------------------------------------- Unidata HomePage http://www.unidata.ucar.edu **************************************************************************** Ticket Details =================== Ticket ID: SDI-707505 Department: Support McIDAS Priority: High Status: Open =================== 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.