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 Alan, re: > Been a few days since we last communicated. I have since > installed gcc and have been able to get the process further > along---much, much more output showing things being checked, > etc. I will append the /src/makelog file and the > /hdf/config.log files for you see. OK. I have edited out most of the makelog and config.log output in this reply. > Could be that I have the > gcc, but the C++ compiler is not functional--hard to tell--so > much printout. McIDAS does not use C++ interfaces for any of the packages it includes (e.g., zlib, hdf, netcdf, etc.). Because of this we require that the CXX Unix environment variable be set to the empty string (" ") so that none of the 'configure' scripts will attempt to build C++ interfaces. > First the makelog file: > > ######################################### > Sun Mar 26 16:59:26 EST 2006: BUILD INIT > ########################################## > > ./configure --prefix=/home/mcidas > creating cache ./config.cache > checking for top-level source-directory > /home/mcidas/mcidas2005/netcdf > checking for m4 preprocessor > checking for m4... m4 > checking m4 flags... -B10000 > checking for xlc... no > checking for c89... c89 > checking C compiler "c89"... works > checking how to make dependencies... false > checking for CC... no > checking for cxx... no > checking for c++... no > checking for g++... no > checking for gcc... gcc > checking C++ compiler "gcc"... configure: warning: gcc failed > on test program > configure: warning: Could not find working C++ compiler This tells me that your environment is not quite setup correctly. The reason I say this is that the Unix environment variable CXX should be set to an empty string so that C++ interfaces for various packages included with the McIDAS distribution don't get built (McIDAS does not use any C++ code, just C and Fortran). The 'mcidas' account preparation instructions have you unpack the distribution and then include an 'if' statement in your shell definition file (e.g., .bashrc if you are using Bash) that will load environment variable definitions from ~mcidas/admin/mcidas_env.sh. One of the environment variables defined in mcidas_env.sh is CXX, and it is set to the empty string. The fact that configure tried to find a working C++ compiler suggests that CXX is not set in your environment. > checking for f90... no > configure: warning: Could not find working Fortran-90 compiler The environment variable definitions in ~mcidas/admin/mcidas_env.sh also set the Unix environment variable F90 to a blank string, and configure would use this fact to not try to find a working F90 compiler. ... > checking whether gcc and cc understand -c and -o together... yes > checking how to run the C++ preprocessor... /usr/bin/cpp > configure: error: C++ preprocessor "/usr/bin/cpp" fails sanity > check > See `config.log' for more details. > configure /home/mcidas/mcidas2005/hdf: FAILED The inability to find a working C++ compiler is the error that is causing your build to cease prematurely. Setting of the CXX environment variable to the empty string would cause the configure script for the HDF portion of the build to not try and build the C++ interface. > So, perhaps this will point a little further along. Please send me the listing of the environment in which you are attemtping to build McIDAS: <as 'mcidas'> env <- run the 'env' command and send us the output What you could do at this point to test to see if the build would work if your environment was correct is: <login as 'mcidas'> CXX=" " F90=" " CC=gcc VENDOR=-g77 export CXX F90 CC VENDOR cd ~mcidas/mcidas2005/src make clobber make all > Thanks, Tom No worries. I think you are close to having a functional development environment. Once you do, the McIDAS build should be simple. 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: MET-935016 Department: Support McIDAS Priority: Normal Status: Closed