NOTICE: This version of the NSF Unidata web site (archive.unidata.ucar.edu) is no longer being updated.
Current content can be found at unidata.ucar.edu.
To learn about what's going on, see About the Archive Site.
On Oct 25, 12:48pm, William Weibel wrote: > Subject: Re: conflicting subroutines (fwd) > A student here was trying to compile a code on an SGI power challenge > and got the following from the link editor: > > > ld: FATAL 12: Object class error (/usr/local/lib/libnetcdf.a): not a 32-bit object. > > He says he was compiling in "32 bit mode", alledgedly to be compatible > with the IMSL library. Is there anything he can do, short of rebuilding > NetCDF on his own? > > Thank-you > Bill > > William Weibel weibel@xxxxxxxxxxxxxx > UCLA Department of Atmospheric Sciences Tel. (310)206-4441 \\\\/ > Los Angeles, CA 90095-1565 Fax (310)206-5219 O-O > U.S.A. | > - > > "Id quod est praestantissimum maximeque optabile omnibus sanis et bonis et > beatis, cum dignitate otium." (The thing which is the most outstanding and > chiefly to be desired by all healthy and good and well-off persons, is > leisure with honour.) Cicero - Pro Sestio, xlv.98 > > |||| | | | | | | | | | | | | | | | | | | | | | | |||| >-- End of excerpt from William Weibel William, Just 'cuz I'm doing a lot of compiling these days, that message is telling you that the netcdf library is not a 32-bit library, whence imcompatible with the 32-bit build underway. I'm guessing that he built the netcdf library himself and did not specify 32-bit mode for that build. The obvious solution would be to rebuild the netcdf library and be sure to use the "-32" flag when doing so. Either that or I'm wrong. Hope this helps. Regards, Matthew -- Matthew H. Koebbe, Ph.D. | "UNLESS someone like you cares a whole Scientific VisLab 408/656-3778 | awful lot, nothing is going to get phaedrus@xxxxxxxxxxxx | better. It's not." http://vislab-www.nps.navy.mil/~phaedrus/ | -- Dr. Seuss (the Lorax)
netcdfgroup
archives: