Your message dated Sun, 9 Jul 2006 12:28:01 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Bug#357062: closed by Matthias Klose <[EMAIL PROTECTED]> (Re:
libstdc++6-4.0-dev: 32-bit includes missing on amd64 (no
/u/i/c++/4.0/i486-linux-gnu))
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: libstdc++6-4.0-dev
Version: 4.0.3-1
Severity: normal
/usr/include/c++/4.0/i486-linux-gnu seems to have gone missing,
breaking g++ -m32 (which zeroc-ice inappropriately uses, but that's a
separate bug).
Could you please restore it?
Thanks!
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable')
Architecture: amd64 (x86_64)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.15
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)
Versions of packages libstdc++6-4.0-dev depends on:
ii g++-4.0 4.0.3-1 The GNU C++ compiler
ii gcc-4.0-base 4.0.3-1 The GNU Compiler Collection (base
ii libc6-dev 2.3.6-3 GNU C Library: Development Librari
ii libstdc++6 4.0.3-1 The GNU Standard C++ Library v3
libstdc++6-4.0-dev recommends no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Aaron M. Ucko writes:
> retitle 357062 libstdc++6-4.1-dev: 32-bit includes missing on amd64 (no
> /u/i/c++/4.1/i486-linux-gnu)
> reassign 357062 libstdc++6-4.1-dev 4.1.1-7
> reopen 357062
> thanks
>
> [EMAIL PROTECTED] (Debian Bug Tracking System) writes:
>
> > Version: 4.0.3-4
> >
> > at least they are present in this version.
>
> So they are; thanks. However, in the meantime, gcc-4.1 seems to have
> developed an identical bug, hence the reassignment and reopening. :-/
"seems to have" is too weak. the headers are there, libstdc++6-4.1-dev
never had the problem. closing the report again.
--- End Message ---
