[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:
> I did as you instructed: went to ~mcidas/mcidas2005/src and
> executed 'make clobber'

OK.  For reference, 'make clobber' run in the ~mcidas/mcidas2005/src
directory cleans out anything left over from an attempted build.
You will be using this alot until the build is successful.

> A lot of messages scrolled by on the screen.  Then, I
> executed, 'make all' again.  The following is all of what
> appeared on the terminal screen:
> 
> address@hidden 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
> address@hidden src]$

OK, this is what I was expecting on an initial build.

> I went to the ../tcl/unix directory and opened the config.log
> file.  It contained the following:
> 
> 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

The fact that 'configure' checked for 'cc' means that it did not
find gcc.  If it had, the next line in ~mcidas/mcidas2005/tcl/unix/config.log
would have looked like:

configure:642: checking for gcc
configure:755: checking whether the C compiler (gcc -O ) works

> There was nothing else after this.  Maybe there is something
> that I don't have for gcc...?

I think that the PATH you have does not include the installation
directory for gcc.  In Fedora Core, gcc will be found in /usr/bin
_if_ a development environment has been installed.  The thing to
do now is to list out the PATH you have in place:

<login as 'mcidas'>
which gcc

'which' should tell you that gcc can be found in /usr/bin.  If
you get an indication that gcc was not found, it means one of
a couple of things:

- your PATH does not include /usr/bin
- gcc is not installed

To see if gcc is installed, run:

locate gcc

If this comes back blank, it likely means that gcc was not installed.
If 'locate' finds gcc, it means that your PATH is incomplete.  If
this is the case, add the following two lines to your .bashrc file
at the beginning of the file:

PATH=/usr/kerberos/bin:/usr/local/bin:/usr/bin:/bin:/usr/X11R6/bin
export PATH

The easiest thing to do at this point is logoff and login again.
After doing this, recheck to see if gcc is found using 'which':

which gcc

If gcc is still not found, your development environment is likely
incomplete and will have to be updated.

> Hopefully this information helps.

Yes, the output from ~mcidas/mcidas2005/tcl/unix/config.log was very
instructitve.

> Thank you

No worries.

By the way, I am willing to logon to your machine and poke around to
see what I can see if you like.  In order to do this, I would need
your 'mcidas' password; the fully qualified name of your machine;
and for your firewall to allow SSH connections from the unidata.ucar.edu
domain (128.117.140.*).  If you decide that you want me to login, please
send me the password in a different email than the machine name AND
do not reference the machine or account name in the email with the
password.

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


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.