John Levon wrote: > On Wed, Dec 04, 2002 at 10:09:11AM +0100, Lars Gullik Bjønnes wrote: > >> Most distributions have added some "vendor patches" that fix this >> problem. So IMHO it is a vendor problem. >> >> RH f.ex. does not have this problem. (and suse do have it) > > it's a buggy suse patch. clean 3.2 tarball is fine. I've asked people > to report bug to suse to but nobody has said they've done so
I just did. Nobody really said it is a SuSE bug so far, I thought it were a gcc bug.
