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 Samuel, re: environment variables listed from 'env' It looks like the environment variables needed to perform a build that incorporates use of MySQL are correct. re: snippit from 'makelog' that shows build of dmbin.k Your makelog output for the build of dmbin.k indicates that it was _not_ built with MySQL support. This seems inconsistent with the environemt variables being set properly _unless_ you built McIDAS before having the full set of environment variables defined. My recommendation at this point is to rebuild your McIDAS distribution in the environment defined by your 'env' listing above: <as 'mcidas'> cd ~mcidas/mcidas2007/src make clobber make all After the re-build finishes, look through makelog and verify that dmbin.k was linked against the MySQL libraries. If it is now built with MySQL support, go ahead and reinstall the code: make install.all The makelog output for dmbin.k should look something like: ./mccomp -O -s -mysql -g77 -o dmbin.k main.o dmbin.o -L. -lxcd -lmcidas -L. -L/usr/X11R6/lib64 -lxcd -lmcidas -lX11 -L. -lsdi -lmcidas -L../netcdf/libsrc -lnetcdf -L. -L../g2clib -lsdi -lmcidas -lgrib2c -L. -L../jasper/src/libjasper/.libs -lsdi -lmcidas -ljasper ../jasper/src/libjasper/.libs/libjasper.a mccomp: Using default optimizations g77 -s -O -o dmbin.k main.o dmbin.o -L. -L. -L/usr/X11R6/lib64 -L. -L../netcdf/libsrc -L. -L../g2clib -L. -L../jasper/src/libjasper/.libs -L/usr/X11R6/lib -L/usr/lib64/mysql -L/usr/X11R6/lib64 -lxcd -lmcidas -lxcd -lmcidas -lX11 -lsdi -lmcidas -lnetcdf -lsdi -lmcidas -lgrib2c -lsdi -lmcidas -ljasper ./jasper/src/libjasper/.libs/libjasper .a -ldl -lmysqlclient -L../zlib -lz -lm Notice the explicit references to '-lmysqlclient' in the link step. Your listing: g77 -s -O -o dmbin.k main.o dmbin.o -L. -L. -L/usr/X11R6/lib64 -L. -L../netcdf/libsrc -L. -L../g2clib L.-L../jasper/src/libjasper/.libs -L/usr/X11R6/lib -lxcd -lmcidas -lxcd -lmcidas -lX11 -lsdi -lmcidas lnetcdf -lsdi -lmcidas -lgrib2c -lsdi -lmcidas -ljasper ../jasper/src/libjasper/.libs/libjasper.a -ldl -lm link dmbin.k: done has no reference to the mysqlclient library, so dmbin.k was not built with MySQL support. Finally, your DECINFO (decinfo.k) output shows that you enabled both GRIB filing and decoding: Processing Data Monitor: DMGRID is active ========================================================================= Decoder Status Configuration File ---------------------------------------------------------------------- GRIB Active GRIBDEC.CFG ... Processing Data Monitor: DMBIN is active ========================================================================= Decoder Status Configuration File ---------------------------------------------------------------------- GRBFILER Active GRBFILER.CFG I strongly recommend that you use only the GRIB filing method after you get dmbin.k built with MySQL support. 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: WTM-677712 Department: Support McIDAS Priority: Normal Status: Closed