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: Eirh-Yu Hsie <address@hidden> >Organization: CU/CIRES >Keywords: 200405061548.i46Fm1tK006094 McIDAS 2003 build Hsie, >We have a Summer field study on early July, 2004. Owen Cooper want to add >data set to our ADDE server. Before I do anything, I thindk this is a good >time to upgrade my McIDAS package from 2002 to 2003. I run into compilation >problem. > >The machine is Sun 3500 running OS 5.8 (blizzard). The compiler is Sun >compiler suite version 6. I remember running into the same problem before. >My McINST_ROOT >is set to "/home/mcidas/solaris". It is a soft link to >/home/mcidas/solaris2003. The source is in "/home/mcidas/mcidas2003". The >error messages are: > >... >... >Making `all' in directory /home/mcidas/mcidas2003/netcdf/cxx > >CC -c -I../libsrc -I. -DNDEBUG netcdf.cpp >CC -c -I../libsrc -I. -DNDEBUG ncvalues.cpp >ar cru libnetcdf_c++.a netcdf.o ncvalues.o >ranlib libnetcdf_c++.a >CC -c -I../libsrc -I. -DNDEBUG nctst.cpp >CC -o nctst nctst.o libnetcdf_c++.a -L../libsrc -lnetcdf > >Returning to directory /home/mcidas/mcidas2003/netcdf > >cd ../hdf && make allnofortran >Making `allnofortran' in /home/mcidas/mcidas2003/hdf/hdf >Making `libjpeg.a' in /home/mcidas/mcidas2003/hdf/hdf/jpeg >c jcapimin.c >sh: c: not found >*** Error code 1 (ignored) >c jcapistd.c >sh: c: not found >*** Error code 1 (ignored) >c jctrans.c The problem is in the environment variables you did or did not set before starting the build. The configure script that builds the Makefile for the jpeg stuff is dumb. It defaults to using 'c' as the C compiler. Setting needed environment variables insures that this does not happen. The list of environment variables you should set before building McIDAS are listed in: Review System-specific Notes and Warnings http://my.unidata.ucar.edu/content/software/mcidas/2003/mcx/warnings_mcx.html Here is the set that should work for your 'VENDOR' environment: setenv CC /opt/SUNWspro/bin/cc setenv CPPFLAGS -DNDEBUG setenv CFLAGS -O setenv FC /opt/SUNWspro/bin/f77 setenv FFLAGS "-O -erroff=WDECL_LOCAL_NOTUSED" # "-erroff=..." turns # off an ignorable warning. # Your compiler may differ. setenv CXX " " setenv F90 " " Note that setting CXX and F90 to a blank stops the build of the netCDF C++ and F90 interfaces. Neither of these is used by McIDAS, so this does not hurt anything. ... >I need your help. Set the environment variables as indicated above in your shell-specific definition file (e.g. .cshrc for C shell, etc.), make sure that the settings are active (e.g., source ~/.cshrc, etc.), clobber the first build attempt (e.g., 'make clobber') and then start the build again. Cheers, Tom -- NOTE: All email exchanges with Unidata User Support are recorded in the Unidata inquiry tracking system and then made publically 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.