Bug#366204: gcc-4.0: dangling symlinks

[Matthias Klose <doko@cs.tu-berlin.de>]

tags 366204 + wontfix
thanks

Florian Schlichting writes:
> Package: gcc-4.0
> Version: 4.0.3-1
> Severity: minor
> 
> gcc-4.0 puts three dangling symlinks on my system - is that meant to be
> the case?

yes, these are resolved by the lib64stdc++6 package; we do not depend
on that package by default, because not everybody needs the 64bit compiler.

> /bin/ls: /usr/lib/gcc/i486-linux-gnu/4.0.3/64/libstdc++.so: No such file or directory
> /bin/ls: /usr/lib/gcc/i486-linux-gnu/4.0.3/64/libgcc_s.so: No such file or directory
> /bin/ls: /usr/lib/gcc/i486-linux-gnu/4.0.3/libgcc_s_64.so: No such file or directory
> 
> Also, now-purged gcc-3.3 and gcc-3.4 have left the following two symlinks:
> /bin/ls: /usr/share/modass/gcc-3.4/gcc: No such file or directory
> /bin/ls: /usr/share/modass/gcc-3.3/gcc: No such file or directory
> 
> this is tigercron's output and I hope I'm not wrong in assuming that
> none of this should be there?

these files were never part of the gcc packages. that's maybe a local
installation or installation from other sources.