[Bug faq/333] Do not report build errors in bugzilla!

["sergstesh at yahoo dot com" <sourceware-bugzilla at sourceware dot org>]

------- Additional Comments From sergstesh at yahoo dot com  2009-11-27 16:51 -------
(In reply to comment #88)
> Maintainers and developers, I bet you are wondering why you end up having to
> close so many open bogus bugs that are related to build errors. That's because
> there does not appear to be a single guide instructing us how to fix these
> problems. People, this issue/confusion isn't going to fix its self, that's for
> sure. Someone needs to step up here and help us out.

No, it's just the main developer's attitude - it's impossible for him to
acknowledge that build system has bugs.

By the way, typical closure of WORKSFORME is often a plain lie - as I already wrote.

This is because to make such claim the developer needs to run build in end
user's environment - in my case I have a "one button" tool which builds
literally hundreds of targets. But the developer hasn't even asked for the tool.

Another issue - I managed to build 'glibc-2.9', but using _exactly_ the same
settings I can't build 'glibc-2.10.1', so it's a clear regression. I need to
find time to file this bug.

And I looked into the build system, and I already know there is at least a
couple of things that are screwed up, and I even know places in the build code
where they are screwed up - again, I need to find time to file these bugs.


FWIW, I will absolutely _never_ recommend sourceware/RedHat as service provider
to anybody - my dealing with this infamous bug #333 will be a clearly documented
example why.


-- 


http://sourceware.org/bugzilla/show_bug.cgi?id=333

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.