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

[McIDAS #MET-935016]: McIDAS - Cannot get mcunpack to execute -- keep getting message to define McINST_ROOT

Hi Alan,

re:
> Busy day at the UGa yesterday.

No worries.  In looking through all that you did, I would say
that it is pretty definitive that your machine does not have
gcc installed.  Given this, I would also guess that you do not
have other packages needed to build McIDAS installed.  Your
system administrator needs, therefore, to install a full development
environment before you can proceed.

> Have worked this morning on
> your last set of recommendations, which did reveal that I did
> not have gcc.
> 
> In executing 'locate gcc' as user 'mcidas' I learned that I
> did not have that package for the devt. environment.  So, per
> instructions on the screen, I logged in as root and executed
> 'updatedb'.  I logged out and logged back in as user 'mcidas'.


Running updatedb only updates the database of installed packages,
it does not install new packages (i.e., it updates the database that
locate uses).

> When using 'locate gcc' I observed:
> 
> [mcidas@Constellation ~]$ locate gcc
> /lib/libgcc_s-4.0.2-20051126.so.1
> /lib/libgcc_s.so.1
> /home/mcidas/mcidas2005/zlib/nt/Makefile.gcc
> /home/mcidas/mcidas2005/gzip/vms/Makefile.gcc
> /home/mcidas/mcidas2005/gzip/amiga/Makefile.gcc
> /usr/lib/gcc-lib
> /usr/lib/openoffice.org1.9.104/program/libsalhelpergcc3.so.3
> /usr/lib/openoffice.org1.9.104/program/libjvmaccessgcc3.so.3
> /usr/lib/openoffice.org1.9.104/program/libucbhelper3gcc3.so
> /usr/lib/openoffice.org1.9.104/program/libuno_cppuhelpergcc3.so.3
> /usr/lib/openoffice.org1.9.104/program/libgcc3_uno.so
> /usr/lib/openoffice.org1.9.104/program/libsalhelper3gcc3.so
> /usr/lib/openoffice.org1.9.104/program/libi18nutilgcc3.so
> /usr/lib/openoffice.org1.9.104/program/libstlport_gcc.so
> /usr/lib/openoffice.org1.9.104/program/libuno_salhelpergcc3.so.3
> /usr/lib/openoffice.org1.9.104/program/libjvmaccessgcc3.so
> /usr/lib/openoffice.org1.9.104/program/libsalhelpergcc3.so
> /usr/lib/openoffice.org1.9.104/program/libuno_salhelpergcc3.so
> /usr/lib/openoffice.org1.9.104/program/libuno_cppuhelpergcc3.so
> /usr/lib/openoffice.org1.9.104/program/libi18nregexpgcc3.so
> /usr/lib/openoffice.org1.9.104/program/libcppuhelpergcc3.so
> /usr/lib/openoffice.org1.9.104/program/libcppuhelpergcc3.so.3
> /usr/lib/openoffice.org1.9.104/program/libcomphelp4gcc3.so
> /usr/lib/openoffice.org1.9.104/program/libcppuhelper3gcc3.so
> /usr/lib/openoffice.org1.9.104/program/libvos3gcc3.so
> /usr/libexec/gcc
> /usr/libexec/gcc/i386-redhat-linux
> /usr/libexec/gcc/i386-redhat-linux/4.0.2
> /usr/libexec/gcc/i386-redhat-linux/4.0.2/cc1
> /usr/sbin/libgcc_post_upgrade
> /usr/share/doc/libgcc-4.0.2
> /usr/share/doc/libgcc-4.0.2/COPYING.LIB
> /usr/share/ghostscript/Resource/CMap/HKgccs-B5-H
> /usr/share/ghostscript/Resource/CMap/HKgccs-B5-V
> /usr/share/ghostscript/Resource/ac14/CMap/HKgccs-B5-H
> /usr/share/ghostscript/Resource/ac14/CMap/HKgccs-B5-V
> /usr/share/locale/C/LC_MESSAGES/msgcc
> /usr/share/locale/fr/LC_MESSAGES/msgcc
> /usr/share/locale/pt/LC_MESSAGES/msgcc
> /usr/share/locale/es/LC_MESSAGES/msgcc
> /usr/share/locale/de/LC_MESSAGES/msgcc
> /usr/share/locale/it/LC_MESSAGES/msgcc

When I run 'locate gcc' on my Fedora Core 4 machine and count
the number of entries listed using:

locate gcc | wc -l

I get ALOT more entries than your listing, and one of them is
/usr/bin/gcc.

> When I executed 'which gcc' I obtained the message that the
> path did not seem to be found:
> 
> [mcidas@Constellation ~]$ which gcc
> /usr/bin/which: no gcc in
> (/usr/kerberos/bin:/usr/local/bin:/usr/bin:/bin:/usr/X11R6/bin)

gcc should be installed in /usr/bin.  Since /usr/bin is included in
your PATH, it indicates that gcc is not installed on your machine.

> I then changed the path per your instructions by modifying the
> .bashrc file and the logging out, logging back in as user
> 'mcidas'.

This would not help since the directory that should contain the
gcc executble was already included in your PATH.

> For the record, the .bashrc reads:
> 
> 
> [mcidas@Constellation ~]$ cat .bashrc
> # .bashrc
> PATH=/usr/kerberos/bin:/usr/local/bin:/usr/bin:/bin:/usr/X11R6/bin
> export PATH
> # User specific aliases and functions
> 
> # McINST_ROOT and VENDOR non-conforming shell definitions
> McINST_ROOT=/home/mcidas
> VENDOR=-g77
> export McINST_ROOT VENDOR
> if [ -d $HOME/admin/mcidas_env.csh ]; then
> source $HOME/admin/mcidas_env.csh
> fi
> 
> # Source global definitions
> if [ -f /etc/bashrc ]; then
> . /etc/bashrc
> fi
> [mcidas@Constellation ~]$

OK, looks good.

> I then went to mcidas2005/src and executed 'make clobber'.
> 
> I then tried to rebuild and obtained the same errors:
> 
> 
> [mcidas@Constellation src]$ make all
> make: NOTICE: VENDOR compiler selection: -g77
> 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
> [mcidas@Constellation src]$

This is the same error as before.  It is expected since gcc is
not installed on your machine.
 
> The output from the config.log file was also the same--no gcc
> being found, apparently.
> 
> This file contains any messages produced by compilers while
> running configure, to aid debugging if configure makes a mistake.
> 
> configure:579: checking whether to use symlinks for manpages
> configure:591: checking whether to compress the manpages
> configure:614: checking whether to add a package name suffix
> for the manpages
> configure:642: checking for gcc
> configure:672: checking for cc

Yup.

> Let me see what I need to do on this end to get the remote
> access you mentioned--that may save a lot of steps and is a
> good idea.  I will try gaining access to this computer from
> another one so that I know how to do it and can give you all
> the correct info that you asked for.

At this point, my logging in as 'mcidas' would only serve to
verify the steps that you have already run.  Unless I am totally
offbase in my observations that you do not have a development
environment installed, the next bit is the installation of a
full development environment by 'root'.

> Thanks,

No worries.


Cheers,

Tom
****************************************************************************
Unidata User Support                                    UCAR Unidata Program
(303) 497-8642                                                 P.O. Box 3000
address@hidden                                   Boulder, CO 80307
----------------------------------------------------------------------------
Unidata HomePage                       http://www.unidata.ucar.edu
****************************************************************************


Ticket Details
===================
Ticket ID: MET-935016
Department: Support McIDAS
Priority: Normal
Status: Closed