On Sun Oct 12 01:27:38 2014 Anthony G. Basile <bluen...@gentoo.org> wrote: > On 10/11/14 16:28, Rich Freeman wrote: > > On Sat, Oct 11, 2014 at 4:07 PM, M. Ziebell <ziebell_ma...@posteo.de> > > wrote: > > > But if anyone would ask me to stabilize gcc-4.8 I would say "amd64 > > > ok". > > > > > If there is general consensus that this is going to be a stable target > > it might make sense to start running mixed stable+gcc-4.8 systems as > > widely as possible for feedback. > > > > -- > > Rich > > > > Looking at the following two trackers: > > #461954 - GCC 4.8 porting > > #516152 - sys-devel/gcc-4.8.? stabilization > > > I would say the following still should be fixed: >
<snip> > #500944 - =media-libs/x264-0.0.20111220 segmentation faults during > initialization of x264 encoder in x264_cqm_init () from > /usr/lib/libx264.so.120 Most likely already fixed in current stable x264-0.0.20140308 > > #500966 - >=net-libs/webkit-gtk-2.2.4 USE=-webgl - > ./.libs/libwebkitgtk-1.0.so: undefined reference to > `_ZN3JSC21GenericTypedArrayViewINS_14Float32AdaptorEE6createEj' Not a blocker for gcc-4.8 stabilization - I can reproduce this bug with gcc-4.7. > > #513386 - net-libs/webkit-gtk-2.4.3 - ./.libs/libwebkitgtk-3.0.so: > undefined reference to `_ZNSt6chrono12steady_clock3nowEv@GLIBCXX_3.4.17' > Maybe documentation + news item would be enough? -- Alexander Tsoy
