>From: Patrick Dills <address@hidden> >Organization: UCAR/COMET >Keywords: 200407020423.i624NgaW002282 McIDAS-X build Hi Patrick, re: build was successful on gizmo >That's great, I'm impressed (but not the least surprised) the build worked >for you. Was really starting to feel jinxed. Still scratching my >head over what happened when I tried the compiling/building with >gcc/g77. The only difference I see in our approaches is you explicitly >indicated VENDOR=-g77 in the 'make mcx' command line, whereas I had tried >to hardwire "VENDOR=-g77" in the mcidas2003/src 'makefile'. Specifying VENDOR=-g77 on the make invocation command line is entirely equivalent to editing the McIDAS makefile and setting VENDOR there, so this is not the difference. >Sorry about the 'slowness' of gizmo. Disappointed we did not break the >snail record though ;-) The snail record at UPC was set on a very old IRIX machine. This puppy was so slow that I would start a build, go home, and not check on its progress until the next morning! >Would love to move to one of our faster Suns. >Recall that we were stuck with 'gizmo' since it was one of the few >systems we have with a static IP, which unfortunately I need to access >the NESDIS ADDE polar-sat server. OK. >I'm giving serious consideration though >to moving the entire build to a Linux platform, isolating 'mcidas-x' from >the competition we have now with other processes running on 'gimzo', e.g. >ldm, datastreme, gempak, etc.. I have put together very fast/capable machines for the RMTCs at the Universidad de Costa Rica and the Caribbean Institute for Meteorology and Hydrology for very little money: UCR - dual Athlon 2600+, 2 GB RAM, 80 GB HD, 320 GB RAID, 128 MB video, CDRW, keyboard, mouse, monitor -- $1700 CIMH - dual Athlon 2800+, 3 GB RAM, 80 GB HD, 500 GB RAID, 128 MB video, DVD+-RW, keyboard, mouse, monitor -- $2100 >I tried finishing the 'install' process this AM...but as luck would have >it, ran into yet another hurdle it seems. > >On the 'make install.mcxall', I'm getting: > >gizmo: 34 % make install.mcxall >make: ERROR: no directory: /pub/mcidas/mcidas04/bin >make: ERROR: no directory: /pub/mcidas/mcidas04/lib >make: ERROR: no directory: /pub/mcidas/mcidas04/tcl >make: ERROR: no directory: /pub/mcidas/mcidas04/lib/gui >make: ERROR: no directory: /pub/mcidas/mcidas04/inc >make: ERROR: no directory: /pub/mcidas/mcidas04/data >make: ERROR: no directory: /pub/mcidas/mcidas04/data/tutorial >make: ERROR: no directory: /pub/mcidas/mcidas04/admin >make: ERROR: no directory: /pub/mcidas/mcidas04/savedata >make: ERROR: no directory: /pub/mcidas/mcidas04/workdata >make: ERROR: no directory: /pub/mcidas/mcidas04/help >make: ERROR: no directory: /pub/mcidas/mcidas04/man >make: ERROR: no directory: /pub/mcidas/mcidas04/man/man3 >make: If your environment is OK, try 'make rootdirs' >make: *** [env_dir] Error 1 > >Do I need to create these directories first, or run 'make rootdirs' as the >output suggests ? Hmm... Well, the environment that is in place for your McIDAS login is different from the one in place when I did the build. The difference has to be in the definition of the McINST_ROOT environment variable. This is defined as: McINST_ROOT=/pub/mcidas/mcidas03 for me (I am still logged on) -- and this is wrong (!!). I should have set it to be: McINST_ROOT=/pub/mcidas/mcidas04 which is what I am betting it is set for you. >Noticed I had reset my "McINST_ROOT" path in my .cshrc file, which I did >before running 'install.mcxall'. That's it. >thanks again Tom for all the help, Since I built McIDAS-X v2004 with McINST_ROOT set incorrectly, I am doing the following: o redefine McINST_ROOT source ~/.cshrc o wipe out the Tcl/Tk portion of the build: cd ~/mcidas2004/tcl/unix make distclean cd ~/mcidas2004/tk/unix make distclean cd ~/mcidas2004/src rm tclcomp .built* o and redo the build (only the Tcl/Tk stuff will be rebuilt, so this won't take another 4 hours): cd ~/mcidas2004/src make rootdirs make mcx VENDOR=-g77 o install v2004: make install.mcxall As I close this note, 'make mcx VENDOR=-g77' is running. The rest of the build/install will be finished as soon as gizmo is able :-) Cheers, Tom -- 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.
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.