changing build dependencies in a distribution from g77 to gfortran

[Steve Kargl]

On Fri, Jan 26, 2007 at 07:07:09PM +0200, Janne Blomqvist wrote:
> And just to make your life even more miserable, there will be ABI 
> breakage in libgfortran in the not too far future. IIRC 4.2 bumped the 
> so version from 4.1, and it will probably happen again for 4.3. 
> Hopefully we'll get symbol versioning for 4.3 and thus get some 
> semblance of ABI stability, courtesy of yours truly, but the patch has 
> stalled due to some minor problems and I'm quite busy with Real Life(TM) 
> at the moment so I haven't had time to look into it. :(

I was wondering about the status of versioning patch.  I had
problems with it on FreeBSD and tried fixing it (following the
wiki instruction) but could not make it work.  I suppose I
should go back and try again.

> Matthias Klose wrote:
> 
> >I'm aware that the fortran ML may not be the ideal forum to discuss
> >this; maybe we can move these conversations to distribution specific
> >lists after some time.
> 
> Another thing you might want to consider is that now that you're 
> providing a Fortran 95 compiler, presumably other developers will want 
> to add F95 libraries that provide module files (say, the F90 interface 
> to netcdf, lapack95 etc.). Coming up with a policy for these .mod files 
> (where should they go?) might be easier now than a few years later when 
> you have a few dozen libraries doing it their own way. IIRC the default 
> is to put them into the normal include directories, but since they are 
> somewhat system(?) and compiler version dependent you might want to put 
> them somewhere else. Or then not, it's up to you of course.

I think the .mod should not be mingled with C/C++ .h files. Locally,
I place these files in /usr/local/modules and ${HOME}/modules.  I'm
sure others will have different opinions of this.

-- 
Steve