Bug#358076: ...

2006-03-23 Thread Christian E. Boehme
On Wed, Mar 22, 2006 at 10:15:40PM -0800, Steve Langasek wrote: Ok, this is pretty much an unsupported configuration in Debian. Debian policy assumes, for instance, that any symlinks within a single top-level directory can be made relative symlinks: e.g., /usr/include/X11 -

Bug#358076: ...

2006-03-23 Thread Christian E. Boehme
On Thu, Mar 23, 2006 at 04:12:51PM +0100, Matthias Klose wrote: hmm, I don't see it as a bug. the nice thing is that you can unpack old deb's on other places and just use them. Not with the path resolution policy I was describing. It starts out with an absolute path name rooted at /usr and

Bug#358076: g++-4.0: fails to locate std C++ headers (eg, typeinfo)

2006-03-21 Thread Christian E. Boehme
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?

Bug#358076: ...

2006-03-21 Thread Christian E. Boehme
On Tue, Mar 21, 2006 at 05:49:43PM -0800, Steve Langasek wrote: Then you're obviously doing something wrong, but you haven't actually told us what you're doing, which makes it difficult to help you debug it. Well, as indicated earlier, I checked the binaries of the g++ driver versions for

Bug#358076: g++-4.0: fails to locate std C++ headers (eg, typeinfo)

2006-03-20 Thread Christian E. Boehme
Package: g++-4.0 Version: 4.0.3-1 Severity: grave Justification: renders package unusable g++ (or cpp, for that matter) is not able to find the standard C++ headers and terminates with (example: typeinfo) ``error: typeinfo: No such file or directory'' although /usr/include/c++/4.0.3/typeinfo