Re: path for bison-1.28 in .bashrc file

[Hans Aberg]

On 19 Aug 2010, at 23:02, SMITH, JONATHAN WYNN. (GSFC-6133) wrote:

> 1)      I have just recently installed bison-1.28.  What path is  
> appropriate in the .bashrc file (i.e export ...=...) so other  
> programs will know here bison is?
>
> 2)      Is bison-1.28 appropriate for to build ncap and ncap2 for  
> nco.  Nco-4.0.2 has not compiled for me, and I am seeing if the  
> absence of bison is the problem.

To begin with, 1.28 is so old that probably few here will remember it.  
If you can, try to install latest stable version, but first installing  
M4, which it will need.

The location of the install depends on the system, but on BSD systems  
(like Mac OS X), it is /usr/local/.

Then .bashrc is only read when creating a non-login shell (like X11  
and xterm on Mac OS X). So I have:
  source ~/.profile

On Mac OS X, the file .profile is read when starting Terminal. The  
paths I use correspond to the stuff below, though I have a more  
complicated script that only adds a path if not already there (as when  
invoking a shell within a shell). I'm not sure LIBPATH is used for  
anything, but that is where the libraries are.

PATH=/usr/local/bin:/usr/local/X11R6/bin:/bin:/sbin:/usr/bin:/usr/ 
sbin:/usr/X11R6/bin
MANPATH=/usr/local/share/man:/usr/local/man:/usr/share/man:/usr/X11R6/ 
man
INFOPATH=/usr/local/share/info:/usr/local/info:/usr/share/info
LIBPATH=/usr/local/lib:/usr/lib:/usr/X11R6/lib

# Export changed paths:
export PATH
export MANPATH
export INFOPATH
export LIBPATH