This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.
>From: Ricky Irving <address@hidden> >Organization: SATEPS >Keywords: 199910251755.LAA07454 McIDAS-X Linux Ricky, >As always thanks for the help and guidance....unfortunately the problems >continue. No problem. >It appears that the make script generates an error when I use the >version of TCLCOMP that you provided. This is odd. >There appears to be three (3) versions >of the script TCLCOMP. Yours (TCLCOMP.SH.UNIDATA) SSEC (TCLCOMP.SH.SSEC) and >one that I am calling TCLCOMP.org that was in the mcidas7.6/src directory. This is even more strange. Where did the TCLCOMP.SH.SSEC file come from if not from the original 7.6 distribution itself? What I am driving at is whether or not modifications to your 7.6 distribution were made before I sent you mine. If so, then there might be some strange interaction between the various modified sources. >I have attached all three versions. I get the most success with the TCLCOMP.org >(as it were) and the makelog file from my last e-mail I think was output from >its use. Yes, I could tell that. The output was incorrect, however, since the directories that contain the Tcl and Tk shared libraries were not being searched during the link of mcwish. This is why the link failed. >All the libraries that are referenced already exist. I have also attached the >makelog file. The first build [08:51:18] is a result of using the tclcomp.org >script. I believe that this must be the same one you sent yesterday. >The third build (last in the makelog file) is from using the >tclcomp.unidata. Awaiting further guidance. Just for verification sake, I need to ask: o what was your procedure in using the different versions of tclcomp, etc. For instance, did you do a 'make clobber' inbetween so that the build was started fresh each time, or did you do something else (and if so what) o how do you have the following Unix environment variables defined: CC, CFLAGS, FC, FC, FFLAGS, CXX >Thanks I will offer to you what I offer to my sites: if you give me a login as 'mcidas', I can troubleshoot the problem quicker and provide a solution for your setup. >########################################## >Tue Oct 26 08:51:18 EDT 1999: BUILD BEGIN >########################################## > >./tclcomp ./mccomp -g -I. -I../netcdf/libsrc -I../tcl -I../tcl/generic -I../tk > -I../tk/generic -c wishcrex.c >gcc -c -O -ansi -D_GNU_SOURCE -I/usr/X11R6/include -g -DHAVE_GETCWD=1 -DHAVE_U > NISTD_H=1 -DUSE_TERMIOS=1 -DHAVE_SYS_TIME_H=1 -DTIME_WITH_SYS_TIME=1 -DHAVE_T > M_ZONE=1 -DHAVE_TM_GMTOFF=1 -DHAVE_TIMEZONE_VAR=1 -DHAVE_ST_BLKSIZE=1 -DSTDC_ > HEADERS=1 -DNEED_MATHERR=1 -DRETSIGTYPE=void -DHAVE_SIGNED_CHAR=1 -DHAVE_SYS_ > IOCTL_H=1 -DHAVE_UNISTD_H=1 -DHAVE_LIMITS_H=1 -DSTDC_HEADERS=1 -DHAVE_SYS_TIM > E_H=1 -DTIME_WITH_SYS_TIME=1 -I. -I../netcdf/libsrc -I../tcl -I../tcl/generic > -I../tk -I../tk/generic wishcrex.c >compile wishcrex.c: done ... >wishcrex.o: In function `Tk_CreateWindowFromExisting': >/home/mcidas/mcidas7.6/src/wishcrex.c:371: undefined reference to `Tk_CreateWi > ndowFromPath' ... >collect2: ld returned 1 exit status >link mcwish: FAILED All of these undefined references are due to the non-searching of the Tcl and Tk libraries that should have been created at the beginning of the build. This portion of the build is not logged into ~mcidas/mcidas7.6/src/makelog; the messages would be posted to the screen. >X-Content-Name: tclcomp.org > >#!/bin/sh > ># if this is Solaris, need to add a run-time path when linking ># <<<<< UPC mods 981130 >>>>> - added Linux and OSF1 to list ># of OSes needing RUNTIME_PATH ># >RUNTIME_PATH= >case `uname -sr` in >"SunOS 5."*) RUNTIME_PATH="-R /home/mcidas/tcl/lib";; >"Linux 2."*) RUNTIME_PATH="-Wl,-rpath,/home/mcidas/tcl/lib";; >OSF1*) RUNTIME_PATH="-Wl,-rpath,/home/mcidas/tcl/lib";; >IRIX*) RUNTIME_PATH="-Wl,-rpath,/home/mcidas/tcl/lib";; >HP-UX*) RUNTIME_PATH="-Wl,+b,/home/mcidas/tcl/lib";; >esac This looks like a portion of version of tclcomp.sh that I sent you, not the one that comes with McIDAS-X 7.60. In the email I got, however, this version was not complete. >Content-Description: tclcomp.sh.ssec > >#!/bin/sh ># ># Copyright(c) 1998, Space Science and Engineering Center, UW-Madison ># Refer to "McIDAS Software Acquisition and Distribution Policies" ># in the file mcidas/data/license.txt ># ># $Id: tclcomp.sh,v 1.10 1999/04/23 18:39:17 beckys Exp $ ># > ># save program name ># >prog=`basename $0` > ># make sure we got the correct number of arguments ># >if [ $# -ne 4 ]; then > echo "Usage: $prog tcldir tclsrc tksrc target" 1>&2 > exit 1 >fi OK, this looks like the original, unmodified SSEC 7.60 version. >X-Content-Name: tclcomp.sh.unidata > >#!/bin/sh ># ># Copyright(c) 1998, Space Science and Engineering Center, UW-Madison ># Refer to "McIDAS Software Acquisition and Distribution Policies" ># in the file mcidas/data/license.txt ># ># $Id: tclcomp.sh,v 1.10 1999/04/23 18:39:17 beckys Exp $ ># > ># save program name ># >prog=`basename $0` > ># make sure we got the correct number of arguments ># >if [ $# -ne 4 ]; then > echo "Usage: $prog tcldir tclsrc tksrc target" 1>&2 > exit 1 >fi This one looks like the full version that I sent you. I extracted it from your email and did a diff between it and the version in my distribution and see that they are identical. Given the above listings, I would say that you should get the furthest using the last version of tclcomp.sh as that one is the one that I include in my distribution. Please let me know if you would like me to poke around in the version you are trying to build to see what could be wrong. Tom