[Bug libc/11878] 'glibc' build documentation is apparently incomplete

["jsm28 at gcc dot gnu.org" <sourceware-bugzilla at sourceware dot org>]

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

Joseph Myers <jsm28 at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|SUSPENDED                   |RESOLVED
         Resolution|                            |INVALID

--- Comment #2 from Joseph Myers <jsm28 at gcc dot gnu.org> 2012-02-18 00:35:55 UTC ---
"incomplete" is not a useful bug report.  Feel free to file more specific bug
reports in the "manual" component that identify more specifically what is not
documented (for example, "the --enable-SOMETHING configure option is not
documented" or "the requirement that your processor support feature X is not
documented").

The bug you linked to, bug 11875, looks like it was a genuine configure bug
(rather than a doc bug) which was fixed by:

commit 84b9230c404aed4fd3a7bb3d045ca367043dde8c
Author: Mike Frysinger <vapier@gentoo.org>
Date:   Mon Aug 23 07:51:49 2010 -0700

    Remove multiarch dirs when gnu indirect is not supported

In the course of fixing other problems, I have found that the installation
documentation is very out-of-date - documenting many things that are no longer
relevant or appropriate on current systems - and will be pruning the old
pieces.  Some of those were advice about particular circumstances that used to
be common but are no longer going to be seen - it's useful to add advice for
current circumstances, but that can only be done when we know the causes of
current build failures.  We do need to know about deficiencies in the
installation documentation.  But identifying such a deficiency from a build
failure requires that the person seeing the failure, with access to the system
on which it appears, debugs the failure so they can understand the underlying
cause.  That's what's meant by not filing build failures in Bugzilla: a build
failure by itself does not give enough information to be a useful problem
report, but information about the underlying causes of the failure can be a
useful report.  The libc-help@sourceware.org mailing list can provide help
debugging build failures and other problems to the point at which it is
possible to make a useful bug report, so please ask there if you have a failure
but do not have enough specific information about the underlying defect in
glibc.

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.