This is the mail archive of the fortran@gcc.gnu.org mailing list for the GNU Fortran project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: changing build dependencies in a distribution from g77 to gfortran


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.

It already happened.


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

Nope. The module files for the standard headers (including Fortran standard headers and the OpenMP module) was decided to be ${prefix}/ lib/gcc/${target-triplet}/${version}/${multilib}/finclude because it depends on both the target, GCC version and multilib settings.


Now, I agree with Jane: while you don't want to put any other headers in there, you need to come up with something :)

FX


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]