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.
Kassim, > attached are two sets of config and make log files > > The difference between the files is that the files with '_gcc' in the > filename were produced after i typed: > export CC='/usr/local/bin/gcc' > > i ran > make distclean > after setting the environment variable and before running ./configure The "configure" script is getting bad options from its execution of the getconf(1) utility. Is the system in question a 64-bit one or a 32-bit one? If it's 32-bit, what gcc(1) options are necessary to obtain 64-bit longs, 64-bit pointers, and a 64-bit "off_t" C type? If you don't need a large product-queue (see step 4 in <http://www.unidata.ucar.edu/software/ldm/ldm-6.6.5/basics/source-install-steps.html#build>), then you might try the equivalent of the following (adjust for your user-shell): make distclean CC=/usr/local/bin/gcc ./configure --disable-max-size >configure.log 2>&1 && make >make.log 2>&1 && echo OK > thanks so very much > IT is a bureaucratic wasteland here and i dont have many support options You have my sympathies. > --kassim;kl Regards, Steve Emmerson Ticket Details =================== Ticket ID: MAC-518090 Department: Support LDM Priority: Normal Status: On Hold