> > http://bugs.gentoo.org/show_bug.cgi?id=340923 > > > > It's known and fixed. It's not a gcc regression, nor is it > > HPPA-specific (didn't you try to confirm that it was > > HPPA-specific? :) My mistake. I hardly come accross non-hppa specific bugs :) > > > > The reason you're hitting it is that you've keyworded gcc-4.5.2, but > > aren't running a full ~hppa system. vapier doesn't seem to > > acknowledge that this is a reasonable, sensible, or even common > > configuration. > > that's because it is not. there's a difference between running brand > new bleeding edge versions of the toolchain on a stable system all the > time and running them for the stabilization process. inevitably every > gcc/glibc/kernel header upgrade in ~arch breaks a shit ton of stable > packages (and even unstable packages), the vast majority of which will > be fixed by those packages stabilizing a new version as natural > progression by the time the toolchain versions have settled for > stabilization. > -mike Kinda makes sens but it's probably not the right list to discuss. In any case, thanks everybody for the feedback. I'm quite happy this is not a gcc issue ! Guy -- To unsubscribe from this list: send the line "unsubscribe linux-parisc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
