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.
Dave, > > If you would, please move /usr/X11R6/bin to the head of PATH and try again > > (after a "make distclean", of course -- better yet, remove the entire > > directory hierarchy and unpack from scratch). > Done. Either this worked, or switching to the t-shell from the Bourne shell > worked, or some of each. (I usually use a t-shell, but I keep forgetting how > to redirect both standard output and standard error to create configure.log > and make.log files, so I switched to the Bourne shell. The PATH looks the > same as for the t-shell, though. In any case, v6.13.1.7 installed > successfully with no further interventions, and I’m keeping an eye on it. Excellent! > > Also, having "./" near the head of PATH can cause problems. I recommend > > leaving it out of PATH altogether -- or at least moving it to end. > > So you live with specifying “./“ in front of all local scripts (etc.) in > directories not in PATH? That sounds like a chronic, low-level headache. :-( Not really. Scripts that get used a lot always reside in a directory that's in PATH -- so I tend to specify "./" only once on the command-line if I need to execute a truly local script. This is an old habit from the days when pranksters would replace, say, ls(1) with a local script and then ask an administrator to change to that directory to help them debug a problem. > Thanks for the intervention! You're most welcome. Please keep us apprised. Regards, Steve Emmerson Ticket Details =================== Ticket ID: EJF-472056 Department: Support LDM 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.