Branden, first of all I would like to apologize for the duplicate bug report which I filed on this subject.
On 04-Oct-08 15:36, Branden Robinson wrote: > Okay, I'm tired of getting griped at about this issue by various people, so > I looked up why I originally made this change in the first place. :) > xfree86 (4.2.1-5) unstable; urgency=low > [...] > * debian/control: > - add Build-Dependency on libstdc++5-dev (for libGLU in xlibmesa3-glu) > [...] > - C++ ABI 1.02 transition / Mesa 5.0 awareness: > + xlibmesa-glu-dev depends on libstdc++5-dev and libc6-dev | libc-dev > -- Branden Robinson <[EMAIL PROTECTED]> Tue, 21 Jan 2003 12:02:40 -0500 > > It looks like I added the build-dep on libstdc++5-dev (which I later > broadened to include an alternative on libstdc++-dev) because I needed to > add a regular dependency to xlibmesa-glu-dev. > > Generally, if you're shipping a -dev package that depends on a C library > -dev package, your source package depends on that C library as well, to > build. > > The fact that libstdc++ (some real package providing it, rather) is > build-essential is persuasive to me, and I'd be happy to drop it. > > *However*, we have a magical mystical C++ ABI shuffle going on. GCC 3.2 > provides libstdc++5-dev. GCC 3.3 provides libstdc++5-3.3-dev. GCC 3.4 > provides libstdc++6-0-dev. > > For xlibmesa-glu-dev's Depends: line to be accurate, don't I need to > preferentially build-depend on the same C++ library? Why does xlibmesa-glu-dev still preferentially depend on 'libstdc++5-dev'? > It has been my understanding that sarge is supposed to use the GCC 3.3 C++ > ABI, and not GCC 3.4's. But I may be wrong, as I cannot find any such > delcaration at <URL: http://release.debian.org/sarge.html >. I am certainly not entitled to give any advice on release issues, but I am quite sure that the C++ ABI from gcc-3.3 will be used for sarge. The archive is not (yet) clean with respect to gcc-3.4. More than 600 bug reports with patches have been filed to the BTS to resolve the FTBFS issues with gcc-3.4. About two thirds of those patches have already been accepted by the maintainers and uploaded to the archive. The number of packages which do not build with gcc-3.4 is decreasing every day but currently there are still more than 200 packages which FTBFS with gcc-3.4. Nevertheless, the Build-Depends (and also the Depends of xlibmesa-glu-dev) on the old libstdc++5-dev from gcc-3.2 is outdated and should be dropped in any case. If you do not like to drop it for some reason, please consider to add '[!amd64]' to the (Build-)Depends on libstdc++5-dev because otherwise autobuilding of xfree86 fails since we do not have gcc-3.2 and libstdc++5-dev on amd64. Regards Andreas Jochens
