[Debian-med-packaging] Please consider bin-NMUs of certain gfortran-using packages on mips/mipsel
Kevin B. McCarty
kmccarty at debian.org
Mon May 5 19:10:03 UTC 2008
Hi Release Team,
as I mentioned previously , a bug in gfortran 4.3 [2,3] caused some
FORTRAN code using SIN() / COS() functions to be miscompiled on mips and
mipsel with -O1 or greater. Thanks to Jakub Jelinek and Matthias Klose,
this bug should now be fixed in version 4.3.0-4 of Debian's gfortran-4.3
The following source packages in "main" were built with gfortran-4.3
prior to 4.3.0-4 and appear to be affected by the bug. Could you please
consider scheduling bin-NMUs of these packages, with a dep-wait on
# a bin-NMU is apparently only needed on mips:
# a bin-NMU appears to be needed on both mips and mipsel:
The following packages in "contrib" and "non-free" also appear to be
affected, but I don't know whether packages in those sections can be
automatically bin-NMUed. Therefore I also CC their maintainers. Please
keep them in CC regarding this question.
# In contrib (only on mips; ifeffit has never been built on mipsel)
# Note: a newer version of ifeffit, 2:1.2.10a-5, needs to be built on
# mips anyway so there is no point in doing a bin-NMU of ifeffit.
# In non-free on both mips and mipsel:
# Note: a newer version of scilab, 4.1.2-5, needs to be built on
# mips and mipsel anyway so there is no point in doing a bin-NMU of
The above lists are based on re-running my script from , plus manual
review of the buildd logs for packages that are newer than they were at
the time of my previous email.
Uninteresting caveats: It is conceivable there could be a few false
positives (for binaries that combine FORTRAN and C code and use sincos()
within the C portion) but I think this is unlikely and not worth the
trouble to weed them out. There may also be a couple other false
positives for packages whose buildd logs were not available but which
were already built with gfortran-4.3 4.3.0-4. But it shouldn't hurt
anything to do a bin-NMU in either of those cases.
Finally, note that I would not have detected any source package that is
affected but which builds only object files (*.o), static libraries,
and/or binaries statically linked against libm or libgfortran.
Again, I think it's unlikely that there exists such a source package.
Kevin B. McCarty <kmccarty at gmail.com>
GPG: public key ID 4F83C751
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 252 bytes
Desc: OpenPGP digital signature
Url : http://lists.alioth.debian.org/pipermail/debian-med-packaging/attachments/20080505/8aaa6168/attachment.pgp
More information about the Debian-med-packaging