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

20031103: McIDAS Build Errors under Redhat 9 (cont.)



>From: "Patrick O'Reilly" <address@hidden>
>Organization: UNI
>Keywords: 200310311747.h9VHlZOb021585 McIDAS-X v2002 RedHat 9.0 Linux

Patrick,

>I removed the mcidas2003 directory and have attached the output of the env
>command.

Given that what you are seeing does not match my experience building
under Redhat 9.0 Linux, would it be possible for me to get a login
to your system?  If yes, I will need the logins for 'mcidas' and 'ldm'.
If you want me to setup the McIDAS ADDE remote server, I will also
need 'root'.

Tom

>----- Original Message ----- 
>From: "Unidata Support" <address@hidden>
>To: "Patrick O'Reilly" <address@hidden>
>Cc: <address@hidden>
>Sent: Friday, October 31, 2003 7:34 PM
>Subject: 20031031: McIDAS Build Errors under Redhat 9 (cont.)
>
>
>> >From: "Patrick O'Reilly" <address@hidden>
>> >Organization: UNI
>> >Keywords: 200310311747.h9VHlZOb021585 McIDAS-X v2002 RedHat 9.0 Linux
>>
>> Patrick,
>>
>> >Not going so well.  Of course, it's Friday afternoon, that's why!  I did
>> >what you said.  Didn't make it nearly as far this time.  Isn't that
>perfect?
>>
>> Given that you modified the McIDAS make file the first time around
>> (only by changing the VENDOR setting), and given that you didn't get
>> as far the second time around, I think that the quickest and easites thing
>> to do now is to wipe out the mcidas2003 directory tree and start from
>> scratch:
>>
>> <as 'mcidas'>
>> cd /home/mcidas
>> rm -rf mcidas2003
>> ./mcinstall
>>
>> Please send me the output of 'env' run before you try the build again.
>>
>> Then do the following:
>>
>> cd /home/mcidas/mcidas2003
>> make all VENDOR=-g77
>>
>> If this works follow up with:
>>
>> make install.all VENDOR=-g77
>>
>> >I am copying pertinent info of the unsuccessful build below:
>>
>> What I see is no different than what I see on the 16 workshop systems
>> that have McIDAS built and running.  Please try wiping the entire
>> distribution and starting from scratch.  If you have a new machine,
>> this will be _much_ quicker than trying to troubleshoot a potential
>> typo or munged file.
>>
>> Please let me know the results of the above.
>>
>> Tom
>>
>> >address@hidden src]$ which gcc
>> >/usr/bin/gcc
>> >address@hidden src]$ gcc --version
>> >gcc (GCC) 3.2.2 20030222 (Red Hat Linux 3.2.2-5)
>> >Copyright (C) 2002 Free Software Foundation, Inc.
>> >This is free software; see the source for copying conditions.  There is
>NO
>> >warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR
>PURPOSE.
>> >
>> >address@hidden src]$ which g77
>> >/usr/bin/g77
>> >address@hidden src]$ g77 --version
>> >GNU Fortran (GCC 3.2.2 20030222 (Red Hat Linux 3.2.2-5)) 3.2.2 20030222
>(Red
>> >Hat Linux 3.2.2-5)
>> >Copyright (C) 2002 Free Software Foundation, Inc.
>> >
>> >GNU Fortran comes with NO WARRANTY, to the extent permitted by law.
>> >You may redistribute copies of GNU Fortran
>> >under the terms of the GNU General Public License.
>> >For more information about these matters, see the file named COPYING
>> >or type the command `info -f g77 Copying'.
>> >
>> >
>> >address@hidden src]$ echo $CC
>> >gcc
>> >address@hidden src]$ uname -a
>> >Linux thunder.storm.uni.edu 2.4.20-8smp #1 SMP Thu Mar 13 17:45:54 EST
>2003
>> >i686 i686 i386 GNU/Linux
>> >address@hidden src]$ make all
>> >rm -f cal_init; cp cal_init.sh cal_init; chmod 755 cal_init
>> >rm -f disable_mcidas_gui; cp disable_mcidas_gui.sh disable_mcidas_gui;
>chmod
>> >755 disable_mcidas_gui
>> >rm -f enable_mcidas_gui; cp enable_mcidas_gui.sh enable_mcidas_gui; chmod
>> >755 enable_mcidas_gui
>> >rm -f fx; cp fx.sh fx; chmod 755 fx
>> >rm -f mcidasx; cp mcidasx.sh mcidasx; chmod 755 mcidasx
>> >rm -f mcservsh
>> >Updating mcservsh...
>> >chmod 755 mcservsh
>> >rm -f mcar; cp mcar.sh mcar; chmod 755 mcar
>> >rm -f mccomp; cp mccomp.sh mccomp; chmod 755 mccomp
>> >rm -f tclcomp
>> >sh tclcomp.sh /home/mcidas/tcl ../tcl ../tk tclcomp
>> >tclcomp.sh: Error building Tcl configuration file
>> >tclcomp.sh: Possible compiler error
>> >make: *** [tclcomp] Error 1
>> >
>> >
>> >address@hidden src]$ make all VENDOR=-g77
>> >rm -f tclcomp
>> >sh tclcomp.sh /home/mcidas/tcl ../tcl ../tk tclcomp
>> tclcomp.sh: Error building Tcl configuration file
>> >tclcomp.sh: Possible compiler error
>> >make: *** [tclcomp] Error 1
>> >
>> >address@hidden src]$
>> >
>> >
>> >
>> >SOOOOOOOOO........as you can see things have gone haywire.  I did do a
>"make
>> >clobber" first, but didn't feel like pasting the output of that above.
>In
>> >fact, I removed all the directories created by mcinstall then re-ran it
>to
>> >recreate all the directories/files.  The netCDF settings were previously
>put
>> >in mcidas' .cshrc.  Any guidance would be muchly appreciated.
>> >
>> >
>> >
>> >Patrick
>> >
>> >
>> >
>> >
>> >----- Original Message ----- 
>> >From: "Unidata Support" <address@hidden>
>> >To: "Patrick O'Reilly" <address@hidden>
>> >Cc: <address@hidden>
>> >Sent: Friday, October 31, 2003 3:08 PM
>> >Subject: 20031031: McIDAS Build Errors under Redhat 9
>> >
>> >
>> >> >From: "Patrick O'Reilly" <address@hidden>
>> >> >Organization: UNI
>> >> >Keywords: 200310311747.h9VHlZOb021585 McIDAS-X v2002 RedHat 9.0 Linux
>> >>
>> >> Patrick,
>> >>
>> >> >I'm trying to build McIDAS 2003 on a RedHat 9 system.  I am using
>gcc/g77
>> >> >compilers (or trying to), and hence have made VENDOR=-g77 change to
>the
>> >> >makefile.
>> >>
>> >> OK.  You can do that, or you can specify the VENDOR use on the command
>> >line:
>> >>
>> >> <as 'mcidas'>
>> >> cd mcidas2003/src
>> >> make all VENDOR=-g77
>> >> make install.all VENDOR=-g77
>> >>
>> >> >I have set environment for netCDF as explained in documentation.
>> >>
>> >> Just to make sure, these should look like:
>> >>
>> >> # Defines needed for netCDF build using gcc/g77
>> >> setenv CC gcc
>> >> setenv CPPFLAGS "-DNDEBUG -Df2cFortran"
>> >> setenv CFLAGS -O
>> >> setenv FC g77
>> >> setenv FFLAGS "-O -Wuninitialized -fno-automatic"
>> >> setenv CXX
>> >>
>> >> >I don't understand errors I am getting, and have attached the makelog
>and
>> >> >the errors that I see on my terminal in file make.errors (which aren't
>in
>> >> >the makelog).  Can anyone shed some light on this for me?
>> >>
>> >> >I also have the
>> >> >Portland f90 compiler handy if that would work better.
>> >>
>> >> The gcc/g77 combination of compilers should work fine.  I have not
>> >> built with the Portland Group f90 compiler, so I can't say what
>> >> kinks there might be if you try it.
>> >>
>> >> >Has McIDAS 2003 even
>> >> >been built successfully on RH 9?
>> >>
>> >> Yes, in fact we are using McIDAS-X v2003 built with gcc/g77 on RedHat
>> >> 9.0 Linux systems in the current series of training workshops.
>> >>
>> >> From the following snippit you sent in:
>> >>
>> >> ...
>> >>
>> >> >Making `libjpeg.a' in /home/mcidas/mcidas2003/hdf/hdf/jpeg
>> >> >make[5]: Entering directory `/home/mcidas/mcidas2003/hdf/hdf/jpeg'
>> >> >DNDEBUG -Df2cFortran  -c -o jcapimin.o jcapimin.c
>> >> >make[5]: DNDEBUG: Command not found
>> >>
>> >> ...
>> >>
>> >> It looks like the CC environment variable wasn't set.  What appears to
>be
>> >> happening is an attempt to compile jcapimin.o with no C compiler
>> >specified:
>> >>
>> >> DNDEBUG -Df2cFortran  -c -o jcapimin.o jcapimin.c
>> >>
>> >> instead of:
>> >>
>> >> gcc DNDEBUG -Df2cFortran  -c -o jcapimin.o jcapimin.c
>> >>
>> >> So, list out your environment and see if you have CC defined/defined
>> >correctly.
>> >> If you do, it may be the case that you started the build once without
>> >having
>> >> defined CC, etc., and then defined them later.
>> >>
>> >> I would recommend that after you verify that CC, etc. is defined
>correctly
>> >> you do the following:
>> >>
>> >> <as 'mcidas'>
>> >>
>> >> cd ~mcidas/mcidas2003/src
>> >> make clobber
>> >> make all VENDOR=-g77
>> >> make install.all VENDOR=-g77
>> >>
>> >> >Thanks for the help.
>> >>
>> >> No worries.
>> >>
>> >> Tom
>> >>
>>
>>***************************************************************************
>*
>> ><
>> >> Unidata User Support                                    UCAR Unidata
>> >> (303)497-8643                                                  P.O. Box
>> >> address@hidden                                   Boulder, CO
>>
>>> -------------------------------------------------------------------------
>-
>> >> Unidata WWW Service
>> >>
>**************************************************************************
>> >
>>
>>
>****************************************************************************
><
>> Unidata User Support                                    UCAR Unidata
>> (303)497-8643                                                  P.O. Box
>> address@hidden                                   Boulder, CO
>> --------------------------------------------------------------------------
>> Unidata WWW Service
>>
>****************************************************************************
><
>
>------=_NextPart_000_00B0_01C3A1F7.96C8EC50
>Content-Type: text/plain;
>       name="env.txt"
>Content-Transfer-Encoding: quoted-printable
>Content-Disposition: attachment;
>       filename="env.txt"
>
>SSH_AGENT_PID=3D17604=0A=
>SUPPORTED=3Den_US.UTF-8:en_US:en=0A=
>HOSTNAME=3Dthunder.storm.uni.edu=0A=
>HOST=3Dthunder.storm.uni.edu=0A=
>SHELL=3D/bin/csh=0A=
>TERM=3Dxterm=0A=
>CPPFLAGS=3D-DNDEBUG -Df2cFortran=0A=
>MCHOME=3D/home/mcidas=0A=
>MCCOMPRESS=3DTRUE=0A=
>GROUP=3Dldm=0A=
>USER=3Dmcidas=0A=
>LS_COLORS=3Dno=3D00:fi=3D00:di=3D00;34:ln=3D00;36:pi=3D40;33:so=3D00;35:b=
>d=3D40;33;01:cd=3D40;33;01:or=3D01;05;37;41:mi=3D01;05;37;41:ex=3D00;32:*=
>.cmd=3D00;32:*.exe=3D00;32:*.com=3D00;32:*.btm=3D00;32:*.bat=3D00;32:*.sh=
>=3D00;32:*.csh=3D00;32:*.tar=3D00;31:*.tgz=3D00;31:*.arj=3D00;31:*.taz=3D=
>00;31:*.lzh=3D00;31:*.zip=3D00;31:*.z=3D00;31:*.Z=3D00;31:*.gz=3D00;31:*.=
>bz2=3D00;31:*.bz=3D00;31:*.tz=3D00;31:*.rpm=3D00;31:*.cpio=3D00;31:*.jpg=3D=
>00;35:*.gif=3D00;35:*.bmp=3D00;35:*.xbm=3D00;35:*.xpm=3D00;35:*.png=3D00;=
>35:*.tif=3D00;35:=0A=
>SSH_AUTH_SOCK=3D/tmp/ssh-XX8UxAE9/agent.17603=0A=
>HOSTTYPE=3Di386-linux=0A=
>USERNAME=3Dmcidas=0A=
>McINST_ROOT=3D/home/mcidas=0A=
>MCTABLE_WRITE=3D/home/mcidas/data/ADDESITE.TXT=0A=
>PATH=3D/home/mcidas/bin:/usr/local/bin:/usr/bin:/bin:/usr/X11R6/bin:/usr/=
>X11R6/bin=0A=
>PWD=3D/home/mcidas=0A=
>address@hidden
>LANG=3Den_US.UTF-8=0A=
>GDMSESSION=3DDefault=0A=
>CXX=3D=0A=
>SSH_ASKPASS=3D/usr/libexec/openssh/gnome-ssh-askpass=0A=
>MCDATA=3D/home/mcidas/workdata=0A=
>SHLVL=3D2=0A=
>HOME=3D/home/mcidas=0A=
>OSTYPE=3Dlinux=0A=
>MCTABLE_READ=3D/home/mcidas/workdata/MCTABLE.TXT;/home/mcidas/data/ADDESI=
>TE.TXT=0A=
>CFLAGS=3D-O=0A=
>FC=3Dg77=0A=
>VENDOR=3Dintel=0A=
>MACHTYPE=3Di386=0A=
>LOGNAME=3Dmcidas=0A=
>XCD_disp_file=3D/home/mcidas/workdata/DECOSTAT.DAT=0A=
>MCGUI=3D/home/mcidas/bin=0A=
>LESSOPEN=3D|/usr/bin/lesspipe.sh %s=0A=
>MCPATH=3D/home/mcidas/workdata:/home/mcidas/data:/home/mcidas/help=0A=
>CC=3Dgcc=0A=
>DISPLAY=3D:0.0=0A=
>G_BROKEN_FILENAMES=3D1=0A=
>FFLAGS=3D-O -Wuninitialized -fno-automatic=0A=
>XAUTHORITY=3D/home/mcidas/.Xauthority=0A=
>GTK_RC_FILES=3D/etc/gtk/gtkrc:/home/mcidas/.gtkrc-1.2-gnome2=0A=
>SESSION_MANAGER=3Dlocal/thunder.storm.uni.edu:/tmp/.ICE-unix/17603=0A=
>GNOME_DESKTOP_SESSION_ID=3DDefault=0A=
>DESKTOP_STARTUP_ID=3D=0A=
>COLORTERM=3Dgnome-terminal=0A=
>WINDOWID=3D29360392=0A=
>
>------=_NextPart_000_00B0_01C3A1F7.96C8EC50--
>



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.