Ludovic Brenta writes: > Matthias Klose writes: > > peter green writes: > >> >Next GCC 4.2 will be prepared to be included in unstable; a current > >> >issue is http://sourceware.org/bugzilla/show_bug.cgi?id=4302 which has > >> >to be resolved before g++-4.2 can enter unstable.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > >> That bug is marked as "resolved invalid" with a reply "Those symbols are > >> for glibc. Why do they have libstdc++ version names? I think it is a gcc > >> bug. Please open a gcc bug instead." > >> > >> Does anyone know if such a bug has been filed and if so where? > > > > the upstream gcc-4_1-branch doesn't include the ldbl changes. > > So? Does that mean the bug doesn't affect GCC 4.1? In that case, I > believe Peter is correct that the bug must be resolved before GCC 4.2 > can enter unstable. Do you agree? see above. what needs clarifying? if you have any pointers where the problem actually is, please say so. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
