> Andreas Jaeger:
> Just use the glibcbug script that comes with every glibc installation
> to report a complete bug report.
> <rant on>
> Why can't people read? The glibc source distribution contains a
> README, a FAQ, an INSTALL file,... and installs the glibcbug script for
> bug reporting. You can even (ok, that doesn't work with some glibc
> 2.0.x versions) execute your libc, like /lib/libc.so.6 to get
> information about it.
> <rant off>
> Hmm - interesting - can one execute /lib/libc.so.6 these days?
With 2.1 it works, it is broken in 2.0.7 at least.
> Do you think anyone would have guessed that? Would have thought
> `Hmm, what is the address of the libc maintainer,
> let us say "/lib/libc.so.6" to find out!'
> ?
Ok, mentioning /lib/libc.so.6 was a bit too much. Sorry.
> [...]
> : There are probably bugs in the GNU C library. There are certainly
> : errors and omissions in this manual. If you report them, they will get
> : fixed. If you don't, no one will ever know about them and they will
> : remain unfixed for all eternity, if not longer.
> ...
> : Send bug reports to the Internet address <bug-glibc@gnu.og>.
> But then, when I report errors, I get
> ----- Transcript of session follows -----
> 550 <bug-glibc@gnu.og>... Host unknown (Name server: gnu.og: host not found)
Yes, there was a typo in the manual which is still in glibc 2.0.7pre6.
It should be gnu.org - this has been fixed in glibc 2.1.
Andreas
-- Andreas Jaeger aj@arthur.rhein-neckar.de jaeger@informatik.uni-kl.de for pgp-key finger ajaeger@aixd1.rhrk.uni-kl.de- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/