port PATH handling

[Kevin Ballard]

On Jan 29, 2007, at 1:24 PM, Michael Sternberg wrote:

> I'm testing to set a fortran dependency for port netCDF (this is a  
> library which may be built with an optional fortran interface).  I  
> have difficulty convincing port(1) to find the fortran compiler in  
> $PATH.
>
> Trying to use a commercial compiler (intel fortran), I source its  
> dotfiles interactively (to augment $PATH etc.), then run:
>
> 	port -dk install netcdf +ifort
>
> This fails because "configure" when run under port claims it cannot  
> find the fortran compiler.  However, when I run the exact same  
> command manually (as root), it succeeds (diff attached).
>
> Does port(1) clean out $PATH ??

If you look at /opt/local/etc/ports/ports.conf, at the bottom is a  
list of environment variables to keep. You may want to try setting  
that to PATH.

-- 
Kevin Ballard
http://kevin.sb.org
eridius at macports.org
http://www.tildesoft.com


-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.macosforge.org/pipermail/macports-users/attachments/20070129/fcdfbe0a/attachment.html