Jeff,
Don't forget to file a PR against gfortran in bugzilla if you
come across any particular problems that can be testcased. The
gfortran developers are actually pretty good about fixing issues
in the compiler once they are aware of the problem. Also, exactly
which fortran 95 and fortran 77 fe
Jack Howarth wrote:
> Jeff,
>The new lammpi and openmpi packages that I maintain now use gcc4
> I also see that raster3d, pdftk, apbs, apbs-mpi, ccp4-onlylibs-dev,
> ccp4, mosflm, mosflm-small, plplot, maloc, maloc-mpi, pdb2pqr and
> tinker use gcc4 as well. Most of those are probably packages
Jeff,
The new lammpi and openmpi packages that I maintain now use gcc4
I also see that raster3d, pdftk, apbs, apbs-mpi, ccp4-onlylibs-dev,
ccp4, mosflm, mosflm-small, plplot, maloc, maloc-mpi, pdb2pqr and
tinker use gcc4 as well. Most of those are probably packages that
are maintained by Willia
David Fang wrote:
>> So the next time we update gcc4, we will have to contend with the
>> breakage of any package that uses gfortran from gcc4.
>> Jack
>>
>
> Hi,
> Would it be possible (and a good idea?) to split the gcc4 package
> into release-branches? e.g. gcc4.0 (cu
Dan,
The point though is that the current gcc4 has a bogus libgfortran.so.1.
So if there are compatibility packages created they will have to be
mapped as...
libgfortran.so.0 -> gcc 4.0.3
libgfortran.so.1 -> gcc 4.1.1
libgfortran.so.2 -> gcc 4.2
The current gcc4 in unstable has a bogus libgfor
On Wed, Jul 12, 2006 at 07:57:38PM -0400, David Fang wrote:
> > So the next time we update gcc4, we will have to contend with the
> > breakage of any package that uses gfortran from gcc4.
> > Jack
>
> Hi,
> Would it be possible (and a good idea?) to split the gcc4 package
> i
> So the next time we update gcc4, we will have to contend with the
> breakage of any package that uses gfortran from gcc4.
> Jack
Hi,
Would it be possible (and a good idea?) to split the gcc4 package
into release-branches? e.g. gcc4.0 (currently 4.0.3), gcc4.1 (currently
4.
As I warned, the gcc developers will be bumping the .so of
libgfortran for the gcc 4.2 release tomorrow...
http://gcc.gnu.org/ml/fortran/2006-07/msg00128.html
So the next time we update gcc4, we will have to contend with the
breakage of any package that uses gfortran from gcc4.
