[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

20050314: McIDAS build error on Fedora Core 2 64-bit Linux (cont.)

>From: Unidata Support <address@hidden>
>Organization: UCAR/Unidata
>Keywords: 200503111622.j2BGM8v2022849 McIDAS Fedora Core 2 64-bit

Hi Mark,

I'm back... this time with a fix.

I updated the McIDAS-X distribution with the latest distribution of
HDF-4, HDF 4.2r1;  modified the McIDAS 'makefile'; and modified the
McIDAS compilation script, 'mccomp.sh'.

- upgraded to HDF 4.2r1

- build the HDF portion of the distribution correctly:

  - use new flags for the HDF configure script (makefile)
  - modified the Linux defaults file ~mcidas/mcidas2004/hdf/config/linux-gnu
    to include a reference to '-lm' in its definition of LIBS

- compile mnmx.for with no optimization (to get around the g77 bug)
  (mccomp.sh)

- update 'makefile' to include SSEC McIDAS v2004b code to build the
  netCDF, JPEG, ZLIB, HDF, Tcl, and TK portions of the build silently
  (output now gets logged in ~mcidas/mcidas2004/makelog)

So, you should grab the newly cut distribution, v2004c, and us it instead
of v2004b:

<as 'mcidas'>
cd ~mcidas
rm -rf mcidasx2004.tar.Z mcidas2004

ftp ftp.unidata.ucar.edu
  <user> XXXXXX
  <pass> XXXXXX
  cd unix/2004
  binary
  get mcidasx.tar.Z
  get mcinstall
  quit

chmod +x mcinstall

-- make sure that the Unix environment variable McINST_ROOT is defined;
   this is typically /home/mcidas

./mcinstall

cd mcidas2004/src

make mcx
make install.mcx


I just built v2004c on a variety of systems here at the UPC including
Fedora Core 2 32-bit, Fedora Core 3 32-bit, Fedora Core 3 64-bit,
Solaris SPARC 5.9, Solaris x86 5.9, FreeBSD 4.10, OSF/1 5.1, IRIX64
6.5, and MacOS-X 7.8.0 Darwin.

Please let me know if this distribution builds correctly for you now.

Cheers,

Tom
--
NOTE: All email exchanges with Unidata User Support are recorded in the
Unidata inquiry tracking system and then made publicly 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.