Your message dated Wed, 08 May 2013 15:22:51 +0200
with message-id <518a51ab.2040...@debian.org>
and subject line closing as won't fix
has caused the Debian Bug report #622783,
regarding libgfortran3: Conflicting version between libgfortran and the default 
gfortran compiler
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
622783: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=622783
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libgfortran3
Version: 4.6.0-2
Severity: grave
Justification: renders package unusable

Hello,

I have a package (hdf5) which is built with gfortran.
It is going to use gfortran 4.5 as compiler but will use libgfortran3 
as version 4.6. It is causing the FTBFS reported as #619281
and detailed here:
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48404

So, libgfortran of gcc 4.5 and gcc 4.6 are not fully compatible...

Sylvestre

-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (600, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.38-1-686-bigmem (SMP w/4 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages libgfortran3 depends on:
ii  gcc-4.6-base                  4.6.0-2    The GNU Compiler Collection (base 
ii  libc6                         2.11.2-11  Embedded GNU C Library: Shared lib
ii  libquadmath0                  4.6.0-2    GCC Quad-Precision Math Library

libgfortran3 recommends no packages.

libgfortran3 suggests no packages.

-- no debconf information



--- End Message ---
--- Begin Message ---
closing this one as won't fix, 4.8 behaves the same as 4.7.

--- End Message ---

Reply via email to