Re: [ferret_users] Ferret in Mac 10.8 (Mountain Lion) => Works!

[Russ Fiedler <russell.fiedler@xxxxxxxx>]

Karl, Billy,

Given that Billy was trying to install in /usr/local it's likely that he
was running as root under bash when he set up Ferret rather than his
normal tcsh. Maybe Finstall should ask for the default shell? The other
explanation would be the environment variable SHELL isn't set (this
would be odd).

Russ 

On Tue, 2013-04-30 at 17:23 -0700, Karl Smith - NOAA Affiliate wrote:
> Hi Billy,
> 
> 
> Good to hear.  In step 2 of Finstall it tries to figure out which type
> shell you are using, and make a symbolic link of ferret_paths to
> either ferret_paths.csh (for C-type shells) or ferret_paths.sh (for
> Bourne-type shells).  It sounds like my logic in Finstall needs some
> reworking for Mac.
> 
> 
> Thanks,
> Karl
> 
> 
> 
> 
> On Tue, Apr 30, 2013 at 3:10 PM, William S. Kessler
> <william.s.kessler@xxxxxxxx> wrote:
>         Hi all -
>         
>         There's an oddity in installing Ferret in Mountain Lion. For
>         those who come after ... after a bit of tweaking it appears to
>         work fine. Here's my notes; maybe someone has a better
>         solution.
>         
>         1) I downloaded the 3 gzipped files from
>         http://ferret.pmel.noaa.gov/Ferret/downloads/ferret-mac-os-x-downloads
>         then followed the instructions from
>         http://ferret.pmel.noaa.gov/Ferret/downloads/ferret-installation-and-update-guide
>         
>         2) Finstall steps 1 and 2 appeared to work fine, installing
>         the executables and creating the soft link ferret_paths.
>         
>         3) But then when I tried to "source ferret_paths", it failed
>         with the error "export: Command not found" (repeatedly)
>         After some looking, it appears that the script deduced that I
>         was using a bash shell (I use tcsh).
>         In fact Finstall creates both ferret_paths.sh (for bash) and
>         ferret_paths.csh (for tcsh), but the soft link (in /usr/local)
>         was to the bash version:
>         ferret_paths@ -> ferret_paths.sh
>         
>         The solution is to explicitly:
>         source ferret_paths.csh
>         ... or, you can do as I did before I realized this, and simply
>         edit a version of ferret_paths I had from a previous machine.
>         
>         Now it works! I have not tested it thoroughly, but the basic
>         functions function.
>         
>         Billy K
>         
> 
> 
> 
> 
> -- 
> Karl M. Smith, Ph.D.
> JISAO Univ. Wash. and TMAP/PMEL NOAA
> "The contents of this message are mine personally and do
> not necessarily reflect any position of the Government
> or the National Oceanic and Atmospheric Administration."
>