This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug faq/333] Do not report build errors in bugzilla!
- From: "pasky at suse dot cz" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sources dot redhat dot com
- Date: 5 Feb 2010 10:01:56 -0000
- Subject: [Bug faq/333] Do not report build errors in bugzilla!
- References: <20040816203830.333.roland@gnu.org>
- Reply-to: sourceware-bugzilla at sourceware dot org
------- Additional Comments From pasky at suse dot cz 2010-02-05 10:01 -------
I don't want to start a flamewar, especially in this bug. Greg, you are the one
complaining, not us. Noone is paid to support people trying to compile their own
glibc (usually with massive ./configure commandlines often bearing no
resemblance to those used in distribution packages), unfortunately, and the
project lacks any _volunteers_ to do that work.
This is why we have to deal with build problem bugs in this way, just letting
them pollute the bugzilla database in open state indefinitely is even worse.
There is no obligation for noone here to provide technical support; sometimes we
do, sometimes we can't. Sergei, if you want to volunteer to help people with
their build problems, I think you would be welcome to - just revisit bugs closed
as dupes of this. Are you willing to spend the time? The same applies to the
lack of comprehensive and up-to-date build instructions. As tgp1994 said,
someone indeed needs to step in and help out here for the situation to improve,
but it's easy to follow up "but it can't be me because X".
If you want to continue this discussion *and* have concrete technical
suggestions that do not involve the current already-overworked libc hackers
spending more time supporting users trying to compile their own libc, please
follow up on libc-help.
--
What |Removed |Added
----------------------------------------------------------------------------
Status|REOPENED |RESOLVED
Resolution| |WORKSFORME
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.