On Mon, Mar 20, 2006 at 08:36:05PM -0800, Steve Langasek wrote: > severity 358076 normal > tags 358076 unreproducible > thanks ??? > Huh? Are you really suggesting that the standard C++ compiler has been > unable to find any of its own header files for over a week in unstable, and > no one noticed? That's what the report might lead to assume. I _definitely_ wondered for myself. I have currently three g++ incarnations (3.3, 3.4, 4.0.3) installed and none of these actually let me transform my sources into binaries. The 3.3 and 3.4 versions _do_ find their headers (as indicated in my report) but fail at the linking stage. Apparently, they have no idea which C++ library to link against as all the unresolved symbols come from ``std''. I am strictly on packages from www.debian.org (http://ftp.de.debian.org to be precise). At roughly 03:00 CET today, there were no > I think you will need to provide more detail about what it is you're doing; Anything that will resolve the issue. I can send you /var/lib/dpkg/available if you need that. Or anything the canonical debian tools report. At roughly 03:00 CET today, there was the usual ``<pkg> is already the newest version.'' for either g++-3.3, g++-3.4, and g++-4.0. > g++-4.0 is certainly not unable to find its header files in the general > case, so this bug doesn't qualify as "rendering the package unusable". Over here it does. What I find noteworthy is the fact that ``apt-get install g++-4.0'' did _not_ lead to installing the headers. I had to explicitly invoke apt-get on libstdc++6-4.0-dev to have these installed yet still g++-4.0 does not find them. What's the point in having a C++ compiler without it's headers on a system ? I work with systems where it's actually the other way around: headers first, then the compiler according to gusto. Regards, Christian
Attachment:
signature.asc
Description: Digital signature