This is the mail archive of the glibc-bugs@sourceware.org mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

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


In http://sourceware.org/bugzilla/show_bug.cgi?id=11875#c10 one can read:

"
Of course this is a 333 dup.  Don't ever file build problem reports in BZ.  This
is what mailing lists are for.
".

So, the lead 'glibc' developer openly claims one can't get knowledge on how to
build 'glibc' in places other than mailing list.

I think that the logical place to look for such knowledge is the documentation
which comes with the source.

Just wondering - is the official RedHat policy ? I.e. does RedHat think that
users of its software should look for info in mailing lists rather than in the
documentation which comes with the software ?

-- 
           Summary: 'glibc' build documentation is apparently incomplete
           Product: glibc
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: libc
        AssignedTo: drepper at redhat dot com
        ReportedBy: sergstesh at yahoo dot com
                CC: glibc-bugs at sources dot redhat dot com


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

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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]