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

20040305: McIDAS-x Build Errors under Redhat 7.2



>From: =?ISO-8859-1?Q?Angel_Luque_S=F6llheim?= <address@hidden>
>Organization: University of Balear Islands in Spain
>Keywords: 200403051638.i25GcKrV026412 McIDAS build RedHat 7.2 Linux gcc/g77

Hi Angel,

>I`m Angel Luque from the University of Balear Islands in Spain.
>I`m trying to build McIDAS 2003 on RedHat 7.2 system. I am using gcc/g77 
>compilers. 
>I have set the mcidas account and the environment for netCDF as 
>explained in documentation
>
>-- Vendor supplied gcc and g77 --
>    setenv CC gcc
>    setenv CPPFLAGS "-DNDEBUG -Df2cFortran"
>    setenv CFLAGS -O
>    setenv FC g77
>    setenv FFLAGS "-O -Wuninitialized -fno-automatic"
>    setenv CXX

These are correct.

>In the attached system file are listed the linux and compilers 
>characteristics.
>
>I have made ./mcinstall
>make all VENDOR=-g77 and that was the farther point I got.
>
>I dont`t understand errors I am getting, and have attached the last 
>results I see on my terminal in the make-end file. The makelog file is 
>very long and it look like the process was almost finishing before it 
>fails.

The build process is failing on the building of mcwish, but I do
not see the mcwish build log messages in the makelog output you
sent me.

>Any help will be very apreciated.

>make[1]: Leaving directory `/home/mcidas/mcidas2003/tk/unix'
>compile main.c:                 done
>compile mcterm.c:               done
>compile macro3.fp:              done
>link    macro3:                 done
>compile mcenv.cp:               done
>link    mcenv:                  done
 ...
>compile wishcrex.c:             done
>compile wisherrh.c:             done
>compile wishinit.c:             done
>compile wishmcid.c:             done
>compile wishrglb.c:             done
>compile wishutil.c:             done
>compile wishxinf.c:             done
>compile wishxwin.c:             done
>compile tkAppInit.c:            done
>link    mcwish:                 FAILED (See '/home/mcidas/mcidas2003/src/makel
> og' for details.)
>
>make: *** [mcwish] Error 1

Here is where I need the makelog output for the attempted build of
'mcwish.

>[mcidas@multicelula ~]$ gcc --version
>2.96
>[mcidas@multicelula ~]$ g77 --version
>GNU Fortran 0.5.26 20000731 (Red Hat Linux 7.1 2.96-98)
>Copyright (C) 1997 Free Software Foundation, Inc.
>For more version information on components of the GNU Fortran
>compilation system, especially useful when reporting bugs,
>type the command `g77 --verbose'.

I have built McIDAS using these compilers many times with no problems.
I have not recently built under RedHat 7.2, however, since we no
longer have a RedHat 7.2 system at Unidata.

>
>##########################################
>Fri Mar  5 13:07:13 CET 2004: BUILD BEGIN
>##########################################
>
>./mccomp -O -g77 -I. -I../netcdf/libsrc -I../hdf/hdf/src -I../hdf/mfhdf/libsrc
>  -I../jpeg -I../zlib -c convdlmc.c
>mccomp: Using default optimizations

 ...

>rm -f convdlmc.o
>./mccomp -O -g77 -I. -I../netcdf/libsrc -I../hdf/hdf/src -I../hdf/mfhdf/libsrc
>  -I../jpeg -I../zlib -c m0mxmn.c
>mccomp: Using default optimizations
>rm -f m0mxmn.o
>gcc -c -I/usr/X11R6/include -O -I. -I../netcdf/libsrc -I../hdf/hdf/src -I../hd
> f/mfhdf/libsrc -I../jpeg -I../zlib m0mxmn.c
>compile        m0mxmn.c:               done

Is there no logging output after this?  The log output from above show that
you got well past this portion of the build, but your makelog output
does not reflect this.

Can you retry your make to see if you get complete logging this time:

<as 'mcidas'>
cd mcidas2003/src
make clobber
make all VENDOR=-g77

All I need in the way of log output is the end of the messages you see
on the screen, and the last 100 or so lines of ~mcidas/mcidas2003/src/makelog.

Cheers,

Tom Yoksas
--
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.