[RFC] Fortran search path for intrinsic includes and modules

[Steve Kargl]

On Thu, Nov 24, 2005 at 03:04:36AM -0500, Jakub Jelinek wrote:
> On Fri, Nov 18, 2005 at 11:54:18AM -0800, Richard Henderson wrote:
> > On Fri, Nov 18, 2005 at 01:25:27PM -0500, Jakub Jelinek wrote:
> > > 	* Make-lang.in (fortran/f95-lang.o): Pass -DGFC_INCLUDE_DIR.
> > > 	* f95-lang.c (gfc_init): Append GFC_INCLUDE_DIR to search
> > > 	path.
> > 
> > I think it seems reasonable.  I have no opinion on whether finclude
> > ought to go adjacent to the include directory; I'm fine with it 
> > being buried under the lib directory.  But this is something for
> > Fortran folks to decide.
> 
> Any word from the Fortran crowd on this?
> 
> Is the patch ok for trunk?
> 

On my system, I have
kargl[208] ls lib/gcc/i386-unknown-freebsd7.0/4.1.0
crtbegin.o      crtend.o        include/        libgcc.a        libgcov.a
crtbeginS.o     crtendS.o       install-tools/  libgcc_eh.a

Creating an finclude directory here would permit
multiple installations of gfortran where each gfortran
will search the right directory.  OTOH, the fortran file
you want to install will become more difficult to find.

I suppose ${PREFIX}/finclude is also a possibility, but installation
of multiple versions of gfortran becomes difficult.  For the general
user, this is probably not an issue;  and, the fortran file is
easy to find.   

Go with ${PREFIX}/finclude unless pbrook objects.

-- 
Steve