Re: [gentoo-dev] glibc-2.8 / gcc-4.3 build failures
On Monday 09 June 2008, Mike Frysinger wrote: > it seems packages are failing when built with glibc-2.8 and/or > gcc-4.3. these are issues in the package, not the toolchain. > previous versions were lazy and included API "bleeding" which > packages took advantage of. with these newer versions, things bleed > less means those packages break. > > some common examples: > - code not including limits.h yet using defines from it > - code using GNU-specific features but not defining _GNU_SOURCE for > it - maybe some other stuff > > please refrain from assigning to toolchain. if you have questions, > feel free to ask. > -mike Just for reference, there are the following tracker bugs for ebuilds failing with either of the two. Please mark build failures as blockers of those. # [tracker] GCC 4.3 porting https://bugs.gentoo.org/show_bug.cgi?id=198121 # [TRACKER] ebuilds failing to build against sys-libs/glibc-2.8 https://bugs.gentoo.org/show_bug.cgi?id=225459 Robert signature.asc Description: This is a digitally signed message part.
Re: [gentoo-dev] glibc-2.8 / gcc-4.3 build failures
On Monday 09 June 2008, Rémi Cardona wrote: > Mike Frysinger a écrit : > > please refrain from assigning to toolchain. if you have questions, feel > > free to ask. > > Is there a howto for users/developers when migrating to glibc 2.8? > Something other than a ChangeLog (too much detail) or a NEWS file > (usually not enough detail) ? not really. write your code to use the write API as documented rather than what happens to work ;). i imagine as the list of packages broken stabilizes, one could glean the common threads, but since you're asking for info that depends on the info, we're chicken pucked at this point in time. -mike signature.asc Description: This is a digitally signed message part.
Re: [gentoo-dev] glibc-2.8 / gcc-4.3 build failures
Mike Frysinger a écrit : please refrain from assigning to toolchain. if you have questions, feel free to ask. (too lazy to look for it, as we already have our hands full with other library breakages) Is there a howto for users/developers when migrating to glibc 2.8? Something other than a ChangeLog (too much detail) or a NEWS file (usually not enough detail) ? Thanks -- Rémi Cardona LRI, INRIA [EMAIL PROTECTED] [EMAIL PROTECTED] -- gentoo-dev@lists.gentoo.org mailing list
[gentoo-dev] glibc-2.8 / gcc-4.3 build failures
it seems packages are failing when built with glibc-2.8 and/or gcc-4.3. these are issues in the package, not the toolchain. previous versions were lazy and included API "bleeding" which packages took advantage of. with these newer versions, things bleed less means those packages break. some common examples: - code not including limits.h yet using defines from it - code using GNU-specific features but not defining _GNU_SOURCE for it - maybe some other stuff please refrain from assigning to toolchain. if you have questions, feel free to ask. -mike signature.asc Description: This is a digitally signed message part.