[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#360504: marked as done (libmudflap0-dev: Broken symlink in /usr/lib64)

Your message dated Sun, 11 Apr 2010 14:30:36 +0000
with message-id <E1O0yBI-0000F5-TD@ravel.debian.org>
and subject line C++ and mudflap packages not built anymore from the gcc-4.1 source
has caused the Debian Bug report #360504,
regarding libmudflap0-dev: Broken symlink in /usr/lib64
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 owner@bugs.debian.org
immediately.)


-- 
360504: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=360504
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: libmudflap0-dev
Version: 4.1.0-1
Severity: minor

This package contains a link

 /usr/lib64/libmudflap.so -> libmudflap.so.0.0.0

This second file is not provided by any file.  Why are there files
being created in /usr/lib64 on a i386 architecture anyway?

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.16
Locale: LANG=C, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)

Versions of packages libmudflap0-dev depends on:
ii  gcc-4.1-base                  4.1.0-1    The GNU Compiler Collection (base 
ii  libc6-dev                     2.3.6-4    GNU C Library: Development Librari
ii  libmudflap0                   4.1.0-1    GCC mudflap shared support librari

libmudflap0-dev recommends no packages.

-- no debconf information

--- End Message ---
--- Begin Message --- 
The C++ and mudflap binary packages are not built anymore from the
gcc-4.1 source package.  Tagging this report as won't fix, and closing
the report.

Please check if the problem is fixed in gcc-4.4 (or gcc-4.5/gcc-snapshot).
If the problem is not fixed, and not yet reported for the new compiler
version(s), open a new report.

--- End Message ---
Reply to: