Package: libgrib-api-dev Version: 1.9.16-2 Severity: important Dear Maintainer,
to have a coherent system of lib*-dev in fortran, all of them should be built with the same version of fortran compiler. Because of a weird design of fortran, modules are not portable. Modules produced with a compiler are not compatible with another compiler or another version of the same compiler. At present in sid, default gfortran (package "gfortran") points to gfortran-4.7 (gcc-4.7) but libgrib-api-dev is built with gfortran-4.6. This is clearly, because latest version of libgrib-api-dev was released before (Mon, 16 Apr 2012) the upgrade from gcc from 4.6 to 4.7 (Mon, 07 May 2012) but I wonder whether an (pseudo?)automatic procedure should be devised to rebuild all the necessary libs when a new version of gfortran implies a backward incompatibility. In any case, at present, a program that uses both libgrib-api-dev and, for instance, libnetcdf-dev (currently built with gfortran-4.7) cannot be built at all in sid. Alberto -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages libgrib-api-dev depends on: ii libgrib-api-1.9.16 1.9.16-2 libgrib-api-dev recommends no packages. libgrib-api-dev suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
